* [PATCH] Documentation: user: suggest U-Boot's bootm, not go
@ 2019-06-17 14:18 Ahmad Fatoum
2019-06-18 8:01 ` Sascha Hauer
0 siblings, 1 reply; 2+ messages in thread
From: Ahmad Fatoum @ 2019-06-17 14:18 UTC (permalink / raw)
To: barebox
Unlike barebox, U-Boot's go command doesn't have any provisions
for cache handling and as such, bootstrapping barebox via go can
cause stale data to be erroneously executed as instructions.
The official documentation[1] suggests use of bootm instead, which
does the necessary flushing and invalidation. Update our documentation
accordingly.
[1]: http://www.denx.de/wiki/view/DULG/UBootStandalone#Section_5.12.3.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
Documentation/user/barebox.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/user/barebox.rst b/Documentation/user/barebox.rst
index 1927fe4efcc5..d82163a88634 100644
--- a/Documentation/user/barebox.rst
+++ b/Documentation/user/barebox.rst
@@ -206,12 +206,12 @@ board documentation for initial bringup.
barebox binaries are, where possible, designed to be startable second stage from another
bootloader. For example, if you have U-Boot running on your board, you can start barebox
-with U-Boot's 'go' command:
+with U-Boot's ``bootm`` command:
.. code-block:: console
U-Boot: tftp $load_addr barebox.bin
- U-Boot: go $load_addr
+ U-Boot: bootm $load_addr
With barebox already running on your board, this can be used to chainload
another barebox. For instance, if you mounted a TFTP server to ``/mnt/tftp``
--
2.20.1
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH] Documentation: user: suggest U-Boot's bootm, not go
2019-06-17 14:18 [PATCH] Documentation: user: suggest U-Boot's bootm, not go Ahmad Fatoum
@ 2019-06-18 8:01 ` Sascha Hauer
0 siblings, 0 replies; 2+ messages in thread
From: Sascha Hauer @ 2019-06-18 8:01 UTC (permalink / raw)
To: Ahmad Fatoum; +Cc: barebox
On Mon, Jun 17, 2019 at 04:18:46PM +0200, Ahmad Fatoum wrote:
> Unlike barebox, U-Boot's go command doesn't have any provisions
> for cache handling and as such, bootstrapping barebox via go can
> cause stale data to be erroneously executed as instructions.
>
> The official documentation[1] suggests use of bootm instead, which
> does the necessary flushing and invalidation. Update our documentation
> accordingly.
>
> [1]: http://www.denx.de/wiki/view/DULG/UBootStandalone#Section_5.12.3.
>
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
> Documentation/user/barebox.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Applied, 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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-06-18 8:01 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-06-17 14:18 [PATCH] Documentation: user: suggest U-Boot's bootm, not go Ahmad Fatoum
2019-06-18 8:01 ` Sascha Hauer
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox