* Martin Michlmayr <t...@cyrius.com> [2015-05-16 21:37]: > So the best solution now is to append the device tree blob (DTB) to > the kernel in the installer. This way, the kernel will find the > correct device tree and can boot (and everything else will work since > flash-kernel already appends the DTB on the SheevaPlug).
Here's a test image. Take the kernel from http://www.cyrius.com/tmp/sheevaplug/uImage Take the ramdisk from http://ftp.debian.org/debian/dists/jessie/main/installer-armel/current/images/kirkwood/netboot/marvell/sheevaplug/uInitrd Boot it as described here: http://www.cyrius.com/debian/kirkwood/sheevaplug/install/ Does this boot? This is how I prepare the image: wget http://ftp.debian.org/debian/dists/jessie/main/installer-armel/current/images/kirkwood/device-tree/kirkwood-sheevaplug.dtb wget http://ftp.debian.org/debian/dists/jessie/main/installer-armel/current/images/kirkwood/netboot/marvell/sheevaplug/uImage # Remove the u-boot header dd if=uImage of=kernel.without bs=1 skip=64 rm -f uImage # Append device tree cat kirkwood-sheevaplug.dtb >> kernel.without # Create new uImage sudo apt-get install u-boot-tools mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n "Debian kernel" -d kernel.without uImage -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150517015607.ga6...@jirafa.cyrius.com
