From: Philip Rakity <prakity@yahoo.com>
To: linux-mtd@lists.infradead.org
Subject: Do not understand use of oobfree
Date: Sun, 4 Feb 2007 19:58:29 -0800 (PST) [thread overview]
Message-ID: <872380.68552.qm@web58702.mail.re1.yahoo.com> (raw)
When reading the documentation for nand flash I realized that there was
an out of band area of some size following each page. This size could
be say 8, 16 or 64 bytes. Inside this oob area is stored a bad block
marker. There may also be stored ecc bytes. And there is of course
some area not used.
Some Questions:
a) the location and size of the ecc bytes are determined by what ?
.useecc = MTD_NANDECC_AUTOPLACE,
the flash chip -
the nand controller on the flash chip ?
both ??
b) the oobfree area is specified as a {offset, length) pair. When this
gets to say the jffs2 file system what does it see. For example
.oobfree = { {8, 8} }
it would see 8 bytes starting at offset 8 OR 8 bytes starting at offset
0 and the mtd driver would do the mapping.
more complex example
.oobfree = { {3, 2}, {6, 2} }
would jffs2 see 4 bytes at offset 0. or 2 sets of data at offset 3 and
offset 6.
I am asking because if I have a flash device that does not map per the
standard includes do I have to touch jffs2 to get things to work.
regards,
Philip
____________________________________________________________________________________
Now that's room service! Choose from over 150,000 hotels
in 45,000 destinations on Yahoo! Travel to find your fit.
http://farechase.yahoo.com/promo-generic-14795097
next reply other threads:[~2007-02-05 4:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 3:58 Philip Rakity [this message]
2007-02-05 8:22 ` Do not understand use of oobfree Artem Bityutskiy
2007-02-05 9:14 ` Artem Bityutskiy
2007-02-06 16:10 ` Philip Rakity
2007-02-05 12:46 ` Adrian Hunter
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=872380.68552.qm@web58702.mail.re1.yahoo.com \
--to=prakity@yahoo.com \
--cc=linux-mtd@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