From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Warren <swarren@wwwdotorg.org>
Date: Thu, 24 Oct 2013 23:08:18 +0100
Subject: [U-Boot] [PATCH 2/2] video: bcm2835: fix various output modes
In-Reply-To: <20131024181447.GA82493@gmail.com>
References: <1382473641-20614-2-git-send-email-a.heider@gmail.com>
	<52680011.4070005@wwwdotorg.org> <20131024181447.GA82493@gmail.com>
Message-ID: <52699A52.3020101@wwwdotorg.org>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

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...