in u-boot, any problem with references to OMAP34XX?

GoogleGroups
1

just perusing the u-boot code, and in board/ti/beagle, we find:

$ 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

  note the references not to OMAP35XX but OMAP34XX. obviously,
that works -- referring to OMAP34XX macro values -- but is there any
possibility that that will eventually cause a conflict? just curious.

rday

2

Shouldn't be a problem for OMAP3 series or family of processors. It
might impact AM series a bit as it depends on OMAP3 for few things.
But we can clean things up as we move forward.

Regards,
Khasim

3

ok, just thought i'd ask since almost all references in the u-boot
tree are to OMAP34XX, even for OMAP3530-based boards.

rday