From: Aneesh V <aneesh@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: Add option to disable code relocation
Date: Tue, 07 Feb 2012 12:55:24 +0530 [thread overview]
Message-ID: <4F30D1E4.5000902@ti.com> (raw)
In-Reply-To: <CA+M6bXmE2NSUy8qJADvvH4ESGDYpw9psgyFThCG=E_dSpUwnTw@mail.gmail.com>
On Monday 06 February 2012 08:19 PM, Tom Rini wrote:
> On Mon, Feb 6, 2012 at 1:43 AM, Graeme Russ<graeme.russ@gmail.com> wrote:
>> Hi Wolfgang,
>>
>> On 02/06/2012 06:51 PM, Wolfgang Denk wrote:
>>> Dear Graeme Russ,
>>>
>>> In message<CALButC+==qGs5EaAHtQqU4zEjqvg-3187eWaqU-fv3dWp5QQ7w@mail.gmail.com> you wrote:
>>>>
>>>> I think the immediate focus should be on centralising the init sequence
>>>> processing into /common/init.c and then bringing the new'initcall'
>>>> architecture online
>>>
>>> Agreed.
>>>
>>>> Once these have been done, any board can just specific:
>>>>
>>>> SKIP_INIT(RELOC)
>>>
>>> I will probably object to his, too - for the same reasons.
>>
>> Considering this is a 'free' artefact of how the init sequence functions,
>> and that it is board specific and totally non-invasive for anyone else
>> (i.e. no ugly ifdef's anywhere else in the code) I'm surprised you would
>> object...
>
> To pick up Wolfgang's argument, but why do we want to skip relocation?
> You can debug through it, it's documented (official wiki has GDB,
> over in TI-land, the wiki page for CCS has the bits for doing it in
> that Eclipse-based env, other debuggers I'm sure have a similar "now
> add symbols at this offset from link" option) and the end result makes
> it very easy for end-users to break their world (default kernel load
> addrs being where U-Boot would be).
Why do all that circus if it's not adding any value for a given
platform. Also, in the previous thread on this I had pointed out a
specific case where this was hurting us. On a slow FPGA platform the
delay due to the relocation was getting magnified and un-necessarily
wasting our time.
best regards,
Aneesh
next prev parent reply other threads:[~2012-02-07 7:25 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-05 6:44 [U-Boot] [PATCH] arm: Add option to disable code relocation Simon Glass
2012-02-05 7:39 ` Mike Frysinger
2012-02-05 12:05 ` Marek Vasut
2012-02-05 20:38 ` Mike Frysinger
2012-02-05 21:40 ` Simon Glass
2012-02-05 22:44 ` Wolfgang Denk
2012-02-05 23:23 ` Graeme Russ
2012-02-05 23:32 ` Simon Glass
2012-02-05 23:37 ` Graeme Russ
2012-02-05 23:41 ` Simon Glass
2012-02-05 23:46 ` Graeme Russ
2012-02-07 9:52 ` Graeme Russ
2012-02-06 7:51 ` Wolfgang Denk
2012-02-06 8:43 ` Graeme Russ
2012-02-06 14:49 ` Tom Rini
2012-02-06 19:27 ` Mike Frysinger
2012-02-06 19:46 ` Tom Rini
2012-02-06 20:25 ` Graeme Russ
2012-02-07 6:41 ` Dirk Behme
2012-02-07 23:23 ` Wolfgang Denk
2012-02-07 23:28 ` Graeme Russ
2012-02-07 23:36 ` Wolfgang Denk
2012-02-07 23:48 ` Graeme Russ
2012-02-08 6:42 ` Dirk Behme
2012-02-08 6:51 ` Dirk Behme
2012-02-08 7:12 ` Simon Glass
2012-02-08 7:16 ` Dirk Behme
2012-02-08 22:05 ` Graeme Russ
2012-02-09 3:38 ` Graeme Russ
2012-02-09 18:30 ` Simon Glass
2012-02-08 14:03 ` Wolfgang Denk
2012-02-06 21:17 ` Albert ARIBAUD
2012-02-06 22:24 ` Wolfgang Denk
2012-02-07 6:51 ` Dirk Behme
2012-02-07 7:25 ` Aneesh V [this message]
2012-02-05 23:32 ` Simon Glass
2012-02-05 12:05 ` Marek Vasut
2012-02-05 18:54 ` 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=4F30D1E4.5000902@ti.com \
--to=aneesh@ti.com \
--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