Robert P. J. Day wrote: > i asked about this on the beagleboard list but i figure i can ask > here as well. while the beagleboard is based on the OMAP3530, if you > check out board/ti/beagle: > > $ grep OMAP3 * > beagle.c: gd->bd->bi_arch_number = MACH_TYPE_OMAP3_BEAGLE; > beagle.c: gd->bd->bi_boot_params = (OMAP34XX_SDRC_CS0 + 0x100); > beagle.c: struct gpio *gpio5_base = (struct gpio *)OMAP34XX_GPIO5_BASE; > beagle.c: struct gpio *gpio6_base = (struct gpio *)OMAP34XX_GPIO6_BASE; > beagle.h: "OMAP3 Beagle board", > config.mk:# Beagle Board uses OMAP3 (ARM-CortexA8) cpu > $ > > as in, note the references to OMAP34XX macros, not OMAP35XX. and > that's because, in include/configs/omap3_beagle.h, all of the > references seem to be to OMAP34XX, such as: > > /* > * High Level Configuration Options > */ > #define CONFIG_ARMCORTEXA8 1 /* This is an ARM V7 CPU core */ > #define CONFIG_OMAP 1 /* in a TI OMAP core */ > #define CONFIG_OMAP34XX 1 /* which is a 34XX */ > #define CONFIG_OMAP3430 1 /* which is in a 3430 */ > #define CONFIG_OMAP3_BEAGLE 1 /* working with BEAGLE */ > > almost all of the macros under include/asm/arch-omap3 are defined in > terms of OMAP34XX as well and while that may work fine for now, is > there any chance that could cause conflicts down the road?
Due to cross-posting answered at Beagle mailing list: http://groups.google.com/group/beagleboard/browse_thread/thread/5813bff4b4d420c7 Dirk _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
