mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: confused about "__PBL__" macro and whether it's actually used
Date: Tue, 4 Dec 2012 07:41:04 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1212040735210.5342@oneiric> (raw)


  perusing arch/arm/mach-omap/omap3_generic.c and i noticed that the
initcall "omap3_gpio_init" is apparently invoked by the TI X-loader,
even though it *appears* to be protected by the macro:

#ifndef __PBL__
static int omap3_gpio_init(void)
{
... snip ...
}
coredevice_initcall(omap3_gpio_init);
#endif

  i assume __PBL__ is meant to refer to the "primary bootloader" --
that would be X-loader -- which suggests that that initcall shouldn't
be invoked by the X-loader as long as that macro is being defined
correctly.

  am i misunderstanding something here?  i'm going to check the
makefiles to see if i'm just confused.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2012-12-04 12:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-04 12:41 Robert P. J. Day [this message]
2012-12-04 16:36 ` Jean-Christophe PLAGNIOL-VILLARD
2012-12-04 16:56   ` Robert P. J. Day

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.02.1212040735210.5342@oneiric \
    --to=rpjday@crashcourse.ca \
    --cc=barebox@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox