From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] NAND:Extending the nand_ecclayout structure
Date: Wed, 18 Nov 2009 14:29:43 -0600 [thread overview]
Message-ID: <20091118202943.GC15517@loki.buserror.net> (raw)
In-Reply-To: <1258396307-9446-1-git-send-email-s-paulraj@ti.com>
On Mon, Nov 16, 2009 at 01:31:47PM -0500, s-paulraj at ti.com wrote:
> From: Sandeep Paulraj <s-paulraj@ti.com>
>
> NANDs with page size of lesser than and equal to 2K are
> reaching EOL. They are bing replaced with NANDs of
> page size 4K and above.
> To support this we have to extend the eccpos field
>
> Signed-off-by: Sandeep Paulraj <s-paulraj@ti.com>
> ---
> I believe a patch was submitted to linux-mtd to update this.
> But this change was rejected to the best of my knowledge because
> it will break user space IOCTL's, i.e. when we we run some tests
> from the mtd-utils. I can't see an solution to the issue addressed
> in the kernel or mtd-utils. I think this can be added to u-boot.
Applied.
-Scott
prev parent reply other threads:[~2009-11-18 20:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 18:31 [U-Boot] [PATCH] NAND:Extending the nand_ecclayout structure s-paulraj at ti.com
2009-11-18 20:29 ` Scott Wood [this message]
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=20091118202943.GC15517@loki.buserror.net \
--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