From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 0/4] mvebu: Make 2nd-stage booting possible
Date: Tue, 28 Feb 2017 17:06:37 +0100 [thread overview]
Message-ID: <20170228160637.gtijba6fgvjxvx3p@pengutronix.de> (raw)
In-Reply-To: <20170228065947.q26xmiy5xyph3mnz@pengutronix.de>
On Tue, Feb 28, 2017 at 07:59:47AM +0100, Sascha Hauer wrote:
> On Sat, Feb 25, 2017 at 09:52:38PM +0100, Uwe Kleine-König wrote:
> > Hello,
> >
> > one specialty of mvebu is that it has a movable register window. Its
> > base address is configured within this register range, so there is no
> > way to find out the current position. The BootROM leaves this window at
> > 0xd0000000, however it is beneficial to move it further to the end of
> > the address range (usually 0xf1000000) to benefit from more continuous
> > RAM. For this reason one of the first things that barebox does it to
> > move the window accordingly. If however barebox is loaded as a second
> > stage image this results in a crash as the register base address
> > register is already moved.
> >
> > This series implements that the called image gets the base address from
> > the barebox header. It defaults to 0xd0000000 which is right for the
> > (unaware) BootROM and when barebox jumps into such an image the register
> > position is passed accordingly.
>
> This makes the 2nd stage images unnecessary, right? Can you remove them
> from images/Makefile.mvebu?
I thought about that already, too, but they are still necessary when you
convert from U-Boot to barebox or upgrade from an older barebox. So I
think keeping them for now makes sense.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2017-02-28 16:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-25 20:52 Uwe Kleine-König
2017-02-25 20:52 ` [PATCH 1/4] mvebu: get initial position of register window from image header Uwe Kleine-König
2017-02-25 20:52 ` [PATCH 2/4] filetype: Add image type for boot images used on Armada 370 and XP Uwe Kleine-König
2017-02-25 20:52 ` [PATCH 3/4] kwbimage_v1: add support to boot a mvebu image Uwe Kleine-König
2017-02-25 20:52 ` [PATCH 4/4] mvebu: netgear-rn2120: make use of mvebu_get_initial_int_reg_base Uwe Kleine-König
2017-02-28 6:59 ` [PATCH 0/4] mvebu: Make 2nd-stage booting possible Sascha Hauer
2017-02-28 16:06 ` Uwe Kleine-König [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=20170228160637.gtijba6fgvjxvx3p@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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