From: David Brownell <david-b@pacbell.net>
To: "Narnakaje, Snehaprabha" <nsnehaprabha@ti.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"davinci-linux-open-source@linux.davincidsp.com"
<davinci-linux-open-source@linux.davincidsp.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MTD-NAND: Changes to read_page APIs to support NAND_ECC_HW_SYNDROME mode on TI DaVinci DM355
Date: Tue, 14 Apr 2009 10:36:13 -0700 [thread overview]
Message-ID: <200904141036.13325.david-b@pacbell.net> (raw)
In-Reply-To: <200904071546.14898.david-b@pacbell.net>
On Tuesday 07 April 2009, David Brownell wrote:
> >
> > I have not sent the actual NAND driver to the linux-mtd yet, since
> > the initial version (supported only 1-bit HW ECC) submitted by David
> > Brownell was still in review (no comments and not approved yet).
>
> It merged to mainline yesterday; should verify on DM6446 EVM.
For the record: it seems to have merged OK, and the resulting
driver passed all the mtd tests I threw at it. Current mainline
Linux and U-Boot interop through that small-page NAND just fine.
- Dave
next prev parent reply other threads:[~2009-04-14 17:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 16:03 [PATCH] MTD-NAND: Changes to read_page APIs to support NAND_ECC_HW_SYNDROME mode on TI DaVinci DM355 nsnehaprabha
2009-04-05 22:56 ` David Brownell
2009-04-06 22:59 ` Thomas Gleixner
2009-04-07 1:49 ` David Brownell
2009-04-07 16:02 ` Narnakaje, Snehaprabha
2009-04-07 16:45 ` Thomas Gleixner
2009-04-07 18:34 ` Narnakaje, Snehaprabha
2009-04-07 19:48 ` Thomas Gleixner
2009-04-07 23:08 ` David Brownell
2009-04-09 13:41 ` Narnakaje, Snehaprabha
2009-04-07 22:46 ` David Brownell
2009-04-14 17:36 ` David Brownell [this message]
2009-04-07 22:44 ` David Brownell
2009-04-06 23:07 ` Thomas Gleixner
2009-04-07 15:07 ` Narnakaje, Snehaprabha
-- strict thread matches above, loose matches on Subject: below --
2009-04-01 16:32 nsnehaprabha
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=200904141036.13325.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=nsnehaprabha@ti.com \
--cc=tglx@linutronix.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