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

7 views
Skip to first unread message

Robert P. J. Day

unread,
Nov 17, 2009, 2:41:56 AM11/17/09
to BeagleBoard list

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
--

========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA

Linux Consulting, Training and Kernel Pedantry.

Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================

Syed Mohammed, Khasim

unread,
Nov 17, 2009, 3:20:26 AM11/17/09
to beagl...@googlegroups.com
On Tue, Nov 17, 2009 at 1:11 PM, Robert P. J. Day <rpj...@crashcourse.ca> wrote:
>
>  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.
>
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

Robert P. J. Day

unread,
Nov 17, 2009, 3:33:55 AM11/17/09
to beagl...@googlegroups.com
ok, just thought i'd ask since almost all references in the u-boot
tree are to OMAP34XX, even for OMAP3530-based boards.
Reply all
Reply to author
Forward
0 new messages