From: Thomas Gleixner <tglx@linutronix.de>
To: anidea@earthlink.net, linux-mtd@lists.infradead.org
Subject: Re: Nand flash and blob
Date: Mon, 25 Nov 2002 18:40:56 +0100 [thread overview]
Message-ID: <200211251840.56144.tglx@linutronix.de> (raw)
In-Reply-To: <018501c294a8$12311ba0$6401000a@zorak>
On Monday 25 November 2002 18:28, Gabriel Goldstein wrote:
> This is interesting. I was planning on storing my ramdisk image in the
> nand flash and still having blob expand it to ram. I can see benefits
> to both ways. If I store the ramdisk.gz in flash, I will always have a
> good image to boot up to, if I store it directly in nand, I could have
> persistant information much easier.
If youre not going to have a lot of changing environment, there is no real
reason to use a ramdisk.
> How do you handle the aspect of all of the dev devices? Are they part
> of the root file system in ram still?
My root fs is on JFFS2 and the /dev/ directory is on there
> If I wanted to make a JFFS image, how do I take a directory and make a
> file system image that I could load though blob? Or how else would I
> get it in there?
You mean a JFFS2 image ? Either you boot your Kernel via NFS, mount your FLASH
with JFFS2 and copy all the stuff you need over there. The other way is you
build up your root fs in a directory and use mkfs.jffs2, which is in
mtd/utils, to build a fs-image. Then you still have to modify blob to burn it
into the flash. Read also http://www.linux-mtd.infradead.org/tech/nand.html
--
Thomas
____________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de
next prev parent reply other threads:[~2002-11-25 17:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-25 16:49 Nand flash and blob Gabriel Goldstein
2002-11-25 17:15 ` Thomas Gleixner
2002-11-25 17:28 ` Gabriel Goldstein
2002-11-25 17:40 ` Thomas Gleixner [this message]
2002-11-25 19:22 ` Charles Manning
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=200211251840.56144.tglx@linutronix.de \
--to=tglx@linutronix.de \
--cc=anidea@earthlink.net \
--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