From: Charles Manning <manningc2@actrix.gen.nz>
To: Paul Nash <paulnash@wildseed.com>, Russ Dill <Russ.Dill@asu.edu>,
linux-mtd@lists.infradead.org
Subject: Re: Intel sez: Synchronous Flash and XIP is the future -- thought s? -->NAND
Date: Thu, 19 Dec 2002 19:41:49 +1300 [thread overview]
Message-ID: <20021219064630.BCABD14EC0@dragon.actrix.co.nz> (raw)
In-Reply-To: <43CB1396676FD4119F03001083FD299401A1C91F@neptune.kirkland.local>
On Thu, 19 Dec 2002 02:13, Paul Nash wrote:
> So what are people out there using in their designs for NAND primarily?
> Raw NAND? NAND plus some bootable sector? DiskOnChip?
>
NAND has been around for over ten years now, but the real uptake has only
been very recent.
Until recently, most people have used DiskOnChip which is essentially just a
raw NAND + an ASIC to do ECC + a very expensive price tag.
Probably most NAND in use is SmartMedia (numerically speaking) - using FAT.
These are just raw nand on a carrier card. Just ask David Woodhouse what he
thinks about that! THis is being superceded by XD card.
Now that there are very reliable NAND file systems (JFFS2 and YAFFS) that run
under Linux and other OSs, it is becoming increasingly palatable to use raw
NAND parts soldered down, or use SmartMedia/XD if you want an expanadable
system.
The new generation NAND parts expand to 16-bit data buses and have bootable
code space. This makes it possible to build systems that are all NAND with no
NOR in sight.
-- CHarles
prev parent reply other threads:[~2002-12-19 6:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-18 13:13 Intel sez: Synchronous Flash and XIP is the future -- thought s? Paul Nash
2002-12-19 6:41 ` Charles Manning [this message]
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=20021219064630.BCABD14EC0@dragon.actrix.co.nz \
--to=manningc2@actrix.gen.nz \
--cc=Russ.Dill@asu.edu \
--cc=linux-mtd@lists.infradead.org \
--cc=paulnash@wildseed.com \
/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