From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: Re: shouldn't asm-generic/barebox.lds.h be arch-independent?
Date: Sun, 18 Nov 2012 13:31:06 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.02.1211181326250.704@oneiric> (raw)
In-Reply-To: <alpine.DEB.2.02.1211181240360.32651@oneiric>
there is one more oddity(?) with the way the linker "lds" files are
set up. if i read this correctly (and i could be wrong), here's
arch/x86/lib/barebox.lds.S:
#undef i386
#include <asm-generic/barebox.lds.h>
which gets us to that included file, which contains:
#if defined CONFIG_ARCH_IMX25 || \
defined CONFIG_ARCH_IMX35 || \
defined CONFIG_ARCH_IMX51 || \
defined CONFIG_ARCH_IMX53 || \
defined CONFIG_ARCH_IMX6 || \
defined CONFIG_X86 || \ <-- that will be true, correct?
defined CONFIG_ARCH_EP93XX
#include <mach/barebox.lds.h>
#endif
which finally takes us to
arch/x86/mach-i386/include/mach/barebox.lds.h, which is nothing more
than a collection of macro definitions. there's no "pre-image"
content to be incorporated into the final image -- it's just
preprocessor content. so why isn't all that simply at the beginning
of the main x86 barebox.lds.S file?
or am i missing something?
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
next prev parent reply other threads:[~2012-11-18 18:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-18 17:52 Robert P. J. Day
2012-11-18 18:21 ` Antony Pavlov
2012-11-18 18:24 ` Robert P. J. Day
2012-11-18 18:31 ` Robert P. J. Day [this message]
2012-11-19 8:32 ` Sascha Hauer
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.1211181326250.704@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