From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 6/7] arm: add a common .lds link script
Date: Tue, 21 Feb 2012 20:52:16 +0100 [thread overview]
Message-ID: <4F43F5F0.30409@aribaud.net> (raw)
In-Reply-To: <CAPnjgZ2yFbsMLxk_jXAvXAdN0a3uBMEPs=mBh8f7MZj5UJLehg@mail.gmail.com>
Hi Simon,
Le 21/02/2012 18:02, Simon Glass a ?crit :
>>> + . = ALIGN(4);
>>
>>
>> This "ALIGN(4)" is what upsets my edminiv2 build and makes it not
>> binary-identical. It is not in the current arm926ejs liner script. I will
>> check if adding it to the current arm926ejs script produces a working and
>> binary-identical u-boot.
>
> OK, but realistically we copy a word at a time (at least) and the
> .rel.dyn region is going to be word-aligned I think. All we are doing
> here is making sure that the image ends on a word boundary, which
> seems reasonable to me.
>
> In other words, I would like the __image_copy_start and
> __image_copy_end symbols to be word-aligned.
I understand the requirement and agree to it -- only, it seems to me it
is already fulfilled in the current lds files, so I still fail to see
what breaks 'near binary identity'.
Amicalement,
--
Albert.
next prev parent reply other threads:[~2012-02-21 19:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 6:17 [U-Boot] [PATCH v3 6/7] arm: add a common .lds link script Simon Glass
2012-02-21 6:17 ` [U-Boot] [PATCH v3 7/7] arm: Use common .lds file where possible Simon Glass
2012-02-21 13:11 ` [U-Boot] [PATCH v3 6/7] arm: add a common .lds link script Albert ARIBAUD
2012-02-21 13:12 ` Albert ARIBAUD
2012-02-21 17:02 ` Simon Glass
2012-02-21 19:52 ` Albert ARIBAUD [this message]
2012-02-21 20:14 ` Simon Glass
[not found] ` <4F4D462D.1010403@aribaud.net>
2012-03-07 6:09 ` Simon Glass
2012-02-21 20:24 ` Marek Vasut
2012-02-23 13:27 ` Simon Glass
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=4F43F5F0.30409@aribaud.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.