Greetings,

The attached patch fixes OMAP1610 board builds so that the correct machine number is setup based on the board target config file. This allows recent OMAP linux-2.6 kernels to boot on OMAP1610 based boards since recent OMAP Linux-2.6 kernels now expect the correct and official machine number to be passed in for these OMAP1610 based boards. If the correct machine number is not passed in to recent OMAP Linux-2.6 kernels, then the Linux kernel will either malfunction or hang due to selection of the wrong machine specific support code due to wrong machine number passed into the kernel by U-Boot.

I've tested U-boot on an OMAP1610 H2 board with recent OMAP Linux-2.6 kernel with this patch applied - it works ok for me.

There is in fact one build failure for this MAKEALL test case:

CROSS_COMPILE=/opt/montavista/pro/devkit/arm/v4t_le/bin/arm_v4t_le- ./MAKEALL arm

Here's the build failure for the above test case:

Configuring for xsengine board... cc1: error: unrecognized option `-fdisassemble-all' cc1: error: unrecognized option `-fdisassemble-all' cc1: error: unrecognized option `-fdisassemble-all' make[1]: *** [.depend] Error 1 make: *** [board/xsengine/libxsengine.a] Error 2 /opt/montavista/pro/devkit/arm/v4t_le/bin/arm_v4t_le-size: u-boot: No such file or directory

I did not perform a test build prior to applying this fix. But I'm confident the above build failure is not a regression due to this patch. Perhaps this is merely a problem with my tool chain? However I'm indifferent about that failure and do not know or really much care (at the moment : ) if it exists for other tool chains or not.

-- Regards, George