Hello,
Its been close to a month now that the kernel CI hwpacks built on ci.linaro.org with default omap2plus defconfigs
(available in the linux-arm-soc, linux-next, linux-linaro, linux) are failing to boot on the boards.
Here is an example hwpack built using the linux-linaro tree with omap2plus defconfig on ci.linaro.org which is failing to boot, in case you want to try to test it.
http://snapshots.linaro.org/kernel-h wpack/linux-linaro-tracking/linux-linaro-tracking_panda-omap2plus/hwpack_linaro-lt-panda_20120509-0641_b64_armel_supported.tar.gz
I was able to fix the above boot problem of the CI kernel hwpacks built with omap2plus defconfig
by adding the options similar to the ones available in (linux-linaro tree) default omap4 defconfig on top of the default
omap2plus defconfig options.
Here is the list of the config options which I added http://paste.ubuntu.com/977642/ along with the omap2plus
defconfig to make it work.
Can someone help me with the basic omap2plus defconfig options that will be required to boot the hwpack on the board.
Does anyone care of kernel builds for linux-arm-soc, linux-next, linux-linaro, linux tree using omap2plus defconfigs ?
Apart from this, there are build failures with the linux-next trees failing since last 20 days.
https://ci.linaro.org/jenkins/view/Linux%20%28next%29/ lists such failing build jobs.
For example the following job fails https://ci.linaro.org/jenkins/view/Linux%20%28next%29/job/linux-next_panda-omap2plus/.
Can someone look at these linux-next build failures ?
--
Thanks and Regards,
Deepti
Infrastructure Team Member, Linaro Platform Teams
Linaro.org | Open source software for ARM SoCs