Hi,
Where can I find the git repo that contains the kernel sources for the Pandaboard 13.09 Ubuntu image?
The Linaro wiki mentions the kernel/linux-linaro-3.1.git repo:
https://wiki.linaro.org/Resources/HowTo/KernelDeploy
I didn't see a kernel/linux-linaro-3.11.git repo, so I'm guessing kernel/linux-linaro-stable.git is the repo I want?
To reconstruct the .config that was used to build the kernel, I suppose I should 'cat debug.conf linaro-base.conf omap4.conf panda.conf ubuntu-minimal.conf'?
Thanks for your help.
Best, Arun
On 16 October 2013 21:19, Arun Thomas arun.thomas@gmail.com wrote:
Hi,
Where can I find the git repo that contains the kernel sources for the Pandaboard 13.09 Ubuntu image?
The Linaro wiki mentions the kernel/linux-linaro-3.1.git repo:
https://wiki.linaro.org/Resources/HowTo/KernelDeploy
I didn't see a kernel/linux-linaro-3.11.git repo, so I'm guessing kernel/linux-linaro-stable.git is the repo I want?
https://git.linaro.org/gitweb?p=kernel/linux-linaro-tracking.git (linux-linaro branch) or https://releases.linaro.org/13.09/components/kernel/linux-linaro/linux-linar...
To reconstruct the .config that was used to build the kernel, I suppose I should 'cat debug.conf linaro-base.conf omap4.conf panda.conf ubuntu-minimal.conf'?
ARCH=arm ./scripts/kconfig/merge_config.sh linaro/configs/linaro-base.conf linaro/configs/distribution.conf linaro/configs/omap2plus.conf linaro/configs/panda.conf or pick up config in the deb package.
Cheers, Fathi
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
On 17 October 2013 17:37, Arun Thomas arun.thomas@gmail.com wrote:
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.
see below
Is the KernelDeploy page still accurate? Here's the recipe outlined in the page:
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- uImage
zImage instead of 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?
make dtbs
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
On 17 October 2013 07:49, Fathi Boudra fathi.boudra@linaro.org wrote:
On 17 October 2013 17:37, Arun Thomas arun.thomas@gmail.com wrote:
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.
see below
Is the KernelDeploy page still accurate? Here's the recipe outlined in the page:
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- uImage
zImage instead of uImage
Last time I tried bootz with pandaboard u-boot from Linaro hwpacks, it did not understand this command so zImage did not work for it I had to pull u-boot source tree and enable bootz configs (CONFIG_CMD_BOOTZ), only after that I was able to use zImage with Pandaboard.
For Pandaboard uImage personally I use LOADADDR=0x80008000
make LOADADDR=0x80008000 uImage
Thanks, Victor
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?
make dtbs
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
Thanks a lot, Fathi and Victor. I was able to build and boot the 3.12.0-rc5 kernel on the Pandaboard. I went with building a uImage, but I'll try a zImage next. It looks like I'll have to update the boot.scr (and u-boot, based on Victor's reply), since the 13.09 boot.scr calls bootm.
Is there a recipe to cross-build the initramfs? I ended up doing update-initramfs -c -k `uname -r` on the Pandaboard itself.
Arun
-
Arun Thomas -
Fathi Boudra -
Victor Kamensky