From: Russ Dill <Russ.Dill@asu.edu>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Pantelis Antoniou <panto@intracom.gr>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Cram FS on NAND - How to do this?
Date: 11 Jun 2003 02:10:14 -0700 [thread overview]
Message-ID: <1055322613.886.2.camel@russ> (raw)
In-Reply-To: <1055322260.2097.13.camel@passion.cambridge.redhat.com>
On Wed, 2003-06-11 at 02:04, David Woodhouse wrote:
> On Wed, 2003-06-11 at 09:58, Pantelis Antoniou wrote:
> > That is a valid approach.
> >
> > I take it that you mean a new MTD block device over NAND that
> > automatically skips over bad blocks and presents an error free
> > block interface for use by read only filesystems.
>
> Basically, yes. You can then either require the use of a special
> userspace tool to program the file system images onto the flash, or
> perhaps you could implement it as a writable block device, in the
> expectation that people don't _actually_ use it in write mode in
> production.
you could simplify this by making it so that writes can only occur
starting at 0 sequentially onward (I think this is doable by not
implementing seek)
--
Russ Dill <Russ.Dill@asu.edu>
next prev parent reply other threads:[~2003-06-11 9:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-11 8:43 Cram FS on NAND - How to do this? Pantelis Antoniou
2003-06-11 8:51 ` David Woodhouse
2003-06-11 8:58 ` Pantelis Antoniou
2003-06-11 9:04 ` David Woodhouse
2003-06-11 9:10 ` Russ Dill [this message]
2003-06-11 9:12 ` David Woodhouse
2003-06-11 9:01 ` Jasmine Strong
2003-06-11 9:54 ` Pantelis Antoniou
2003-06-11 10:24 ` angainor
2003-06-11 19:22 ` Russ Dill
2003-06-12 8:22 ` Pantelis Antoniou
2003-06-12 9:06 ` Thomas Gleixner
2003-06-12 8:15 ` Pantelis Antoniou
2003-06-12 23:13 ` Charles Manning
2003-06-13 12:18 ` Jasmine Strong
2003-06-13 16:30 ` Brian J. Fox
2003-06-13 16:33 ` Jasmine Strong
2003-06-13 16:45 ` Brian J. Fox
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=1055322613.886.2.camel@russ \
--to=russ.dill@asu.edu \
--cc=dwmw2@infradead.org \
--cc=panto@intracom.gr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.