On Wed, 8 Jun 2011, Dave Martin wrote: > Bisecting when CONFIG_THUMB2_KERNEL=y reproducibly identified > af3e4fd37a18f2e5a00175bc96061541d1364a3b as the first bad commit > between v2.6.39 and linux-linaro-2.6.39/master, but it's obviously > totally irrelevant and causes no code changes at all (which I > confirmed by disassembling) :P Only the config.gz data and kernel > signature in the kernel changes... > > It could be a decompressor problem or similar, but actually booting > from an Image doesn't work for me either after or before the above > commit.
How is this commit identified as the first bad one then? Another thing to keep in mind is the fact that the OMAP code is doing pretty nasty things wrt the serial console where the detection and initialization of the serial port address is done in the zImage code, and the kernel proper simply hope for the best by simply relying on some leftovers in memory from zImage to keep on using the serial console. You can bypass this by hardcoding the appropriate addresses in arch/arm/mach-omap2/include/mach/debug-macro.S, otherwise running zImage is pretty much mandatory. Nicolas _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
