Il 21/03/2011 17:32, Luca Ceresoli ha scritto: ... >>> --- a/boards.cfg >>> +++ b/boards.cfg >>> @@ -117,6 +117,7 @@ omap3_pandora arm armv7 >>> pandora - >>> igep0020 arm armv7 igep0020 >>> isee omap3 >>> igep0030 arm armv7 igep0030 >>> isee omap3 >>> am3517_evm arm armv7 am3517evm >>> logicpd omap3 >>> +omap3_cps arm armv7 cps >>> comelit omap3 >>> omap3_zoom1 arm armv7 zoom1 >>> logicpd omap3 >>> omap3_zoom2 arm armv7 zoom2 >>> logicpd omap3 >>> omap3_beagle arm armv7 beagle >>> ti omap3 >> >> Please name your board just "cps" (or chose a better name). There >> shall be no SoC-prefix in the board names. > > Will be called dig297 in v2.
Well, not so fast. The board is named OMAP3_CPS in the ARM Linux Machine Registry (http://www.arm.linux.org.uk/developer/machines/list.php?id=2751), which is reflected in mach-types.h. I don't know how exactly the registry info is used throughout U-Boot, and I didn't find documentation about it. Am I supposed to rename the board in the registry, then wait for mach-types to be updated in U-Boot before submitting a new patch? Or can I live with the current name in mach-types and rename elsewhere? Thanks, Luca _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot