From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] MXS-NAND: Backport ecc.size from linux kernel
Date: Mon, 19 Dec 2011 14:34:47 -0600 [thread overview]
Message-ID: <4EEF9FE7.9010901@freescale.com> (raw)
In-Reply-To: <201112192123.26747.marek.vasut@gmail.com>
On 12/19/2011 02:23 PM, Marek Vasut wrote:
>> On 12/18/2011 11:50 AM, Marek Vasut wrote:
>> What specifically is happening in "ubi part" with ecc.size = 512?
>
> The driver doesn\t support subpage writes.
Is this meant to be a workaround for the NAND layer ignoring a driver
setting NAND_NO_SUBPAGE_WRITE? I'd rather just fix that...
-Scott
next prev parent reply other threads:[~2011-12-19 20:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-18 17:50 [U-Boot] [PATCH] MXS-NAND: Backport ecc.size from linux kernel Marek Vasut
2011-12-19 14:33 ` Veli-Pekka Peltola
2011-12-19 15:05 ` Marek Vasut
2011-12-19 15:30 ` Veli-Pekka Peltola
2011-12-19 20:19 ` Scott Wood
2011-12-19 20:23 ` Marek Vasut
2011-12-19 20:34 ` Scott Wood [this message]
2011-12-19 20:56 ` Marek Vasut
2012-01-03 21:20 ` Marek Vasut
2012-01-03 21:30 ` Scott Wood
2012-01-04 0:39 ` 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=4EEF9FE7.9010901@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