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

[Thilo Fromm]

Hello Ricard,

>>> gluebi + mtdblock_ro doesn't work ?
>>
>>
>> Can you paint the abstraction layer call flow involved in this for a
>> single read transaction and _not_ burst out laughing ;) ? We're on an
>> embedded system, man :)
>
> The crucial issue is really what performance you get, gluebi is fairly
> transparent so I don't think you loose any significant amount. True, there's
> a lot of code that must be passed in order to get at the data, but the same
> is true for a lot of the kernel.

I fear the complexity. NAND technology has some nasty corner cases, I
want my NAND code to be simple and separated (KISS in the traditional
sense). Consequently I try to avoid these other parts of the kernel
that do things in a weird way, too.

> u-boot perhaps can't handle gluebi though?

Hmmm, dunno. I'm not using UBI from u-boot right now.

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