From: Ahmad Fatoum <ahmad@a3f.at>
To: barebox@lists.infradead.org
Cc: Frank Wunderlich <frank-w@public-files.de>, Ahmad Fatoum <ahmad@a3f.at>
Subject: [PATCH 1/2] Documentation: remove some references to zbarebox.bin
Date: Sun, 6 Feb 2022 00:19:29 +0100 [thread overview]
Message-ID: <20220205231930.2948516-1-ahmad@a3f.at> (raw)
At least ARM doesn't generate zbarebox.bin anymore. Remove some of the
left-over references.
Reported-by: Frank Wunderlich <frank-w@public-files.de>
Signed-off-by: Ahmad Fatoum <ahmad@a3f.at>
---
Documentation/boards/mips/qemu-malta.rst | 2 +-
Documentation/user/barebox.rst | 7 ++++---
Documentation/user/pbl.rst | 3 +--
3 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/Documentation/boards/mips/qemu-malta.rst b/Documentation/boards/mips/qemu-malta.rst
index fd37d5edb229..44f671638d9d 100644
--- a/Documentation/boards/mips/qemu-malta.rst
+++ b/Documentation/boards/mips/qemu-malta.rst
@@ -35,7 +35,7 @@ Using GXemul
GXemul supports MIPS Malta except PCI stuff.
You can use GXemul to run little-endian barebox (use gxemul-malta_defconfig).
-N.B. There is no need to swap words in ``zbarebox.bin`` for little-endian GXemul!
+N.B. There is no need to swap words in the barebox binary for little-endian GXemul!
GXemul run string:
diff --git a/Documentation/user/barebox.rst b/Documentation/user/barebox.rst
index b6b7a57af300..8634d8e48eef 100644
--- a/Documentation/user/barebox.rst
+++ b/Documentation/user/barebox.rst
@@ -220,10 +220,11 @@ another barebox. For instance, if you mounted a TFTP server to ``/mnt/tftp``
bootm /mnt/tftp/barebox.bin
-At least ``barebox.bin`` (with :ref:`pbl` support enabled ``arch/$ARCH/pbl/zbarebox.bin``)
-should be startable second stage. The flash binary (``barebox-flash-image``) may or may not
+At least ``barebox.bin`` (with :ref:`pbl` support enabled ``images/*.pblb``)
+should be startable second stage. The final binaries (``images/*.img``) may or may not
be startable second stage as it may have SoC specific headers which prevent running second
-stage.
+stage. barebox will usually have handlers in-place to skip these headers, so
+it can chainload itself regardless.
First Steps
-----------
diff --git a/Documentation/user/pbl.rst b/Documentation/user/pbl.rst
index f9b2d2030559..b0acd1a4f24d 100644
--- a/Documentation/user/pbl.rst
+++ b/Documentation/user/pbl.rst
@@ -13,8 +13,7 @@ PBL is available for ARM and MIPS. It can be enabled in ``make menuconfig`` with
the ``[*] Pre-Bootloader image`` option.
The user visible difference is that with PBL support ``barebox.bin`` is no longer
-the final binary image, but instead ``arch/$ARCH/pbl/zbarebox.bin``. Use the
-``barebox-flash-image`` link which always points to the correct image.
+the final binary image, but instead the images are placed in ``images/``.
Technical background
--------------------
--
2.33.0
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2022-02-05 23:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 23:19 Ahmad Fatoum [this message]
2022-02-05 23:19 ` [PATCH 2/2] Documentation: user: barebox: mention generic dt 2nd stage support Ahmad Fatoum
2022-02-07 8:00 ` Sascha Hauer
2022-02-07 8:14 ` Ahmad Fatoum
2022-02-07 8:34 ` Sascha Hauer
2022-02-07 8:36 ` Ahmad Fatoum
2022-02-07 9:36 ` Frank Wunderlich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220205231930.2948516-1-ahmad@a3f.at \
--to=ahmad@a3f.at \
--cc=barebox@lists.infradead.org \
--cc=frank-w@public-files.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox