From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Porting u-boot to a new board
Date: Fri, 19 May 2006 08:53:27 +0200 [thread overview]
Message-ID: <200605190853.27361.sr@denx.de> (raw)
In-Reply-To: <513a5e60605182056n4f04c0adgaa266cbd4868400e@mail.gmail.com>
Hi G.Sibi,
On Friday 19 May 2006 05:56, Madhu Saravana Sibi Govindan wrote:
> I'm trying to port U-boot to a new board which is based on the 440GP
> processor. It is expected to be similar to the Ebony board from AMCC.
> I'm reading the U-boot source code now. I'd be thankful to the group
> if you could tell me which portions of the code need "special"
> attention while porting, like the TLB entries, peripherals, PLL
> values, the system memory map etc.
A lot of stuff is board specific and thorough knowledge is needed to cope with
those issues. Sorry, but I can't give a cookbook description on how to
proceed.
Here some notes: Important is to start from an existing board port (if
available) that comes as close to your custom hardware as possible. I am not
sure if the Ebony port is this starting point, since e.g. it is equipped with
2 different FLASH's and with an FPGA that provides all sorts of configurable
information. A "simpler" 440GP board is the p3p440 which could be a better
starting point. But be aware that it uses onboard soldered SDRAM and not DIMM
modules. So if your board has DIMM modules you need to change the SDRAM
configuration in your board configuration file.
> Would there be problems if I invoke code for initializing PCI devices,
> but didn't have PCI support on the board, for example?
Not necessarily, but I would strongly suggest to remove the PCI support when
you don't need it.
Best regards,
Stefan
prev parent reply other threads:[~2006-05-19 6:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-19 3:56 [U-Boot-Users] Porting u-boot to a new board Madhu Saravana Sibi Govindan
2006-05-19 6:53 ` Stefan Roese [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200605190853.27361.sr@denx.de \
--to=sr@denx.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox