Hello, I have built kernel 2.6.31.5 with modules and ramdisks for some combinations of Kirkwood-based devices (Sheevaplug and QNAP TS-[12]19) and devices carrying the root filesystem. They are available together with my build scripts at http://fedora.danny.cz/arm/ the kernels are: uImage-2.6.31.5-kw uImage-2.6.31.5-kw-ts219 => U-Boot images, generic, but the -ts219 explicitly sets the correct machine ID for the QNAP, because otherwise the ID of the related development board will be used. more details about the available ramdisks: - .padded = padded to 9MB which is the size of flash dedicated to ramdisk on QNAP TS-[12]19 - .uboot = ramdisk converted to an U-Boot image initrd-2.6.31.5-kw-lvm-sata.img initrd-2.6.31.5-kw-lvm-sata.img.padded initrd-2.6.31.5-kw-lvm-sata.img.uboot => use on QNAP with root filesystem on HDD(s) with LVM logical volume /dev/Linux/Root initrd-2.6.31.5-kw-sda1-sata.img initrd-2.6.31.5-kw-sda1-sata.img.padded initrd-2.6.31.5-kw-sda1-sata.img.uboot => use on QNAP with root filesystem on 1st HDD partition /dev/sda1 initrd-2.6.31.5-kw-sdmmc.img initrd-2.6.31.5-kw-sdmmc.img.uboot => use on Sheevaplug with root filesystem on 1st partition of SD card initrd-2.6.31.5-kw-usb.img initrd-2.6.31.5-kw-usb.img.uboot => use on Sheevaplug with root filesystem on 1st partition of USB attached storage (/dev/sda1) and how to test on Sheevaplug with root filesystem on 1st partition of SD card with network boot: > tftpboot 0x400000 uImage-2.6.31.5-kw > tftpboot 0x800000 initrd-2.6.31.5-kw-sdmmc.img.uboot > setenv bootargs 'console=ttyS0,115200 root=/dev/mmcblk0p1 ro' > bootm 0x400000 0x800000 Dan _______________________________________________ fedora-arm mailing list fedora-arm@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-arm
