From: Russ Dill <Russ.Dill@asu.edu>
To: manningc2@actrix.gen.nz
Cc: David Woodhouse <dwmw2@infradead.org>, Wolfgang Denk <wd@denx.de>,
Paul Nash <paulnash@wildseed.com>,
"Linux-MTD (E-mail)" <linux-mtd@lists.infradead.org>
Subject: Re: Intel sez: Synchronous Flash and XIP is the future -- thoughts?
Date: 16 Dec 2002 14:21:19 -0700 [thread overview]
Message-ID: <1040073679.27220.9.camel@timmy> (raw)
In-Reply-To: <20021216210640.C31D314C2B@dragon.actrix.co.nz>
On Mon, 2002-12-16 at 14:02, Charles Manning wrote:
> Intel's flash is expensive. Figure somwhere over $1 per MB. NAND costs
> approx 30c/MB + SDRAM approx 20c/MB. Intel's flash thus costs approx twice
> what a NAND/RAM image does.
>
> One NAND flash footprint can give you up to 256MB of storage.
>
> NOR fully sucks for any sort of writeable file system performance. NAND runs
> a very usable fs with YAFFS or JFFS2.
>
> The only benefit I can see in NOR is a faster boot. This is becoming less of
> an issue as more designs switch to sleep/resume models.
It really depends on how much data you store, and how you use that data.
Sure, for you, with a dynamic file system, and 256M of storage, NAND is an
easy choice. But many designs out there have static file systems, use 2M or
4M of flash, and for such designs, NOR offers a lot more simplicity for around
the same cost as a NAND + boot logic. With NOR flash, I can put a couple
cramfs filesystems on there, and use the boot block for storing a simple
journalled config, reliably. I don't have to worry about setting aside blocks
in case one goes bad.
I think this is the market intel is targeting, just change 2M or 4M to 4M or 8M
(no more compressed fs).
next prev parent reply other threads:[~2002-12-16 20:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-16 2:51 Intel sez: Synchronous Flash and XIP is the future -- thoughts? Paul Nash
2002-12-16 9:07 ` David Woodhouse
2002-12-16 9:27 ` Wolfgang Denk
2002-12-16 9:38 ` David Woodhouse
2002-12-16 9:56 ` Wolfgang Denk
2002-12-16 11:45 ` David Woodhouse
2002-12-16 17:21 ` Nicolas Pitre
2002-12-16 17:38 ` David Woodhouse
2002-12-16 18:06 ` Nicolas Pitre
2002-12-16 17:43 ` Wolfgang Denk
2002-12-16 18:07 ` Nicolas Pitre
2002-12-16 21:02 ` Charles Manning
2002-12-16 21:21 ` Russ Dill [this message]
2002-12-16 23:18 ` Charles Manning
2002-12-16 11:04 ` Michal Schulz
2002-12-16 11:16 ` Wolfgang Denk
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=1040073679.27220.9.camel@timmy \
--to=russ.dill@asu.edu \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=manningc2@actrix.gen.nz \
--cc=paulnash@wildseed.com \
--cc=wd@denx.de \
/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