From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH 8/8] New board SIMPC8313 support: nand_boot.c, sdram.c, simpc8313.c
Date: Mon, 2 Jun 2008 11:48:35 -0500 [thread overview]
Message-ID: <20080602164835.GA3513@loki.buserror.net> (raw)
In-Reply-To: <200805311511.28106.sr@denx.de>
On Sat, May 31, 2008 at 03:11:27PM +0200, Stefan Roese wrote:
> One advantage of the current nand_spl subsystem is that it uses the same NAND
> board/platform driver as the "normal", full blown U-Boot NAND subsystem does.
> So there is no need to maintain multiple NAND drivers for one board/platform.
The elbc nand driver alone is over 4K, so that's not going to work. It
could be cut down a bit by removing erase/program support, and only
supporting the page size present on the target hardware, but even then I'd
rather use the space for things like SPD-based SDRAM initialization.
> So again, please try to use the current nand_spl infrastructure. Or at least
> explain why it doesn't work for you, so that we can work on these problems.
The NAND controller on the 8313 exposes a very different programming
interface than what nand_spl expects. I don't think there's much that could
be re-used, other than the high-level functions like nand_load().
-Scott
next prev parent reply other threads:[~2008-06-02 16:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-30 18:21 [U-Boot-Users] [PATCH 8/8] New board SIMPC8313 support: nand_boot.c, sdram.c, simpc8313.c Ron Madrid
2008-05-31 13:11 ` Stefan Roese
2008-06-02 16:48 ` Scott Wood [this message]
2008-06-02 18:43 ` Stefan Roese
2008-06-02 19:06 ` Scott Wood
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=20080602164835.GA3513@loki.buserror.net \
--to=scottwood@freescale.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