From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] OpenNand Support?
Date: Mon, 21 Nov 2011 13:26:01 -0600 [thread overview]
Message-ID: <4ECAA5C9.1000404@freescale.com> (raw)
In-Reply-To: <CAPTcMzwt7_h5dF9prtbzxoAqZzVEv-p9aoWt2KN5EH507O998A@mail.gmail.com>
On 11/21/2011 01:16 PM, Mahavir Prasad wrote:
> Hello Scott,
>
>> ONFI should be properly supported once we sync up with Linux's NAND
>> code.
> Thanks for the reply. Is the item in priority for U-Boot maintainers?
> Can I expect it to be
> integrated with the main tree sometime in near future? Or should I start
> with the ONFI patches?
I hope that Christian -- or someone else, maybe you? :-) -- will respin
the patchset based on the feedback given. If not, I may do so
eventually, but I do have other tasks not related to U-Boot that are
demanding my time at the moment.
-Scott
next prev parent reply other threads:[~2011-11-21 19:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 14:10 [U-Boot] OpenNand Support? Mahavir Prasad
2011-11-21 18:39 ` Scott Wood
2011-11-21 19:16 ` Mahavir Prasad
2011-11-21 19:26 ` Scott Wood [this message]
2011-11-21 19:58 ` Mahavir Prasad
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=4ECAA5C9.1000404@freescale.com \
--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