From: Phillip Lougher <phillip@lougher.demon.co.uk>
To: David Daney <ddaney@avtrex.com>
Cc: linux-mtd@lists.infradead.org
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Pantelis Antoniou <panto@intracom.gr>
Cc: David Woodhouse <dwmw2@infradead.org>
Subject: Re: [patch] Allow any filesystem on MTD Nand when Read Only
Date: Wed, 05 May 2004 18:44:59 +0100 [thread overview]
Message-ID: <4099281B.1070206@lougher.demon.co.uk> (raw)
In-Reply-To: <40990798.9020703@avtrex.com>
David Daney wrote:
> Pantelis Antoniou wrote:
>>
>> The following patch allows you to have any filesystem over NAND when
>> mounted
>> read only.
> After more thought, I am in the process of doing something similar.
>
I have also been doing something similar to this - though I put the bad
block handling into Squashfs (another RO compressed filesystem). It
therefore seems as if all the possible approaches have been tried:
putting the bad block code in the NAND layer; implementing a new RO
block-driver; and putting the bad block code in the RO filesystem! It
definately seems as if there is a requirement for this in the main source.
Pantelis have you looked at Squashfs? This filesystem gives much better
compression than CRAMFS.
Phillip
next prev parent reply other threads:[~2004-05-05 18:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-05 12:33 [patch] Allow any filesystem on MTD Nand when Read Only Pantelis Antoniou
2004-05-05 12:57 ` David Woodhouse
2004-05-05 13:03 ` Pantelis Antoniou
2004-05-05 15:26 ` David Daney
2004-05-05 17:44 ` Phillip Lougher [this message]
2004-05-05 19:07 ` David Daney
2004-05-06 7:12 ` Pantelis Antoniou
[not found] <AEB09EDA2548094C81ED6AA93269F63D01D09322@siebe001.apac.nokia.com>
2004-05-06 7:20 ` Pantelis Antoniou
2004-05-06 8:02 ` Thomas Gleixner
[not found] <AEB09EDA2548094C81ED6AA93269F63D01D09323@siebe001.apac.nokia.com>
2004-05-06 9:39 ` Pantelis Antoniou
2004-05-06 9:48 ` Thomas Gleixner
2004-05-06 9:45 ` Pantelis Antoniou
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=4099281B.1070206@lougher.demon.co.uk \
--to=phillip@lougher.demon.co.uk \
--cc=ddaney@avtrex.com \
--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