From: Rogan Dawes <rogan@dawes.za.net>
Date: Tue, 24 Aug 2010 14:17:58 +0200
Subject: [U-Boot] DNS323 (Orion5x) must double ORION5X_SZ_BOOTROM to
 access full flash
In-Reply-To: <4C73AE37.6000902@free.fr>
References: <4C729C9B.6000509@dawes.za.net> <4C7356E0.500@free.fr>
	<4C73618B.5000607@free.fr> <4C7378F4.5080108@dawes.za.net>
	<4C73AE37.6000902@free.fr>
Message-ID: <4C73B876.8040709@dawes.za.net>
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 2010/08/24 1:34 PM, Albert ARIBAUD wrote:
> Le 24/08/2010 09:47, Rogan Dawes a ?crit :
> 
>> Yes, I still have the vendor u-boot flashed, so I can still see its
>> configuration. And, yes, it does allow reading the full 8MB of flash.
> 
>> Vendor u-boot:
> 
>> f1020040: 007f0f11 ff800000 00000000 00000000    ................
> 
>> Mainline (8MB window):
> 
>> f1020070: 003f0f11 ff800000 00000000 00000000    ..?.............
> 
>> Mainline (16MB window):
> 
>> f1020070: 007f0f11 ff800000 00000000 00000000    ................
> 
> The good news is that your flash works normally.
> 
> The bad news is that the mainline settings you are showing here are
> wrong with respect to the ORION5X_SZ_BOOTROM: A 16 MB window would be
> 00ff0f11. 007f0f11 is 8MB, and 003f0f11 is 4 MB. Thus, what you think is
> a 16MB widow is actually a 8MB one, and the 8MB one is actually 4MB,
> which explains the issues you have.
> 
> I've just checked the code for computing the window size in mainline
> u-boot, and it is off by one, reducing the actual window mapping by
> half. :(
> 
> They weird thing is that it affect *all* windows, RAM included; we
> should have seen other issues! I'll do some checks later today and
> provide an officiel bugfix this evening.
> 
> Amicalement,

Hi Albert,

Thanks for looking at this.

Do you mean that your own u-boot is also misconfigured?

Rogan