From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] ARM: Incorrect ROM protection range?
Date: Fri, 25 Feb 2011 07:34:45 +0100 [thread overview]
Message-ID: <4D674D85.40904@free.fr> (raw)
In-Reply-To: <AANLkTi=Sf6J49m9_+kv+ERQpGerezanx+G7KRwTfcJQh@mail.gmail.com>
Hi Po-Yu Chuang,
Le 25/02/2011 03:41, Po-Yu Chuang a ?crit :
> Dear Wolfgang and Albert,
>
> On Fri, Feb 25, 2011 at 4:17 AM, Wolfgang Denk<wd@denx.de> wrote:
>> Dear Albert ARIBAUD,
>>
>> In message<4D66A7CD.9020309@free.fr> you wrote:
>>>
>>>> As far as I can tell, arch/powerpc/lib/board.c ,
>>>> arch/avr32/lib/board.c and examples/standalone/stubs.c actually all
>>>> mean __bss_end, as well as all the start.S files, so this seems to be
>>>> consistently used at least.
>>>
>>> I'd come to the same conclusion on my side. However you don't say how
>>> you would like the change to be done. Would a single commit for renaming
>>> _end into _bss_end and then creating _end after .dynsym be ok for you?
>>
>> Ah, sorry.
>>
>> Well, these are two logically separate things: the first is just a
>> renamer that should basicly result in the very same images built on
>> all systems (which can easily be verified semi-automatically). The
>> second step would be adding _end at the end of the used data area (end
>> of .dynsym) on ARM only.
>
> I don't have the environment to build other platforms, so... does any
> of you please to provide such patches?
I suggest you do the changes for all of U-Boot and test them on your
specific board, then submit the patchset and Cc: all architecture
custodians, who will run tests on their respective architectures.
<http://www.denx.de/wiki/U-Boot/Patches> will give you all info on
preparing and sending patches -- remember that's a two-patch set. IMO
you don't necessarily need a cover letter as long as each patch has a
clear commit message.
<http://www.denx.de/wiki/U-Boot/Custodians> will give you the list of
all custodians; you can pick the architecture ones there.
All this, of course, if Wolfgang agrees to this suggestion.
Amicalement,
--
Albert.
next prev parent reply other threads:[~2011-02-25 6:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 6:06 [U-Boot] ARM: Incorrect ROM protection range? Po-Yu Chuang
2011-02-24 6:52 ` Albert ARIBAUD
2011-02-24 7:07 ` Wolfgang Denk
2011-02-24 7:11 ` Po-Yu Chuang
2011-02-24 7:33 ` Heiko Schocher
2011-02-24 7:40 ` Po-Yu Chuang
2011-02-24 8:07 ` Albert ARIBAUD
2011-02-24 9:39 ` Wolfgang Denk
2011-02-24 11:58 ` Albert ARIBAUD
2011-02-24 12:58 ` Po-Yu Chuang
2011-02-24 13:13 ` Albert ARIBAUD
2011-02-24 13:41 ` Wolfgang Denk
2011-02-24 16:01 ` Albert ARIBAUD
2011-02-24 18:38 ` Wolfgang Denk
2011-02-24 18:47 ` Albert ARIBAUD
2011-02-24 20:17 ` Wolfgang Denk
2011-02-25 2:41 ` Po-Yu Chuang
2011-02-25 6:34 ` Albert ARIBAUD [this message]
2011-02-25 7:15 ` Wolfgang Denk
2011-02-25 8:00 ` Po-Yu Chuang
2011-03-01 8:31 ` Po-Yu Chuang
2011-03-01 12:22 ` Albert ARIBAUD
2011-03-02 2:56 ` Po-Yu Chuang
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=4D674D85.40904@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 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.