From: Troy Kisky <troy.kisky@boundarydevices.com>
To: nsnehaprabha@ti.com
Cc: davinci-linux-open-source@linux.davincidsp.com,
Sandeep Paulraj <s-paulraj@ti.com>,
linux-mtd@lists.infradead.org, tglx@linutronix.de,
dwmw2@infradead.org, akpm@linux-foundation.org
Subject: Re: [PATCH v3 3/3] mtd-nand: DaVinci: Add 4-bit ECC support for large page NAND chips
Date: Thu, 16 Jul 2009 16:56:37 -0700 [thread overview]
Message-ID: <4A5FBE35.1030908@boundarydevices.com> (raw)
In-Reply-To: <1247781590-11323-1-git-send-email-nsnehaprabha@ti.com>
nsnehaprabha@ti.com wrote:
> +/* An ECC layout for using 4-bit ECC with large-page (2048bytes) flash,
> + * storing ten ECC bytes plus the manufacturer's bad block marker byte,
> + * and not overlapping the default BBT markers.
> + */
> +static struct nand_ecclayout hwecc4_2048 __initconst = {
> + .eccbytes = 40,
> + .eccpos = {
> + /* at the end of spare sector */
> + 24, 25, 26, 27, 28, 29, 30, 31, 32, 33,
> + 34, 35, 36, 37, 38, 39, 40, 41, 42, 43,
> + 44, 45, 46, 47, 48, 49, 50, 51, 52, 53,
> + 54, 55, 56, 57, 58, 59, 60, 61, 62, 63,
> + },
> + .oobfree = {
> + /* 1 byte at offset 0 holds manufacturer badblock marker */
> + {.offset = 1, .length = 23, },
> + /* 5 bytes at offset 8 hold BBT markers */
> + /* 8 bytes at offset 16 hold JFFS2 clean markers */
> + },
> +};
I hate to sound like a broken record, but
If the bad block marker is only 1 byte. Don't you need to override
static struct nand_bbt_descr largepage_flashbased = {
.options = NAND_BBT_SCAN2NDPAGE,
.offs = 0,
.len = 2,
.pattern = scan_ff_pattern
};
I think it is easier just to leave it as 2 bytes. That may
allow substituting a different manufacturers chip too.
next prev parent reply other threads:[~2009-07-16 23:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 21:59 [PATCH v3 3/3] mtd-nand: DaVinci: Add 4-bit ECC support for large page NAND chips nsnehaprabha
2009-07-16 23:56 ` Troy Kisky [this message]
2009-07-17 14:31 ` Narnakaje, Snehaprabha
2009-07-17 19:32 ` David Brownell
2009-07-17 20:18 ` Narnakaje, Snehaprabha
2009-07-17 21:18 ` David Brownell
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=4A5FBE35.1030908@boundarydevices.com \
--to=troy.kisky@boundarydevices.com \
--cc=akpm@linux-foundation.org \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=nsnehaprabha@ti.com \
--cc=s-paulraj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.