From mboxrd@z Thu Jan 1 00:00:00 1970 From: Robert S. Grimes Date: Thu, 03 May 2007 08:27:57 -0400 Subject: [U-Boot-Users] Getting Started Porting U-Boot to M5329EVB board In-Reply-To: <200705031416.21731.sr@denx.de> References: <4638BF7F.5010507@alum.mit.edu> <200705030721.00820.sr@denx.de> <4639CDB8.80501@alum.mit.edu> <200705031416.21731.sr@denx.de> Message-ID: <4639D54D.6070809@alum.mit.edu> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Stefan Roese wrote: > On Thursday 03 May 2007 13:55, Robert S. Grimes wrote: > >> Yes, I am, and that is where I've started. I currently have got a >> simple copy to compile cleanly, but none of the device-specific code has >> been checked to see if it needs to be modified. >> >> Any hints as to where I should start? >> > > start.S is a good point to "start" looking at. ;-) > Right! > I have to admit that I am not into the ColdFires right now. With addition of > the M5329 to the current U-Boot ColdFire support, we should either > > a) Create a new cpu-directly for the M53xx ColdFire family > > or > > b) Rename the current cpu directory to "mfc5xxx" or something like this > > This depends on the similarities of the chips and their internal resources > (UART, interrupt controller, ethernet controller..) of course. Solution b) > would be my preferred way, if it makes sense. > Okay, I'll take that under advisement. You know, you pick your poison here - either you get similar code in separate files (solution a) or similar code in separate conditionally-compiled blocks (solution b)... Thanks for the advice! -Bob > Thanks. > > Best regards, > Stefan > > ===================================================================== > DENX Software Engineering GmbH, HRB 165235 Munich, CEO: Wolfgang Denk > Office: Kirchenstr. 5, D-82194 Groebenzell, Germany > ===================================================================== > > >