From mboxrd@z Thu Jan  1 00:00:00 1970
From: Pink Boy <dasfoo@yahoo.com>
Date: Mon, 3 Nov 2008 13:40:50 -0800 (PST)
Subject: [U-Boot] Building u-boot for the AT91RM9200-EK circa 2008
In-Reply-To: <20081103201112.D840E83568B6@gemini.denx.de>
Message-ID: <15593.6415.qm@web31812.mail.mud.yahoo.com>
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


Wolfgang Denk sez,

> The thing is: we will not accept any such (new) code for
> mainline. And switching to using the CFI driver is trivial.

Okay so what I've learned.

1)You can build the AT91RM9200DK version of u-boot with u-boot-1.3.4
and it works.  At least I got a prompt.  So one can use the 
AT91RM9200DK as a starting point for the AT91RM9200EK.

2) At this point I think relying on any older patched version of
u-boot that supports the AT91RM9200EK is probably not workable and
not worth doing.

3) Anyone starting a project based on the AT91RM9200EK is making 
big mistake because the AT91RM9200 chip has been abandoned by its
mother.

At least I have I have some sort of peg in the ground to
start with.  Right now I worry about trying to get the CFI to
work because as a noob I'm in the dark on a lot of things 

1) How to port the CFI to the AT91RM9200DK.
2) Create a board support for the AT91RM9200EK based on that.
3) Generate patches that are acceptable.

Personally I think that Atmel is doing people a disservice by 
not classifying the AT91RM9200 as not for new designs since 
there is no current support for it.

Matthew Harper.
Tehama Wireless.