diff options
author | Ahmad Fatoum <a.fatoum@pengutronix.de> | 2019-06-17 16:18:46 +0200 |
---|---|---|
committer | Sascha Hauer <s.hauer@pengutronix.de> | 2019-06-18 10:01:36 +0200 |
commit | 3a14fb79153af84323fee8308989011cd05c7d96 (patch) | |
tree | 330af6b7f48e370b37a67794997020ef73661ab7 | |
parent | 42cc7a3e925eb47563a59045738a82725e1fad8a (diff) | |
download | barebox-3a14fb79153af84323fee8308989011cd05c7d96.tar.gz barebox-3a14fb79153af84323fee8308989011cd05c7d96.tar.xz |
Documentation: user: suggest U-Boot's bootm, not go
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>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
-rw-r--r-- | Documentation/user/barebox.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/user/barebox.rst b/Documentation/user/barebox.rst index 1927fe4efc..d82163a886 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`` |