public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Paul Wong <paul.wong@digitalview.com>, linux-mtd@lists.infradead.org
Subject: Re: compile error when using MEMREADOOB in do_mounts.c.
Date: Sat, 04 Jan 2003 21:32:18 +0100	[thread overview]
Message-ID: <200301042132.18179.tglx@linutronix.de> (raw)
In-Reply-To: <001301c2b309$b85d8750$9000010a@paulwong>

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 the 
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 aware 
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 this 
image you need your NAND and bad block aware bootloader utility to program 
the image to the NAND chip.

> 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 to
> ramdisk. ( I modified the do_mounts.c to do it). Finally, I success to boot
> up and run normal. But, I see fill_inbuf() in do_mounts.c, it only use the
> 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
http://www.linutronix.de
mail: tglx@linutronix.de

  reply	other threads:[~2003-01-04 20:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-03  7:56 compile error when using MEMREADOOB in do_mounts.c Paul Wong
2003-01-03  8:52 ` Thomas Gleixner
2003-01-03  9:22   ` Paul Wong
2003-01-04 20:32     ` Thomas Gleixner [this message]
2003-01-05  8:49       ` Paul Wong
2003-01-05  9:37         ` Thomas Gleixner
2003-01-05 15:56           ` Paul Wong

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=200301042132.18179.tglx@linutronix.de \
    --to=tglx@linutronix.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=paul.wong@digitalview.com \
    /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