State of read-only filesystems in NAND / MTD bad blocks handling when reading

[Thilo Fromm]

Hello Richard,

>> Apart from the fact that my NAND SW stack will then be two layers
>> higher than it actually needs to be (and the added complexity this
>> brings to boot loader and kernel) -  as far as I know UBI does not
>> provide the functionality we require: being able to store a read-only
>> file system image, and mount it at boot time. At least we don't get
>> this without another boot step (initrd, see above).
>
>
> With a root file system in ubifs, you can boot directly with a root
> filesystem in UBI, with a kernel command line such as
>
> ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs
>
> I don't know how far back that was possible, you were using 2.6.27 were you
> not (in my case I'm using 2.6.35)?

This would work for me (since I'm on 2.6.37) but I deeply eschew the
complexity this approach would bring to our system. Don't get me wrong
- I really like UBIFS; we use it for application partitions. I just
don't think it's the right thing to use for a RO rootfs. I want
simple.

Regards,
Thilo

-- 
Dipl.-Ing (FH) Thilo Fromm, MSc., Embedded Systems Architect
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, D-10319 Berlin, Germany
Tel: +49 (30) 515 932 228   mailto:fromm at dresearch-fe.de
Fax: +49 (30) 515 932 77    http://www.dresearch.de
Amtsgericht: Berlin Charlottenburg, HRB 130120 B
Ust.-IDNr. DE273952058
Geschäftsführer: Dr. M. Weber, W. Mögle