From: "Jason Liu" <liu.h.jason@gmail.com>
To: "Curt Scott" <curt_scott@yahoo.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: OOB questions
Date: Tue, 7 Oct 2008 12:04:33 +0800 [thread overview]
Message-ID: <e8775dd00810062104g446c7300vfa82c40546b8effb@mail.gmail.com> (raw)
In-Reply-To: <747772.64619.qm@web81802.mail.mud.yahoo.com>
2008/10/7 Curt Scott <curt_scott@yahoo.com>:
> 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.
Not only your NFC but also some others require to written page data
and oob data
at the same time espically for large page size nand flash since it use oob to
store the ECC data.
> L2.) OOB data is limited to 16 bytes / page (of a 2k page).
>
It should be ok for jffs2 filesystem.
> 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?
jffs2 can work without oob.
> Q2.) Is it a requirement for OOB and non-OOB writes to happen independently?
>
May provide the interface to MTD layer. For MLC Nand flash, it's
impossible to write data and oob indepently since NOP is 1.
The file system should take care not to write it without erase it for MLC.
> thank you for you help,
> Curt
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
next prev parent reply other threads:[~2008-10-07 4:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 18:41 OOB questions Curt Scott
2008-10-07 4:04 ` Jason Liu [this message]
2008-10-07 4:11 ` Ravi Vasarla
[not found] <825594.10285.qm@web81806.mail.mud.yahoo.com>
2008-10-08 2:23 ` Jason Liu
-- strict thread matches above, loose matches on Subject: below --
2008-10-06 19:03 Curt Scott
2008-10-06 18:40 Curt Scott
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=e8775dd00810062104g446c7300vfa82c40546b8effb@mail.gmail.com \
--to=liu.h.jason@gmail.com \
--cc=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