From: Sascha Hauer <s.hauer@pengutronix.de>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: Barebox List <barebox@lists.infradead.org>,
Thomas Huth <thuth@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>,
qemu-arm <qemu-arm@nongnu.org>
Subject: Re: barebox on Canon A1100
Date: Fri, 4 Jan 2019 09:17:41 +0100 [thread overview]
Message-ID: <20190104081741.mxdgg4dwm4l5s4ki@pengutronix.de> (raw)
In-Reply-To: <20190104015641.e6d525f098c5e272694faa62@gmail.com>
On Fri, Jan 04, 2019 at 01:56:41AM +0300, Antony Pavlov wrote:
> Hi Sascha!
>
> I have some good news and some bad news.
>
> First the good news.
>
> Barebox was used for Day 18 of QEMU 2018 advent (https://www.qemu-advent-calendar.org/2018/).
>
> Here is a quote:
>
> > This is an image for QEMU's emulated Canon A1100 Arm machine:
> > Play 2048 in the Barebox firmware environment.
Hey nice :)
>
> The bad news.
>
> Current master branch barebox for Canon A1100 does not work under qemu,
> barebox v2017.02.0 was used for qemu advent.
>
> Thomas Huth reported the problem in the qemu-devel mailing
> list two months ago. Please see https://www.mail-archive.com/qemu-devel@nongnu.org/msg571887.html
> for details.
>
> The commit a43e2bbc468a71 breaks barebox for Canon A1100:
>
> > commit a43e2bbc468a71fb8825e8acafb7fac7ad7c6dad
> > Author: Sascha Hauer <s.hauer@pengutronix.de>
> > Date: Wed Mar 7 10:04:07 2018 +0100
> >
> > ARM: return positive offset in get_runtime_offset()
>
> Any suggestion?
Yes, try again with a recent barebox. There was a bug in this commit that
should be fixed with the following:
| commit 0230365df6601cd561c9e3e368c96222076ec9f5
| Author: Sascha Hauer <s.hauer@pengutronix.de>
| Date: Wed Dec 12 08:55:31 2018 +0100
|
| ARM: fix setup_c when runtime offset is != 0
|
| The runtime offset has to be added to the memcpy source address and
| substracted from the return address. This should have been changed in
| a43e2bbc46 which changed from returning the negative runtime offset
| into changing the positive runtime offset. Instead a43e2bbc46 only
| changed a zero substraction ("subs r4, r0, #0") into a zero addition
| ("adds r4, r0, #0") which was used as a equal to zero test and changed
| nothing. This part is reverted here.
|
| Fixes wrong copy / return locations when setup_c is called with
| different runtime and link addresses.
|
| fixes: a43e2bbc46 ("ARM: return positive offset in get_runtime_offset()")
|
| Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2019-01-04 8:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 22:56 Antony Pavlov
2019-01-04 8:17 ` Sascha Hauer [this message]
2019-01-04 10:54 ` Antony Pavlov
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=20190104081741.mxdgg4dwm4l5s4ki@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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