On Fri, Jun 02, 2017 at 08:22:03PM +0200, Uwe Kleine-König wrote:
> 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@xxxxxxxxxxxxxx>
> ---
> Documentation/boards/mvebu.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/boards/mvebu.rst b/Documentation/boards/mvebu.rst
> index b4f8e6043dac..4dfdc4a8f761 100644
> --- a/Documentation/boards/mvebu.rst
> +++ b/Documentation/boards/mvebu.rst
> @@ -28,8 +28,8 @@ 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.
Applied with an additional line break, 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@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/barebox
