From: Sascha Hauer <s.hauer@pengutronix.de>
To: perachet7@gmail.com
Cc: barebox@lists.infradead.org
Subject: Re: rk3188 (radxa rock pro) boot failure w/ barebox 2018-04 and later
Date: Mon, 17 Sep 2018 09:30:30 +0200 [thread overview]
Message-ID: <20180917073030.GH7949@pengutronix.de> (raw)
In-Reply-To: <1597963.4YffofffW7@think-future.de>
On Thu, Sep 13, 2018 at 01:18:54PM +0200, perachet7@gmail.com wrote:
> Hey list,
>
> Between 2018-04 and 2018-05 tar release, barebox stops booting on rk3188
> (radxa rock pro).
>
> A git bisect reveals (see end of mail for commit detail):
> first bad commit: [2a94e821ba2e64890ac47b9ba177c7b6585b23be] ARM: For
> relocatable image force TEXT_BASE 0x0.
>
> As was suggested on #barebox, I tried setting TEXT_BASE=0x10 at this commit
> but it's a no fix.
>
> It is however booting even later releases if the trailing "if !RELOCATABLE" is
> removed. I have yet to have a deeper look at the code modified by
> HAVE_CONFIGURABLE_TEXT_BASE and RELOCATABLE.
>
> Furthermore, it seems the commit itself is only triggering a boot failure. The
> proper code causing it is probably hiding someplace else.
>
> Any direction, ideas or hints given is appreciated.
I just sent a patch. Could you please give it a test?
Thanks
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
prev parent reply other threads:[~2018-09-17 7:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 11:18 perachet7
2018-09-13 12:37 ` Sam Ravnborg
2018-09-14 18:20 ` Панов Андрей
2018-09-17 6:37 ` Sascha Hauer
[not found] ` <8463281536949204@think-future.de>
2018-09-14 21:41 ` perachet7
[not found] ` <20180913123746.GA18653@think-future.de>
2018-09-14 21:33 ` perachet7
2018-09-17 7:30 ` Sascha Hauer [this message]
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=20180917073030.GH7949@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=perachet7@gmail.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