From: David Brownell <david-b@pacbell.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM DaVinci: Adding DM357 Support
Date: Tue, 28 Apr 2009 14:56:33 -0700 [thread overview]
Message-ID: <200904281456.33504.david-b@pacbell.net> (raw)
In-Reply-To: <1240951925-30439-1-git-send-email-s-paulraj@ti.com>
On Tuesday 28 April 2009, s-paulraj at ti.com wrote:
> Patch adds support for DaVinci DM357. This SOC is very similar to the DM644x.
> The DM357 EVM has 2 NANDs, one small page NAND and another large page NAND.
> But the device can only boot of the small page NAND. It does not have NOR
> support. This patch has been tested on the DM357 EVM.
So this initial U-Boot support only supports the smaller of
the two NAND chips, and access to the second one is only
after booting to the operating system?
I'd have liked to see the NAND driver updates needed to support
the chipselect of the second NAND chip, and use it with HW ECC.
- Dave
next prev parent reply other threads:[~2009-04-28 21:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 20:52 [U-Boot] [PATCH] ARM DaVinci: Adding DM357 Support s-paulraj at ti.com
2009-04-28 21:56 ` David Brownell [this message]
2009-04-29 0:20 ` Paulraj, Sandeep
2009-04-29 1:52 ` David Brownell
2009-04-28 21:59 ` David Brownell
2009-04-29 0:18 ` Paulraj, Sandeep
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=200904281456.33504.david-b@pacbell.net \
--to=david-b@pacbell.net \
--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