summaryrefslogtreecommitdiffstats
path: root/Documentation/user/barebox.rst
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/user/barebox.rst')
-rw-r--r--Documentation/user/barebox.rst11
1 files changed, 6 insertions, 5 deletions
diff --git a/Documentation/user/barebox.rst b/Documentation/user/barebox.rst
index 1927fe4efc..c021a4c743 100644
--- a/Documentation/user/barebox.rst
+++ b/Documentation/user/barebox.rst
@@ -112,11 +112,12 @@ targets, followed by the MIPS-specific ones:
Architecture specific targets (mips):
No architecture specific help defined for mips
+ ath79_defconfig - Build for ath79
+ bcm47xx_defconfig - Build for bcm47xx
+ gxemul-malta_defconfig - Build for gxemul-malta
loongson-ls1b_defconfig - Build for loongson-ls1b
- ritmix-rzx50_defconfig - Build for ritmix-rzx50
- tplink-mr3020_defconfig - Build for tplink-mr3020
- dlink-dir-320_defconfig - Build for dlink-dir-320
qemu-malta_defconfig - Build for qemu-malta
+ xburst_defconfig - Build for xburst
barebox supports building for multiple boards with a single config. If you
can't find your board in the list, it may be supported by one of the multi-board
@@ -206,12 +207,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``