From: Charles Manning <manningc2@actrix.gen.nz>
To: linux-mtd@lists.infradead.org
Subject: Fwd: YAFFS on NOR
Date: Wed, 22 Jan 2003 09:50:56 +1300 [thread overview]
Message-ID: <20030121205525.32F2814AF8@dragon.actrix.co.nz> (raw)
Hi folks
I thought it might be of interest to tell you that people are now starting to
use YAFFS with NOR. Whether is a Good Thing or not, I will not comment on.
Although YAFFS was designed/written with the intention of working only with
NAND, you can make it work on NOR too.
YAFFS uses the OOB space in NAND parts to store tag information. All you need
to do is simulate this area.
For instance, let us suppose you have 64kB blocks. You can do the following:
* Set YAFFS up for 124 chunks per block. ie 124x512 bytes used for data
* Use the remaining 2048 bytes to emulate OOB area (16 bytes per chunk).
YAFFS is not erase suspend aware and thus is going to stall during an
erasure. This might get addressed some time. OK, I lied, I will comment. I
think JFFSx is superior on NOR for Linux. [The person using YAFFS on NOR is
not doing this under Linux].
-- CHarles
reply other threads:[~2003-01-21 20:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030121205525.32F2814AF8@dragon.actrix.co.nz \
--to=manningc2@actrix.gen.nz \
--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