ARM devices on Linux are rapidly moving to use the ‘device tree‘ format to specify the CPU / SoC characteristics at kernel compile time, for producing the boot image… For systems such as the DreamPlug, this means that the old # make uImage is no longer applicable..
For the DreamPlug, this is an example of the way I now produce the bootable image, and as in so many cases, this is one way of doing it, and it works, for me..
# make -j4 # make modules_install # make firmware_install # make dtbs # rm -f arch/arm/boot/zImage_w_dtb # cat arch/arm/boot/zImage arch/arm/boot/dts/kirkwood-dreamplug.dtb > arch/arm/boot/zImage_w_dtb # mkimage -A arm -O linux -T kernel -C none -a 0x8000 -e 0x8000 -n "linux-dreamplug" -d arch/arm/boot/zImage_w_dtb ../uImage313rc7
Then copy the uImage…. file to the SDCard boot partition (and ~/lib/modules and ~/lib/firmware from the compiled kernel tree to the root partition, as appropriate..)
The uImage… naming convention is one I adopted, to allow multiple versions to be available, after changing/saving the uboot parameters..
More info on all this is at http://www.devicetree.org/Main_Page, and follow the link for ‘Device Tree Usage’ for a wealth of very detailed information..
Robert Gadsdon. January 5, 2014..