From: Veli-Pekka Peltola <veli-pekka.peltola@bluegiga.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] NAND: Let NAND_NO_SUBPAGE_WRITE through
Date: Fri, 11 Nov 2011 14:52:38 +0200 [thread overview]
Message-ID: <4EBD1A96.8010805@bluegiga.com> (raw)
In-Reply-To: <201111101844.54924.marek.vasut@gmail.com>
On 11/10/2011 07:44 PM, Marek Vasut wrote:
> Actually, maybe we should fix this in Linux first. Is the GPMI-NAND driver for
> i.MX28 applied already to mainline linux-mtd?
Yes, it is in 3.2-rc1:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=tree;f=drivers/mtd/nand/gpmi-nand
I have tried to figure out why it works. The driver sets same
NAND_NO_SUBPAGE_WRITE flag but it is also dropped in nand_base. One
difference is: chip->ecc.size is set to 1 instead of 512.
--
Veli-Pekka Peltola
next prev parent reply other threads:[~2011-11-11 12:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-05 2:24 [U-Boot] [PATCH] NAND: Let NAND_NO_SUBPAGE_WRITE through Marek Vasut
2011-11-06 9:01 ` Stefano Babic
2011-11-06 12:43 ` Marek Vasut
2011-11-06 14:54 ` Stefano Babic
2011-11-06 15:16 ` Marek Vasut
2011-11-10 17:02 ` Marek Vasut
2011-11-10 17:10 ` Scott Wood
2011-11-10 17:44 ` Marek Vasut
2011-11-11 12:52 ` Veli-Pekka Peltola [this message]
2011-11-11 17:50 ` Marek Vasut
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=4EBD1A96.8010805@bluegiga.com \
--to=veli-pekka.peltola@bluegiga.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