On Tue, Jan 12, 2010 at 01:36:31PM +0100, Stanislav Brabec wrote: > Andrea Adami wrote: > > Hello Stanislav, > > > > > Unfortunately I have a fresh report from JaMa about wrong... > > > > BTW this was on Spitz. So the question is: does the prom appear > > somewhere in /proc/partitions? I could not find it on say mtd3... > > It should (I don't have the latest vanilla just now). And > using /proc/mtd it could be identified.
I can confirm that 2.6.32+ kernels pushed to OE didn't have physmap enabled, that's why the mtdN naming was different than with 2.6.26 With physmap as module sharpsl in kernel I can see 4th partition and I except that it will be named mtd0 as before if i add physmap to kernel instead as module. ANG r...@zjama ~ $ cat /proc/mtd dev: size erasesize name mtd0: 00700000 00004000 "System Area" mtd1: 00500000 00004000 "Root Filesystem" mtd2: 00400000 00004000 "Home Filesystem" mtd3: 006c0000 00800000 "Boot PROM Filesystem" > > > Kernel makes no guarantee of partition order. It depends on order of > > > evaluation. If both drivers (PROM, NAND) are in modules, it can vary > > > even across reboots. > > > > Ok, so what to do? Patch the kernel? > > It is more generic problem. It seems that kernel does not guarantee > order of devices. The order changed even for CF slots: In 2.6.26 > internal slot was listed first. Now external slot is listed first. This i can confirm too, without any CF (or just wifi card in CF slot) I have microdrive as hda, with CF is CF named as hda and and microdrive wasn't detected by kexecboot kernel at all (probably kexecboot bug?). If I boot system from uSD then I see CF card as hda and microdrive as hdc. > The same problem affects keyboard (kernel with CE-RH2 remote support > enumerates touchscreen differently. > > > How do other boards with NOR and NAND do? > > Modern devices use OneNAND or similar and don't need any PROM. With a > single MTD, numbers are stable. > > But this is critical problem only for boot. In the user space, there is > a lot of chances to prevent it (udev, mount by ID). > > > Imho we should respect the factory layout and keep kernel in mtd1. > > Note: I sent a patch to the kernel that fixes PROM layout and introduces > two partitions in PROM: Boot PROM System and EN-JP DB3. With 2.6.32-rc3 I don't see that 2nd PROM partition and didn't noticed any special Kconfig option for that (in case someone wanted to make your change optional) > So it would not be possible. Either mtd0 or mtd2. > > SharpROM$ cat /proc/mtd > dev: size erasesize name > mtd0: 006b0000 00020000 "Filesystem" > mtd1: 00700000 00020000 "smf" > mtd2: 02b00000 00020000 "root" > mtd3: 04e00000 00020000 "home" Regrards and thanks to all kernel hackers for increased interest in Zaurus support! -- uin:136542059 jid:martin.ja...@gmail.com Jansa Martin sip:jama...@voip.wengo.fr JaMa _______________________________________________ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
