On Thu, Jan 06, 2011 at 05:08:05PM +0000, Russell King - ARM Linux wrote:
> This looks like something's rather broken on OMAP4 too - even with the
> DEBUG_LL stuff enabled and my printk hack, I get nothing more, same with
> vanilla 2.6.37. So, no OMAP platform I have seems to be usable with
> 2.6.37...
>
> It's worth noting that the kernel which was originally supplied with the
> board works fine (2.6.31-00682-g49ab82a-dirty) with this uboot, as have
> previous kernels I've built.
>
> Is there yet an updated uboot for this platform which works with ethernet,
> and which has the uboot environment saving implemented? Or are we stuck
> with having to catch uboot before it runs the default settings and paste
> the commands in each time? Also, if possible please extend the default
> timeout - I can only just get from the board to the terminal to stop it
> booting the default environment.
>
> For TI folk: it may be an idea to make X-loader say why it's hanging so
> that we know what is going on.
And another thing: turning on DEBUG in the decompressor breaks the build
on OMAP:
`.data' referenced in section `.text' of arch/arm/boot/compressed/head.o: defined in discarded section `.data' of arch/arm/boot/compressed/head.o
`.data' referenced in section `.text' of arch/arm/boot/compressed/head.o: defined in discarded section `.data' of arch/arm/boot/compressed/head.o
Is there a reason why this:
.pushsection .data
omap_uart_phys: .word 0
omap_uart_virt: .word 0
omap_uart_lsr: .word 0
.popsection
can't be in the BSS section?
With that fixed, and a debug version of the decompressor built, when I
load and run this I get the same results - without the debugging output.
If I put additional debugging earlier in the decompressor, I don't see
it decompressing the kernel at all.
Therefore, I believe the debugging address calculation stuff in
arch/arm/mach-omap2/include/mach/debug-macros.S to be rather broken,
causing an abort when it tries to access the serial port.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
