From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: Allow u-boot to run from offset base address
Date: Wed, 11 Jun 2014 08:45:58 +0200 [thread overview]
Message-ID: <E1WucIJ-0001Lv-5Q@janus> (raw)
In-Reply-To: <20140611044928.25167382C16@gemini.denx.de>
Hi Wolfgang,
On Wed, 11 Jun 2014 06:49:28 +0200, Wolfgang Denk <wd@denx.de> wrote:
> Dear Steve,
>
> In message <53979199.5010100@broadcom.com> you wrote:
> >
> > OK - I think that one of the alternate proposals would be to
> > conditionally reserve a "32 byte block" prior to the _start symbol (in
> > "arch/arm/cpu/armv8/start.S") which would then be filled in by a
> > post-processing step... This could be implemented by:
>
> Yes, that illustrates the idea. However, this implementation suffers
> from the use of an #ifdef where none is actually needed. Instead, you
> can create your own source file which defines the header; this could
> be then even in it's own segment, say:
>
> your_header.c:
>
> struct your_header {
> u_int32[8];
> } your_header __attribute__ ((__section__ (".your_hdr")));
>
> All that is needed then is to make the linker place this segment in
> front of the text segment.
>
> This avoids an ugly #ifdef, and also modifications in the common code.
Agreed and seconded.
Plus, using a dedicated 'header' section and a separate C source file
for the header makes it automatic that if no input 'header' section
were provided then no output 'header' section would be emitted; IOW,
we would not need two different linker scripts, a single one would be
useable for both 'headerless' and 'headerful' image types.
Also, the alignment constraint should be configurable.
> Best regards,
>
> Wolfgang Denk
Amicalement,
--
Albert.
next prev parent reply other threads:[~2014-06-11 6:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 22:05 [U-Boot] [PATCH] arm: Allow u-boot to run from offset base address Darwin Rambo
2014-05-14 22:41 ` Jeroen Hofstee
2014-05-15 14:21 ` Darwin Rambo
2014-05-15 15:21 ` Wolfgang Denk
2014-05-15 16:07 ` Darwin Rambo
2014-05-15 19:19 ` Wolfgang Denk
2014-05-26 9:50 ` Albert ARIBAUD
2014-05-26 16:11 ` Darwin Rambo
2014-06-02 7:26 ` Albert ARIBAUD
2014-06-03 0:37 ` Darwin Rambo
2014-06-09 10:23 ` Albert ARIBAUD
2014-06-09 20:45 ` Steve Rae
2014-06-09 20:56 ` Jeroen Hofstee
2014-06-10 5:16 ` Albert ARIBAUD
2014-06-10 17:56 ` Steve Rae
2014-06-10 18:13 ` Wolfgang Denk
2014-06-10 19:38 ` Steve Rae
2014-06-10 20:35 ` Wolfgang Denk
2014-06-10 23:15 ` Steve Rae
2014-06-11 4:49 ` Wolfgang Denk
2014-06-11 6:45 ` Albert ARIBAUD [this message]
2014-06-11 18:56 ` Steve Rae
2014-06-11 21:16 ` Wolfgang Denk
2014-06-25 12:52 ` Albert ARIBAUD
2014-06-10 21:20 ` Albert ARIBAUD
2014-06-11 0:14 ` Steve Rae
2014-06-11 5:02 ` Wolfgang Denk
2014-06-11 4:38 ` Wolfgang Denk
2014-05-15 4:26 ` Wolfgang Denk
2014-05-15 14:16 ` Darwin Rambo
2014-05-15 15:16 ` Wolfgang Denk
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=E1WucIJ-0001Lv-5Q@janus \
--to=albert.u.boot@aribaud.net \
--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