From: benoit.thebaudeau@advansee.com (Benoît Thébaudeau)
To: linux-arm-kernel@lists.infradead.org
Subject: mtd: nand: mxc: oobfree layout?
Date: Tue, 20 Nov 2012 21:05:18 +0100 (CET) [thread overview]
Message-ID: <880504158.1762783.1353441918369.JavaMail.root@advansee.com> (raw)
In-Reply-To: <1214095427.1646097.1353358014121.JavaMail.root@advansee.com>
Dear Sascha Hauer,
I've seen in the history of mxc_nand.c that you have worked on the
nand_ecclayout structs. The following things look abnormal. Can you confirm?
- nandv1_hw_eccoob_smallpage and nandv2_hw_eccoob_smallpage:
* Why are bytes 0 and 1 in oobfree? These bytes are used for bad block
information on the 16-bit variants of these 512-byte-page NANDs.
- nandv1_hw_eccoob_largepage:
* According to the i.MX31 reference manual, the BI bytes of the spare area
buffers are not free to use. So why are bytes 5, 11, 27, 43 and 59 in
oobfree? On the contrary, if this note is a mistake in the RM, then why
are bytes 21, 37 and 53 not in oobfree?
- nandv2_hw_eccoob_smallpage, nandv2_hw_eccoob_largepage and
nandv2_hw_eccoob_4k:
* Why is byte 6 not in oobfree?
Best regards,
Beno?t
next parent reply other threads:[~2012-11-20 20:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1214095427.1646097.1353358014121.JavaMail.root@advansee.com>
2012-11-20 20:05 ` Benoît Thébaudeau [this message]
2012-11-21 9:25 ` mtd: nand: mxc: oobfree layout? Sascha Hauer
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=880504158.1762783.1353441918369.JavaMail.root@advansee.com \
--to=benoit.thebaudeau@advansee.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).