From: Alex Waterman <awaterman@dawning.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] RFC: porting u-boot to sequoia based nand booting board
Date: Tue, 17 May 2011 10:11:14 -0400 [thread overview]
Message-ID: <4DD28202.4050305@dawning.com> (raw)
In-Reply-To: <201105171541.01662.sr@denx.de>
Stefan,
On 05/17/2011 09:41 AM, Stefan Roese wrote:
> What changes did you have to make? Some 8/16 bit related changes? Or something
> else?
I changed the hard coded value of EBC0_CFG; I forced the chip->options field to have the 16 bit bus width flag set; in board_nand_select_device() I modified the value written to the NDFC_CCR register; I think that's primarily it. The hard coded registers could be made into CONFIG_SYS defines I think, but the bus width setting... Could we make a CONFIG_SYS define that specifies the width of the bus since during the spl we don't have access to the nand chip table?
> It should be the goal, to use *only* the common NDFC code. If you have found
> some bugs, or you need some changes for 16bit devices, we should try to
> integrate them into the common code.
I have seen issues with the nand_read_byte16() function in nand_base.c; it seems like the cpu_to_le16() should be the other way around: le16_to_cpu(). Other than that no bugs as far as I am aware.
> One idea behind the static declarations is to not pollute the namespace.
Ahh, understood.
>> Likewise much of our board specific support files are copies from the
>> sequoia code. Would it be better to symlink to the ones that are not
>> modified? Or is it OK to just copy the relevant source files into our own
>> board directory and make minor adjustments as needed?
> Usually we copy those files into a new board directly. When the similarities
> are too big, then we should probably think about splitting to common parts
> into some other directory (arch/powerpc/cpu/ppc4xx/ppc440epx.c ???).
OK, I see. Most of the code in board/amcc/sequoia is the same except for some of the sdram initialization and the sequoia.c file (which I renamed to tiger.c). Also the linker script differs slightly. How would we go about making those board files common (init.S, chip_config.c)?
Regards,
Alex
--
Alex Waterman
Computer Engineer
Phone: 215-896-4920
Email: awaterman at dawning.com
next prev parent reply other threads:[~2011-05-17 14:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 13:00 [U-Boot] RFC: porting u-boot to sequoia based nand booting board Alex Waterman
2011-05-17 13:41 ` Stefan Roese
2011-05-17 14:11 ` Alex Waterman [this message]
2011-05-17 15:37 ` Stefan Roese
2011-05-17 17:05 ` Scott Wood
2011-05-17 17:49 ` Alex Waterman
2011-05-17 19:20 ` Scott Wood
2011-05-17 21:15 ` Alex Waterman
2011-05-17 21:32 ` Scott Wood
2011-05-18 12:49 ` Alex Waterman
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=4DD28202.4050305@dawning.com \
--to=awaterman@dawning.com \
--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