From: Troy Kisky <troy.kisky@boundarydevices.com>
To: "Narnakaje, Snehaprabha" <nsnehaprabha@ti.com>
Cc: "davinci-linux-open-source@linux.davincidsp.com"
<davinci-linux-open-source@linux.davincidsp.com>,
David Brownell <david-b@pacbell.net>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"dwmw2@infradead.org" <dwmw2@infradead.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Subject: Re: [PATCH 2.6.30-rc6 3/3] NAND: Add 4-bit ECC support for large page NAND chips
Date: Wed, 20 May 2009 17:23:14 -0700 [thread overview]
Message-ID: <4A149EF2.1010208@boundarydevices.com> (raw)
In-Reply-To: <7A436F7769CA33409C6B44B358BFFF0C0113818603@dlee02.ent.ti.com>
>
> I explored nand_bbt, jffs2 using the OOB area.
>
> This is what I found -
> 2 bytes at offset 0: BB markers
> 4 bytes at offset 8: BBT magic number/data
> 1 byte at offset 12: BBT version
> 8 bytes at offset 16: JFFS2 clear markers
>
> So, it is better to start with offset 24 (there are few bytes in between, but it is better to leave them as-is).
>
> Dave,
>
> Did you have any comments?
>
> Thanks
> Sneha
If you have to move the ECC anyway, there really isn't a further compatibility
problem with moving the JFFS2 bytes as well.
0-1 : BB marker
2-23 : Free space (JFFS2 will use)
24-63 : 4 x 10 bytes of ecc.
This way, if the default ecc layout patch that I submitted is ever accepted, the code in this
patch can be removed.
Troy
next prev parent reply other threads:[~2009-05-21 0:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-18 21:38 [PATCH 2.6.30-rc6 3/3] NAND: Add 4-bit ECC support for large page NAND chips nsnehaprabha
2009-05-18 23:57 ` Troy Kisky
2009-05-19 0:17 ` Troy Kisky
2009-05-20 14:11 ` Narnakaje, Snehaprabha
2009-05-20 19:06 ` Troy Kisky
2009-05-20 19:18 ` Narnakaje, Snehaprabha
2009-05-20 20:18 ` Troy Kisky
2009-05-20 20:49 ` Narnakaje, Snehaprabha
2009-05-21 0:23 ` Troy Kisky [this message]
2009-05-20 14:06 ` Narnakaje, Snehaprabha
2009-05-21 0:38 ` David Brownell
2009-05-23 3:51 ` Narnakaje, Snehaprabha
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=4A149EF2.1010208@boundarydevices.com \
--to=troy.kisky@boundarydevices.com \
--cc=akpm@linux-foundation.org \
--cc=david-b@pacbell.net \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=nsnehaprabha@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox