25 Oct
2013
25 Oct
'13
12:08 a.m.
On 10/24/2013 07:14 PM, Andre Heider wrote:
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.
I think it was because the firmware incorrectly decided by default that my HDMI device needed overscan, when in fact it can display the entire signal it's sent. If there's a way to control that in the config file, then perhaps that might be possible instead, or perhaps I should file a bug against the firmware, assuming I'm remembering correctly...