From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH 0/4] mvebu: Make 2nd-stage booting possible
Date: Sat, 25 Feb 2017 21:52:38 +0100 [thread overview]
Message-ID: <20170225205242.18106-1-u.kleine-koenig@pengutronix.de> (raw)
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.
Best regards
Uwe
Uwe Kleine-König (4):
mvebu: get initial position of register window from image header
filetype: Add image type for boot images used on Armada 370 and XP
kwbimage_v1: add support to boot a mvebu image
mvebu: netgear-rn2120: make use of mvebu_get_initial_int_reg_base
arch/arm/Kconfig | 1 +
arch/arm/boards/netgear-rn2120/lowlevel.c | 12 ++--
arch/arm/mach-mvebu/Makefile | 1 +
arch/arm/mach-mvebu/common.c | 6 +-
.../arm/mach-mvebu/include/mach/barebox-arm-head.h | 54 ++++++++++++++
arch/arm/mach-mvebu/include/mach/common.h | 17 +++++
arch/arm/mach-mvebu/kwbootimage.c | 84 ++++++++++++++++++++++
common/filetype.c | 8 +++
include/filetype.h | 1 +
9 files changed, 176 insertions(+), 8 deletions(-)
create mode 100644 arch/arm/mach-mvebu/include/mach/barebox-arm-head.h
create mode 100644 arch/arm/mach-mvebu/kwbootimage.c
--
2.11.0
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2017-02-25 20:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-25 20:52 Uwe Kleine-König [this message]
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
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=20170225205242.18106-1-u.kleine-koenig@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=barebox@lists.infradead.org \
/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