> 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).
...
> So it would not be possible. Either mtd0 or mtd2.

ok, so the only issue could be with pre 2.6.30 kernels / userspaces ?

With patched kexecboot I got now get :

Got device '/dev/mtdblock0' (31, 0) of size 7Mb
Probing /dev/mtdblock0
FS could not be identified
Can't detect FS type
Got device '/dev/mtdblock1' (31, 1) of size 53Mb
Probing /dev/mtdblock1
+ FS on device is jffs2
Got device '/dev/mtdblock2' (31, 2) of size 68Mb
Probing /dev/mtdblock2
+ FS on device is jffs2
Got device '/dev/mmcblk0' (179, 0) of size 489Mb
Probing /dev/mmcblk0
FS could not be identified
Can't detect FS type
Got device '/dev/mmcblk0p1' (179, 1) of size 486Mb
Probing /dev/mmcblk0p1
+ FS on device is ext2
Can't read next device line
Found 3 items
+ processing 0: angstrom
+ processing 1: angstrom
+ processing 2: angstrom
* maximum priority 0 found at 0
+ [angstrom
/dev/mtdblock1 jffs2 53Mb]
+ processing 1: angstrom
+ processing 2: angstrom
* maximum priority 0 found at 1
+ [angstrom
/dev/mtdblock2 jffs2 68Mb]
+ processing 2: angstrom
* maximum priority 0 found at 2
+ [angstrom
/dev/mmcblk0p1 ext2 486Mb]
load_argv: /usr/sbin/kexec, -l, --command-line=root=/dev/mtdblock2
rootfstype=jffs2 rootwait console=ttyS0,115200n8 console=tty1 noinitrd
   debug, /mnt/boot/zImage
No network is detected, disabling ifdown()
exec_argv: /usr/sbin/kexec, -e, -x
Uncompressing Linux...................


What will happen booting a 2.6.26 kernel?
In fstab we have:
  rootfs      /       auto    defaults        1  1

How will be translated "mtdblock2 (31, 2) of size 68Mb" ?

Finally, I'd like to fix the recipes of kexecboot and nandlogical in
order to respect the new layout.
Perhaps with some version-checking logic?

Happily updater.sh relying on 2nd 2.4 kernel still works vanilla.

Regards

Andrea

_______________________________________________
Zaurus-devel mailing list
Zaurus-devel@lists.linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel

Reply via email to