public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
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 13:10:11 +0200	[thread overview]
Message-ID: <4CAB0793.4000300@free.fr> (raw)
In-Reply-To: <20101005104041.6A5921539A0@gemini.denx.de>

Le 05/10/2010 12:40, Wolfgang Denk a ?crit :
> Dear Albert ARIBAUD,
>
> In message<4CAAFEDD.4060005@free.fr>  you wrote:
>>
>> As for splitting the thing into individual patches, I would like some
>> advice. Obviously a first patch could be the bugfix to the ble/blo
>> issuein existing start.S, and the last patch shall be the change to
>> edminiv2.
>
> Correct.
>
>> My problem is with the essential part: changing only the compile and
>> link options in arm, or changing only the start.S and u-boot.lds in
>> arm926, produces a nonworking, non-buildable, tree. So it would seem
>> that all of this should go in a single patch in order to remain bisectable.
>>
>> However, changing arm without changing other cpus than arm926 would
>> break build on these, so a bisectable change would require a single
>> patch to arm and all its cpus. Seems a bit big for me.
>
> Agreed.
>
> Well, let's split development and testing from the final committing.
>
> I suggest you provide what you can in  single patch, and we put this
> in a separate branch of the git repository.  Heiko and me may then add
> support for the precessors we used for testing, i. e. arm1136 and
> armv7.  Hopefully others will pick up from there for the remaining
> processors.
>
> When committing to mainline (or to u-boot-arm) I can sqash all the
> processor related commits into a single one.

Let me recap to make sure I got things right.

Rather than submitting a patch set for mainline, I'll submit a single 
ELF patch that you will put on a specific branch (let's call it 
elf_reloc here for the sake of clarity)

In order to keep elf_reloc devoted to elf relocation and make it simpler 
for you to squash it back to main, elf_reloc should receive only changes 
which are imperative for elf relocation support.

This means the ble bugfix (changing existing ble's into blo's in all ARM 
start.S files) will be a separate patch to main, coming RSN.

Also, I won't submit changes to edminiv2 on elf_reloc either; that'll 
come on main once elf_reloc is squashed back onto it.

> 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.

> Best regards,
>
> Wolfgang Denk

Amicalement,
-- 
Albert.

  reply	other threads:[~2010-10-05 11:10 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 [this message]
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
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=4CAB0793.4000300@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