All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Anderson <sanders@mvista.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: flash filesystem
Date: Tue, 25 Jul 2000 21:36:52 +0000	[thread overview]
Message-ID: <397E0874.564A99B6@mvista.com> (raw)
In-Reply-To: 4.3.2.7.0.20000824132843.00b1f9a0@10.0.0.2


Mike Coy wrote:
> The best that I can come up with is that the flash is probably mapped into
> memory somewhere, and maybe I could fool the ramdisk code into reading a
> pre-existant ramdisk at a given address.  This didn't appear to be too
> trivial at my first browse through the code, though.
> What is the right way to get at data in flash?

I used the MTD code to accomplish the same thing.  I have a compressed
ext2 filesystem image sitting in FLASH and pass the MTD slram driver
the beginning and ending address and it exposes the FLASH as /dev/mtd0.
To make sure we're on the same page, I'm talking about a read-only
filesystem.

Check out http://www.linux-mtd.infradead.org/ to get started with the
MTD layer.  I'm under the impression that MTD has gone into the 2.4
kernel so it should become "the" way of doing this.

    Scott Anderson
    scott_anderson@mvista.com   MontaVista Software Inc.
    (408)328-9214               490 Potrero Ave.
    http://www.mvista.com       Sunnyvale, CA  94086

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2000-07-25 21:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-24 17:36 flash filesystem Mike Coy
2000-07-24 18:33 ` Daris Nevil
2000-07-25 21:36 ` Scott Anderson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-09-07  7:34 Flash Filesystem schardt
2007-09-13  8:39 ` Laurent Pinchart

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=397E0874.564A99B6@mvista.com \
    --to=sanders@mvista.com \
    --cc=linuxppc-embedded@lists.linuxppc.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 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.