From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mark Jackson <mpfj-list@mimc.co.uk>
Date: Fri, 28 Aug 2009 11:16:22 +0100
Subject: [U-Boot] [PATCH] atngw100: Use virtual address in
	CONFIG_ENV_ADDR
In-Reply-To: <20090828113404.2c8ccfb0@hskinnemoen-d830>
References: <1251448970-15252-1-git-send-email-haavard.skinnemoen@atmel.com>	<4A97A060.8000304@mimc.co.uk>
	<20090828113404.2c8ccfb0@hskinnemoen-d830>
Message-ID: <4A97AE76.4000803@mimc.co.uk>
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

Haavard Skinnemoen wrote:
> Mark Jackson <mpfj-list@mimc.co.uk> wrote:
>> Haavard Skinnemoen wrote:
>>> Ever since the CFI driver was rewritten to use virtual addresses, thus
>>> eliminating the whole point of the map_physmem() macro, ATNGW100 has
>>> been broken like this:  
>> How about other boards (like the MIMC200) ?
>>
>> Aren't *all* AVR32 boards affected in this way ?
> 
> Possibly, but NGW100 is the only one which I've seen reports about.
> STK1000 is safe since it doesn't use the CFI driver.

I did kinda report this in the thread "JFFS2 scanning bug", and
the "triple-revert" patch you posted on 26/05/09 16:58 appeared
to fix it.

Since this didn't change any board files (only the core CFI files)
I guess I assumed this "revert" would work its way upstream and I
wouldn't have to change anything.

Shall I just submit a patch to fix the mimc200 board in the same way
as your NGW100 patch ?

Regards
Mark