On 07/31/2010 12:54 AM, Martin Michlmayr wrote: > * Daniel Kahn Gillmor <d...@fifthhorseman.net> [2010-07-30 19:32]: >> There are recent changes in initramfs-tools to accommodate root >> filesystems on ubifs. flash-kernel should inherit these changes if >> possible, especially since ubifs is likely to be correlated with the >> presence of the flash-kernel package. > > Maybe. In the meantime, you can simply dpkg --purge flash-kernel > if your kernel is on ubifs.
I could, but flash-kernel is useful for knowing the correct incantation
of uboot-mkimage's mkimage for my architecture. Otherwise, i'd have to
track the generation of /boot/uImage myself, which seems like a poor
tradeoff.
i also note that there is no command in flash-kernel for the guruplug to
actually write the kernel to NAND storage -- it generates uImage and
uInitrd, but does not store them to /dev/mtd1 as i'd expect something like:
nandwrite /dev/mtd1 /boot/uImage
But i understand not everyone would necessarily arrange the NAND on the
GuruPlug in the same way. Perhaps we could verify that:
fw_printenv x_bootcmd_kernel
emits:
x_bootcmd_kernel=nand read.e 0x6400000 0x100000 0x400000
since in that case, the nandwrite command is more likely to be correct.
--dkg
signature.asc
Description: OpenPGP digital signature
