From: Curt Scott <curt_scott@yahoo.com>
To: linux-mtd@lists.infradead.org
Subject: OOB questions
Date: Mon, 6 Oct 2008 11:40:53 -0700 (PDT) [thread overview]
Message-ID: <843688.86807.qm@web81803.mail.mud.yahoo.com> (raw)
Hi,
I am writing a MTD NAND (2K page) driver module for Linux 2.6.23.
My NAND hardware controller performs all the ECC control
under-the-hood. Although is has OOB bytes available there are some
limitaitions...
L1.) Page data and OOB data must be written at the same time.
L2.) OOB data is limited to 16 bytes / page (of a 2k page).
I have some questions about the OOB requirements for MTD/JFFS2 combo.
Q1.) Does MTD/JFFS2 require the ability to read/write OOB bytes?
Or can the system be set up operate with no OOB available?
Q2.) Is it a requirement for OOB and non-OOB writes to happen independently?
thank you for you help,
Curt
next reply other threads:[~2008-10-06 18:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 18:40 Curt Scott [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-06 18:41 OOB questions Curt Scott
2008-10-07 4:04 ` Jason Liu
2008-10-07 4:11 ` Ravi Vasarla
2008-10-06 19:03 Curt Scott
[not found] <825594.10285.qm@web81806.mail.mud.yahoo.com>
2008-10-08 2:23 ` Jason Liu
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=843688.86807.qm@web81803.mail.mud.yahoo.com \
--to=curt_scott@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