On Tue, Nov 1, 2016 at 12:36 PM, Gerd Hoffmann <kraxel(a)redhat.com> wrote:
Hi,
> > from a survey of my Samsung Smart TV automatic option is disabled!!! but in
> So Raspbian uses a completely different kernel and driver stack, most
> of the options documented in config.txt are completely irrelevant for
> the new driver stack (nothing to do with the Fedora side of things).
> The auto adjustment in the screen settings has worked every single
> time for me, why can't you use this?
Same problem here. Have configured overscan in config.txt[1]. That
works with the downstream kernel (and the BCM2708 fb driver). But as
you outlined already everything else (uboot, simplefb, vc4) ignores the
config.txt settings and I also havn't found any other way to configure
overscan.
I have a samsung tv too, with one of my rpi2's connected. Walked
through the tv menus playing with the settings, but couldn't make things
work properly.
So, no easy way out it seems?
Not off hand, sadly we seem to be having the early adopters problem on
a 4.5 year old device :-/
It's a pity all the EDID and similarly related monitor detection stuff
wasn't shared across drivers in a central location. Going from a
closed driver with a forked kernel we've never supported to a fully
open upstream doesn't give us a lot of room. I'm not a graphics
developer, nor really a kernel developers, so we're at a combination
mercy of upstream and not even the ability to dig into the
driver/firmware to workout what the other driver does.
Open to suggestions but I've pulled in all the upstream fixes I'm aware of.
Peter