summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorUwe Kleine-König <u.kleine-koenig@pengutronix.de>2017-06-02 20:22:03 +0200
committerSascha Hauer <s.hauer@pengutronix.de>2017-06-06 09:16:59 +0200
commitba97a1c1365195e5a76c71355fc5e471d92382b7 (patch)
tree309138b11a7c587e7b8d11c64b4238a5af35fdb5
parentc5c50720c5b2999f5cd72430c60a2022d33d5790 (diff)
downloadbarebox-ba97a1c1365195e5a76c71355fc5e471d92382b7.tar.gz
docs: mvebu can do 2nd stage booting
Since commit 823d08e3e261 ("kwbimage_v1: add support to boot a mvebu image") barebox can use bootm to load a 2nd barebox image. Update the documentation accordingly. Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
-rw-r--r--Documentation/boards/mvebu.rst5
1 files changed, 3 insertions, 2 deletions
diff --git a/Documentation/boards/mvebu.rst b/Documentation/boards/mvebu.rst
index b4f8e60..42dcdb8 100644
--- a/Documentation/boards/mvebu.rst
+++ b/Documentation/boards/mvebu.rst
@@ -28,8 +28,9 @@ initialisation that could be taken.
Booting second stage
--------------------
-This is currently not possible because barebox assumes the registers are mapped
-at 0xd0000000 as is the case when the boot ROM gives control to the bootloader.
+Since ``v2017.04.0`` barebox can boot a barebox image even if the register
+window is moved. This is implemented by writing the actual window position
+into the image where it is then picked up by the second stage bootloader.
Booting from UART
-----------------