help: bootloader for loading kernel from mtdblock device on flash........

Thomas Gleixner tglx at
Tue Feb 4 05:38:13 EST 2003

On Tuesday 04 February 2003 10:30, Vishal wrote:
> >Yep. copy your compressed kernel image in chunks of blocksize to your
> >NAND-FLASH. Reserve enough spare in the case you have bad blocks.
> >Provide a bad block aware read function and modify the decompressor in the
> >kernel to read the image via this function from NAND.
> >Then you don't need JFFS2 inside the bootloader.
> >Then your NAND-CHIP has to have min. 2 Partitions
> >1 for the kernel Image and 1 for the root-fs. You do not mount the
> > partition, where your kernel image is stored.
> hmm....correct me if i am wrong but what you are saying is i have a char
> device /dev/mtd1 (right??) on which i store the kernel image. this
> partition will never be mounted. The kernel image is stored on this
> device in chunks of blocksize.
>    Now while reading from this device on bootup, i read from the char
> device, and generate blocks of the known size in memory, carry out error
> checking and correction on each block. and when the whole of the kernel
> has been read, i run it...right?
> Pardon me if i am wrong.
You don't need to implement a character device. Implement raw NAND access with 
ECC and bad block handling (just skip a bad block, when you program your 
image) in your bootloader. So you can program your kernel image in chunks of 
blocksize into the NAND chip. On boot you provide a small function, which can 
read the kernel image out of the nand-flash. You can do this by copying the 
hole image to RAM and then start the kernel, or load just the decompressor 
portion of the kernel image and modify the decompressor code, so it can read 
the chunks from your NAND-chip.

I'm not sure, why you want to do all this, if there is an out of the box 
solution in YAFFS ? 

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

More information about the linux-mtd mailing list