Messages in this thread | | | Date | Fri, 29 Nov 2013 14:26:53 +0100 | From | Pavel Machek <> | Subject | Re: [PATCH] Make the mtdblock read/write skip the bad nand sector |
| |
Hi!
> > Hi, > > > > > Thanks a lot for the insight. After reading this, I'm wondering what's > > > preventing us from killing MTD block support altogether. Artem, already > > > suggested it a while back... > > > > People using squashfs/cramfs/readonly ext2/.. on a NOR flash? > > And people who *still*, after all these years, don't realise that they > don't actually need it to mount JFFS2. Even as the root file system > (although they *do* need rootfstype=jffs2).
I must admit I'm such person...
I guess printk("...you don't really need mtdblock...") in jffs2's mount code would probably improve that realisation...
This certainly does not help:
pavel@amd:/data/l/linux-n900$ grep -ri mtdblock Documentation Documentation/frv/booting.txt: exec -c "console=ttySM0,115200 ip=:::::dhcp root=/dev/mtdblock2 rw" Documentation/frv/booting.txt: /dev/mtdblock3 Fourth RedBoot partition on the System Flash Documentation/arm/SA1100/Assabet:which is the third one. Within Linux, this correspond to /dev/mtdblock2. Documentation/arm/SA1100/Assabet: exec -b 0x100000 -l 0xc0000 -c "root=/dev/mtdblock2"
(Should not mtdblock be at least in devices.txt file?)
BTW... is there documentation of mtdblock "translation layer" somewhere? I realize it is very simple, but it does need to keep some data?
I guess running jffs on regular block device (USB stick, SD card) is not feasible? Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
| |