From: Charles Manning <manningc2@actrix.gen.nz>
To: "Kevin Liao" <kevinliao@iei.com.tw>
Cc: linux-mtd@lists.infradead.org
Subject: Re: NAND write verify failed problem -->cramfs
Date: Sun, 8 Jun 2003 08:34:16 +1200 [thread overview]
Message-ID: <20030607203201.B098940BD@blood.actrix.co.nz> (raw)
In-Reply-To: <015b01c32c11$a5c2a950$511711ac@kevinliao>
On Friday 06 June 2003 21:54, you wrote:
> Sorry I am new to this list and I have two questions as below:
>
> 1. To loop mount a CRAMFS (root file system) image on one JFFS2 partition,
> we should mount that partition first, shouldn't we? But how can we mount
> that JFFS2 partition without mounting the root file system?
Doing this with a root file system makes it a bit more challenging... I don't
know if that can be done.
>
> 2. Currently I use NAND flash with ramdisk image on /dev/mtdblock1 as the
> root file system. Usually I write the ramdisk image using the command
> "nandwrite /dev/mtdblock1 ramdisk.gz". So far everything works fine. But I
> am wondering whether the kernel can still load the ramdisk image if there
> are some bad blocks on /dev/mtdblock1?
You could perhaps use a cut-down version of YAFFS (like is used in the YAFFS
bootloader) to store a CRAMFS image. This is relatively simple and quite a
few people do this for booting.
Do you have enough RAM to load the image into RAM at boot? That would make it
even easier.
-- CHarles
>
> Thanks a lot for the help.
>
> Regards,
> Kevin
>
> ----- Original Message -----
> From: "Charles Manning" <manningc2@actrix.gen.nz>
> To: "Pantelis Antoniou" <panto@intracom.gr>; <tglx@linutronix.de>
> Cc: <linux-mtd@lists.infradead.org>
> Sent: Friday, June 06, 2003 5:10 AM
> Subject: Re: NAND write verify failed problem -->cramfs
>
> > BTW, is there something anologous to CRAMFS for NAND flash?
> > I have a need for a compressed read-only filesystem on NAND
> > but CRAMFS has no concept of bad blocks.
>
> You could use loop mounting. ie. store the CRAMFS image using a normal
> NAND file system (YAFFS or JFFS2) and loop mount it with cramfs.
>
> -- CHarles
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2003-06-07 20:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-02 11:04 NAND write verify failed problem Pantelis Antoniou
2003-06-02 11:21 ` NAND write verify failed problem (SOLVED?) Pantelis Antoniou
2003-06-04 18:16 ` NAND write verify failed problem Thomas Gleixner
2003-06-05 7:31 ` Pantelis Antoniou
2003-06-05 21:10 ` NAND write verify failed problem -->cramfs Charles Manning
2003-06-06 9:54 ` Kevin Liao
2003-06-07 20:34 ` Charles Manning [this message]
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=20030607203201.B098940BD@blood.actrix.co.nz \
--to=manningc2@actrix.gen.nz \
--cc=kevinliao@iei.com.tw \
--cc=linux-mtd@lists.infradead.org \
/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