Nand flash and blob

Gabriel Goldstein anidea at
Mon Nov 25 12:28:29 EST 2002

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.

How do you handle the aspect of all of the dev devices?  Are they part
of the root file system in ram still?

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?



-----Original Message-----
From: Thomas Gleixner [mailto:tglx at] 
Sent: Monday, November 25, 2002 12:16 PM
To: anidea at; linux-mtd at
Subject: Re: Nand flash and blob

On Monday 25 November 2002 17:49, Gabriel Goldstein wrote:
> Hello,
> I'm working on a arm based design where I have a 16MB Sandisk/Samsung
> nand flash device.  I think I have the Linux side settled buy using
> standard MTD driver.
> I'm using BLOB and I'd like to know what people are doing to get the
> system loaded.  I have zImage, params, and ramdisk that I want to use
> NAND device to store these blocks.
You will have to extend block to handle NAND. You could use the nand
code from mtd-cvs for this. Be aware that you have to handle bad blocks,
your chip can have factory marked bad blocks.

On my system I have 1MB bootflash, where the bootloader, zImage and
params are 
stored and my root filesystem is on a JFFS2 partition on NAND. Thats the

fastest way to go along I think.

linutronix - competence in embedded & realtime linux
mail: tglx at

More information about the linux-mtd mailing list