Nand flash and blob

Thomas Gleixner tglx at linutronix.de
Mon Nov 25 12:40:56 EST 2002


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 at linutronix.de




More information about the linux-mtd mailing list