24 Oct
2013
24 Oct
'13
8:14 p.m.
Hi Stephen,
On Wed, Oct 23, 2013 at 05:57:53PM +0100, Stephen Warren wrote:
Instead, can't you obtain the buffer width and stride separately, and then configure the LCD core based on both those values, rather than assuming they're the same?
I just sent a v2 patch to do exactly that.
Regarding overscan, I wonder why you zero out the initial overscan settings.
If it was just to gain a contiguous frame buffer, can we keep the overscan settings now (assuming my v2 patch is accepted)? That way the framebuffer doesn't get cut off on the sides for old analog SDTV display devices. For HDTV, that means there's a border - but only if the user set the overscan_* values.
Thanks, Andre