compile error when using MEMREADOOB in do_mounts.c.

Paul Wong paul.wong at
Sun Jan 5 03:49:58 EST 2003

----- Original Message -----
From: "Thomas Gleixner" <tglx at>
To: "Paul Wong" <paul.wong at>; <linux-mtd at>
Sent: Sunday, January 05, 2003 4:32 AM
Subject: Re: compile error when using MEMREADOOB in do_mounts.c.

> On Friday 03 January 2003 10:22, Paul Wong wrote:
> > Firstly, thanks Thomas,
> >
> > Let me to explain my system: I separate three partitions of NAND flash
> > (16MB),
> > /dev/mtd0   for kernel image , use dd if=xxx.img of=/dev/mtd0
> This works only, if you have no bad blocks in your mtd0 partition
> > /dev/mtd1   for rootfs image , use dd if=roofts.img of=/dev/mtd1
> Same as above
> > /dev/mtd2   for jffs2 filesystem
> Where do you boot from ? I assume NOR-FLASH. Do you have a bootloader
there ?
> You should modify your bootloader to program the kernel image either to
> NOR-FLASH itself or to the NAND-FLASH with respect to possible bad blocks
> Then your bootloader should load the kernel image from NAND bad block
> to RAM for decrompression or you decompress from your NOR-FLASH.
> There is no need to have a compressed rootfs. You can also put your root
fs on
> JFFS2, which has compression too. This will save you RAM-space. Also for
> image you need your NAND and bad block aware bootloader utility to program
> the image to the NAND chip.

Yes, I modifed the bootloader (in NOR-Flash) that can load kernel image in
/dev/mtd0 (NAND flash) and bad block handling.  and I also tried the rootfs
in JFFS2, but the customer do not shutdown the system by keyboard, just
directly power off the unit. then the JFFS2 may be corrupted and cannot boot
up again. The ramdisk is a good solution for this case.   So, I want to
modify the do_mounts.c to check the bad block to load the rootfs image to

> > Firstly, system decompress and run the compressed kernel image in mtd0,
> > then the kernel (kernel 2.4.20)will decompress the rootfs image in mtd1
> > ramdisk. ( I modified the do_mounts.c to do it). Finally, I success to
> > up and run normal. But, I see fill_inbuf() in do_mounts.c, it only use
> > read(..) functon to get the content of the rootfs.img (/dev/mtd1), is it
> > care the bad block??
> No
> --
> Thomas
> ________________________________________________________________________
> linutronix - competence in embedded & realtime linux
> mail: tglx at

More information about the linux-mtd mailing list