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 18:52:14 -0700 [thread overview]
Message-ID: <200904281852.14371.david-b@pacbell.net> (raw)
In-Reply-To: <C9D59C82B94F474B872F2092A87F26147DF6C757@dlee07.ent.ti.com>
On Tuesday 28 April 2009, Paulraj, Sandeep wrote:
> Dave,
> We can add such support/enhancements later. The
> patch as such will work for sure.
OK, I can understand that. This board seems to have
the most complex NAND config of the DaVinci EVMs.
> In our LSPs we can use
> only one NAND at a time. We do not at this point of time
> have support even in the kernel where both NANDs can be
> used at the same time. Its only either of the 2.
And for that matter, even the DaVinci GIT tree doesn't
yet support this board ... much less mainline Linux!
I believe the current NAND driver (in 2.6.30-rc) should
handle this fine, though.
- Dave
> Thanks,
> Sandeep
>
> > -----Original Message-----
> > From: David Brownell [mailto:david-b at pacbell.net]
> > Sent: Tuesday, April 28, 2009 5:57 PM
> > To: Paulraj, Sandeep; u-boot at lists.denx.de
> > Cc: davinci-linux-open-source at linux.davincidsp.com
> > Subject: Re: [PATCH] ARM DaVinci: Adding DM357 Support
> >
> > ...
> >
> > 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-29 1:52 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
2009-04-29 0:20 ` Paulraj, Sandeep
2009-04-29 1:52 ` David Brownell [this message]
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=200904281852.14371.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