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. Texas Instruments X-Loader 1.41 (Apr 19 2010 - 13:31:11) mmc read: Invalid size Starting OS Bootloader from MMC/SD1 ... U-Boot 1.1.4-g9e955085-dirty (Nov 19 2009 - 13:01:21) Load address: 0x80e80000 DRAM: 512 MB Flash: 0 kB *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Hit any key to stop autoboot: 0 OMAP44XX SDP # setenv bootargs 'root=/dev/mmcblk1p2 rw mem=512M console=ttyO2,115200n8 rootdelay=2' OMAP44XX SDP # mmcinit 0 OMAP44XX SDP # fatload mmc 0 0x80300000 uImage-test mmc read: Invalid size 1843088 bytes read OMAP44XX SDP # bootm 80300000 ## Booting image at 80300000 ... Image Name: Linux-2.6.37+ Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1843024 Bytes = 1.8 MB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. X-Loader hangs -- 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
