From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] mxs-bootloader: Barebox entry point symbol changed in 2012.08
Date: Fri, 19 Oct 2012 10:01:11 +0200 [thread overview]
Message-ID: <508108C7.3000407@free-electrons.com> (raw)
In-Reply-To: <50805E2A.1010308@mind.be>
Hi Arnout,
Le 18/10/2012 21:53, Arnout Vandecappelle a ?crit :
> On 18/10/12 10:02, Maxime Ripard wrote:
>> Signed-off-by: Maxime Ripard<maxime.ripard@free-electrons.com>
>> ---
>> boot/mxs-bootlets/barebox_ivt.bd | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/boot/mxs-bootlets/barebox_ivt.bd
>> b/boot/mxs-bootlets/barebox_ivt.bd
>> index e02ddd6..0c67e9c 100644
>> --- a/boot/mxs-bootlets/barebox_ivt.bd
>> +++ b/boot/mxs-bootlets/barebox_ivt.bd
>> @@ -28,7 +28,7 @@ section (0) {
>> //----------------------------------------------------------
>>
>> load barebox;
>> - load ivt (entry = barebox:exception_vectors)> 0x8000;
>> + load ivt (entry = barebox:start)> 0x8000;
>> hab call 0x8000;
>>
>> }
>
> Shouldn't this somehow depend on the selected barebox version then?
Well, I thought so at first, but since the next barebox release is in
less than two weeks now, and the 2012.07 (the only one we support that
is still using exception_vectors symbol) will be removed at that time,
so I finally gave up to write that code, just to have it removed/be
irrelevant in two weeks.
Maxime
--
Maxime Ripard, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-10-19 8:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 8:02 [Buildroot] [PATCH] mxs-bootloader: Barebox entry point symbol changed in 2012.08 Maxime Ripard
2012-10-18 19:53 ` Arnout Vandecappelle
2012-10-19 8:01 ` Maxime Ripard [this message]
2012-10-19 9:00 ` Peter Korsgaard
2012-10-19 9:41 ` Maxime Ripard
2012-11-17 8:07 ` Maxime Ripard
2012-11-17 8:32 ` Peter Korsgaard
2012-11-17 8:33 ` Peter Korsgaard
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=508108C7.3000407@free-electrons.com \
--to=maxime.ripard@free-electrons.com \
--cc=buildroot@busybox.net \
/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.