From: Troy Kisky <troy.kisky@boundarydevices.com>
To: linux-mtd@lists.infradead.org
Cc: david-b@pacbell.net, tglx@linutronix.de
Subject: Re: [PATCH V5 2/2] mtd: nand: Calculate better default ecc layout
Date: Thu, 16 Jul 2009 18:19:08 -0700 [thread overview]
Message-ID: <4A5FD18C.1090300@boundarydevices.com> (raw)
In-Reply-To: <1247789948-5764-2-git-send-email-troy.kisky@boundarydevices.com>
Troy Kisky wrote:
> Have nand_base calculate a good ecc layout
> default. A benefit of this is allowing
> a software ecc other than 3 bytes long. For example,
> 4 bit software ecc correction.
>
> This patch should be safe because it adds new
> routines to be used. As board maintainers verify
> that the new routines work for them, they should
> send in a patch changing
>
> nand_scan -> nand_scan_finish
> nand_scan_tail -> nand_scan_finish_tail
>
> This patch will also add all oob bytes that
> are not reserved for ecc or bad block markers
> to the end of the free list. I don't think this
> can cause problems, but I would like an authority
> to say, "Yes, it's safe."
>
I have a few checkpatch issues to deal with if this
approach is approved.
Sorry, it slipped my mind.
Troy
next prev parent reply other threads:[~2009-07-17 1:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1247789948-5764-1-git-send-email-troy.kisky@boundarydevices.com>
2009-07-17 19:46 ` [PATCH V5 1/2] mtd: nand: move layout structure into nand_ecc_ctrl David Brownell
2009-07-17 20:20 ` Troy Kisky
2009-07-17 21:19 ` David Brownell
[not found] ` <1247789948-5764-2-git-send-email-troy.kisky@boundarydevices.com>
2009-07-17 1:19 ` Troy Kisky [this message]
2009-07-23 19:14 ` [PATCH V5 2/2] mtd: nand: Calculate better default ecc layout Troy Kisky
2009-07-23 19:26 ` David Brownell
2009-07-23 19:38 ` Troy Kisky
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=4A5FD18C.1090300@boundarydevices.com \
--to=troy.kisky@boundarydevices.com \
--cc=david-b@pacbell.net \
--cc=linux-mtd@lists.infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).