From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] [NEXT] arm926ejs: reduce code size with -msingle-pic-base
Date: Fri, 24 Sep 2010 19:13:23 +0200 [thread overview]
Message-ID: <4C9CDC33.3000901@free.fr> (raw)
In-Reply-To: <4C9CD8D2.7040306@dawes.za.net>
Le 24/09/2010 18:58, Rogan Dawes a ?crit :
> On 2010/09/24 6:45 PM, Rogan Dawes wrote:
>> On 2010/09/24 7:47 AM, Albert ARIBAUD wrote:
>>
>>> On a side note, I do not know of a clear general definition of
>>> 'bisectability', which means I could break it yet again unkonwingly. Can
>>> you (or anyone, actually :) ) point me to a, or even the, standard
>>> definition of 'bisectable' and, if that has a specific meaning, of
>>> 'fully bisectable'?
>
> Here's a decent LWN.net article on the topic:
>
> http://lwn.net/Articles/317154/
>
> Rogan
Thanks Rogan.
Actually I do know the git bisect command, having had to use it to track
a boot issue in recent linux kernel versions; I should have made it
clear that I was looking specifically for the meaning of 'bisectable' --
which you have clarified, thanks again.
So in this specific case, I guess what I should do is look up Heiko's
patch series, see which arm926 boards it makes relocation-capable, and
apply the .lds fx to those. The other arm926 boards, which were left
untouched by Heiko, would not build with his patches anyway, so there is
no real point in fixing them yet. Or is there?
So unless some strong disagreement is voiced, I'll prepare a V3 patch
set which will be V2 + possible fixes stemming from Heiko's and Ben's
test feedback + fixes to the .lds of boards which are made relocation
capable in Heiko's patch series.
Amicalement,
--
Albert.
next prev parent reply other threads:[~2010-09-24 17:13 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 13:57 [U-Boot] [PATCH 1/2] [NEXT] arm: change relocation flag from -fPIC to -fPIE Albert Aribaud
2010-09-22 13:57 ` [U-Boot] [PATCH 2/2] [NEXT] arm926ejs: reduce code size with -msingle-pic-base Albert Aribaud
2010-09-22 18:05 ` Ben Gardiner
2010-09-22 19:07 ` Albert ARIBAUD
2010-09-22 20:51 ` Ben Gardiner
2010-09-22 21:36 ` Albert ARIBAUD
2010-09-22 22:07 ` Albert ARIBAUD
2010-09-23 14:44 ` Ben Gardiner
2010-09-23 15:13 ` Albert ARIBAUD
2010-09-23 15:35 ` Ben Gardiner
2010-09-23 16:53 ` Ben Gardiner
2010-09-23 16:37 ` Ben Gardiner
2010-09-23 17:04 ` Albert ARIBAUD
2010-09-23 21:13 ` Ben Gardiner
2010-09-23 21:30 ` Albert ARIBAUD
2010-09-24 13:38 ` Ben Gardiner
2010-09-24 16:08 ` Albert ARIBAUD
2010-09-22 20:30 ` Wolfgang Denk
2010-09-22 20:55 ` Ben Gardiner
2010-09-22 21:11 ` Wolfgang Denk
2010-09-22 21:33 ` Ben Gardiner
2010-09-23 7:12 ` Heiko Schocher
2010-09-23 8:05 ` Albert ARIBAUD
2010-09-23 10:08 ` Heiko Schocher
2010-09-23 12:45 ` Albert ARIBAUD
2010-09-24 5:11 ` Heiko Schocher
2010-09-24 5:47 ` Albert ARIBAUD
2010-09-24 16:45 ` Rogan Dawes
2010-09-24 16:58 ` Rogan Dawes
2010-09-24 17:13 ` Albert ARIBAUD [this message]
2010-09-22 18:05 ` [U-Boot] [PATCH 1/2] [NEXT] arm: change relocation flag from -fPIC to -fPIE Ben Gardiner
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=4C9CDC33.3000901@free.fr \
--to=albert.aribaud@free.fr \
--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