public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Pantelis Antoniou <panto@intracom.gr>
To: Phillip Lougher <phillip@lougher.demon.co.uk>
Cc: linux-mtd@lists.infradead.org
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: David Woodhouse <dwmw2@infradead.org>
Cc: David Daney <ddaney@avtrex.com>
Subject: Re: [patch] Allow any filesystem on MTD Nand when Read Only
Date: Thu, 06 May 2004 10:12:58 +0300	[thread overview]
Message-ID: <4099E57A.7020108@intracom.gr> (raw)
In-Reply-To: <4099281B.1070206@lougher.demon.co.uk>

Phillip Lougher wrote:

> 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.
>
I've taken a look at squashfs. It does seems nicer than CRAMFS.

My main problem is not that it's not in the kernel proper, but it's not 
in by bootloader too.
If you took a look at u-boot and implemented squashfs support I would 
probably switch.

> Phillip
>
>
>
>
Regards

Pantelis

  parent reply	other threads:[~2004-05-06  7:25 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
2004-05-05 19:07     ` David Daney
2004-05-06  7:12     ` Pantelis Antoniou [this message]
     [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=4099E57A.7020108@intracom.gr \
    --to=panto@intracom.gr \
    --cc=linux-mtd@lists.infradead.org \
    --cc=phillip@lougher.demon.co.uk \
    /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