From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] [PATCH V2] arm: arm926ejs: use ELF relocations
Date: Tue, 05 Oct 2010 15:36:49 +0200 [thread overview]
Message-ID: <4CAB29F1.2050906@free.fr> (raw)
In-Reply-To: <4CAB25B8.10207@emk-elektronik.de>
Le 05/10/2010 15:18, Reinhard Meyer a ?crit :
> Dear Albert ARIBAUD,
>> Le 05/10/2010 13:17, Reinhard Meyer a ?crit :
>>> Dear All ;)
>>>>> Umm... is my understanding correct that we can drop the whole
>>>>> CONFIG_SYS_ARM_WITHOUT_RELOC stuff then, too?
>>>>
>>>> I believe we're just changing the relocation solution, but we're not
>>>> changing the overall strategy regarding CONFIG_SYS_ARM_WITHOUT_RELOC.
>>>
>>> We should not forget that right now, the "ELF" method uses 8 byte entries
>>> to relocate, compared to 4 byte entries with the "GOT" method. We
>>> should not proceed too fast here, the "thought about" tool to squeeze
>>> down
>>> the relocation information should not be completely forgotten...
>>>
>>> Otherwise even more boards would need to change their mtd partitioning ;)
>>>
>>> And I am not too happy if I cannot downgrade to the AT91SAM9XE256 anymore
>>> (256K NOR) if the 512K version proves difficult to obtain ;)
>>>
>>> Reinhard
>>
>> I still think a configuration option to choose between relocation
>> formats would be useful. It could offer:
>>
>> - pure ELF format (8 bytes per relocation plus .dynsym)
>>
>> ... already there, and then to be done:
>>
>> - unified 32-bit format (half the size of pure ELF)
>>
>> - unified 16-bit delta format (a fourth of the size of pure ELF)
>
> Even an 8-bit delta format is possible:
> use the value of 0x00 to skip forward 256 addresses, other values to patch..
> Assuming that all relocations must be on a 32 bit boundary, the delta values
> could even be multiplied by 4 :)
i can see ASN.1-style variable-length integer encoding creeping around,
just waiting to be invoked thrice. :)
> Best Regards,
> Reinhard
>
> PS: I finished the "C" relocation, but it does not work :(
> having problems with setting the stack or calling of board_init_r(),
> I am not sure. Because of otther work I cannot continue there right now.
> If you want to look at it, I can make a patch.
Please do !
Amicalement,
--
Albert.
next prev parent reply other threads:[~2010-10-05 13:36 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 6:31 [U-Boot] [RFC] [PATCH V2] arm: arm926ejs: use ELF relocations Albert Aribaud
2010-10-05 6:45 ` Wolfgang Denk
2010-10-05 7:05 ` Reinhard Meyer
2010-10-05 7:23 ` Reinhard Meyer
2010-10-05 7:52 ` Reinhard Meyer
2010-10-05 8:33 ` Heiko Schocher
2010-10-05 8:41 ` Albert ARIBAUD
2010-10-05 9:00 ` Heiko Schocher
2010-10-05 9:10 ` Reinhard Meyer
2010-10-05 9:15 ` Heiko Schocher
2010-10-05 9:19 ` Reinhard Meyer
2010-10-05 9:29 ` Heiko Schocher
2010-10-05 9:33 ` Reinhard Meyer
2010-10-05 9:39 ` Reinhard Meyer
2010-10-05 10:11 ` Albert ARIBAUD
2010-10-05 10:36 ` Reinhard Meyer
2010-10-05 10:49 ` Graeme Russ
2010-10-05 11:01 ` Reinhard Meyer
2010-10-05 11:18 ` Albert ARIBAUD
2010-10-05 10:33 ` Albert ARIBAUD
2010-10-05 10:40 ` Wolfgang Denk
2010-10-05 11:10 ` Albert ARIBAUD
2010-10-05 11:17 ` Reinhard Meyer
2010-10-05 11:46 ` Albert ARIBAUD
2010-10-05 13:18 ` Reinhard Meyer
2010-10-05 13:24 ` Graeme Russ
2010-10-05 13:36 ` Albert ARIBAUD [this message]
2010-10-05 14:06 ` Reinhard Meyer
2010-10-05 11:43 ` Wolfgang Denk
2010-10-05 10:20 ` Albert ARIBAUD
2010-10-05 8:27 ` Wolfgang Denk
2010-10-05 8:38 ` Reinhard Meyer
2010-10-05 8:50 ` Albert ARIBAUD
2010-10-05 8:59 ` Reinhard Meyer
2010-10-05 7:07 ` Wolfgang Denk
2010-10-05 7:40 ` Heiko Schocher
2010-10-05 8:32 ` Albert ARIBAUD
2010-10-05 8:02 ` Wolfgang Denk
2010-10-05 9:25 ` Heiko Schocher
2010-10-05 9:32 ` Albert ARIBAUD
2010-10-05 12:07 ` Heiko Schocher
2010-10-05 12:52 ` Heiko Schocher
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=4CAB29F1.2050906@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