Thanks a lot, Fathi. And thanks to Andrey who also sent a response. I was able to check out the repo and create the config. Unfortunately, the uImage build fails with an error about a missing LOADADDR. Which LOADADDR should I use for the Pandaboard? I believe LOADADDR=0x80008000 is what's recommended for the Beagleboard.
Is the KernelDeploy page still accurate? Here's the recipe outlined in the page: make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- uImage make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules make ARCH=arm INSTALL_MOD_PATH=/media/rootfs/ modules_install make ARCH=arm INSTALL_FW_PATH=/media/rootfs/lib/firmware/ firmware_install cp arch/arm/boot/uImage /media/boot/ update-initramfs -c -k `uname -r` mkimage -A arm -T ramdisk -C none -n "MY RAMDISK" -d /boot/initrd.img-`uname -r` /mnt/uInitrd I'll have to change the `uname -r` invocations to the appropriate kernel version. I'm assuming I'll also have to build the device tree blob? Thanks again for all your help. Best, Arun I built the modules, modules_install, firmware_install targets. Then, I call update-initramfs and mkimage to create the ramdisk? Is there a separate step to build the FDT blob? Thanks again for the help, Andrey. I really appreciate it. I'd be happy to update the KernelDeploy wiki page based on the info you've provided, so you don't have to keep answering questions. [1] https://wiki.linaro.org/Resources/HowTo/KernelDeploy Best, Arun
_______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
