From: Robert P. J. Day <rpjday@crashcourse.ca>
To: u-boot@lists.denx.de
Subject: [U-Boot] possible typo in beagle identification?
Date: Fri, 20 Nov 2009 11:07:00 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0911201100290.17633@localhost> (raw)
at the risk of embarrassing myself yet again, am i misreading the
macro that defines and tests for a beagle board?
$ grep -rw CONFIG.*OMAP3.*BEAGLE *
include/configs/omap3_beagle.h:#define CONFIG_OMAP3_BEAGLE 1 /* working with BEAGLE */
include/asm-arm/mach-types.h:#ifdef CONFIG_MACH_OMAP3_BEAGLE
$
in short, the config file defines CONFIG_OMAP3_BEAGLE, while the
mach-types.h file *tests* for CONFIG_MACH_OMAP3_BEAGLE. how exactly
does that work? the more i read, the confuseder i get.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
reply other threads:[~2009-11-20 16:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.LFD.2.00.0911201100290.17633@localhost \
--to=rpjday@crashcourse.ca \
--cc=u-boot@lists.denx.de \
/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