On 01/20/2013 06:57 AM, Rob Clark wrote:
Btw, not sure if any of you have seen the 0-day kbuild setup that intel has..
https://lists.01.org/mailman/listinfo/kbuild
runs various builds for different archs on every commit with different
configs, randconfig, etc. And various checks with sparse, smatch,
etc. Seems kinda useful, and would be a worthwhile goal to get arm
arch to the point of "it just compiles and boots" like x86 is, vs arm
which has a lot higher tendency to be broken if you don't have the
right kernel config, etc. I guess on x86, they boot test all the
kernels too on VMs. Perhaps we could go one better with something
tied in to lava?
+1 on this, Rob.
Just about every time I go to bump kernel revisions for the
linaro.android tree, and actually try to build and boot on a board, I
regularly hit compile and boot issues.
Although for the boot issues, there's still the hard problem for
hardware-simpletons like me in being able to figure out what configs I
actually need to enable (especially as those options change over time).
I suspect these sorts of problems are unlikely to be something we can
test away, and instead need a more critical eye as to how the kconfig
options are added (so there's less of a random set of options that you
have to pick the right combination, and more of the existing physical
dependencies being properly stating in the kconfig - but I realize this
is more complicated to do then say).
thanks
-john
_______________________________________________
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
