From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH] Documentation: bcm283x: be clearer about Raspberry Pi 4 support
Date: Wed, 13 Dec 2023 13:12:46 +0100 [thread overview]
Message-ID: <20231213121246.1676405-1-a.fatoum@pengutronix.de> (raw)
While rpi4 support is not as extensive as the rpi3, it's still
sufficient to boot Linux from either SD or Ethernet.
Make this clearer in the documentation.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
Documentation/boards/bcm2835.rst | 21 ++++++++++++++-------
1 file changed, 14 insertions(+), 7 deletions(-)
diff --git a/Documentation/boards/bcm2835.rst b/Documentation/boards/bcm2835.rst
index cfd3bb2edb96..f7ab723d633a 100644
--- a/Documentation/boards/bcm2835.rst
+++ b/Documentation/boards/bcm2835.rst
@@ -5,28 +5,35 @@ Raspberry Pi
------------
barebox has support for BCM283x-based Raspberry Pi single board computers.
-Support is most extensive for BCM283[567]. For the newer BCM2711 used in the
-Raspberry Pi 4, only basic support is currently available (Serial Port,
-Pinctrl/GPIO, SD-Card).
+Support is most extensive for BCM283[567], but barebox can also boot Linux
+over SD or Ethernet on the Raspberry Pi 4.
1. Prepare an SD or microSD card with a FAT filesystem of at least 30 MB in size.
2. Download the `Raspberry Pi firmware`_ (195 MB), unzip it, and copy the
contents of the ``boot/`` folder to your card.
- 3. Use ``make rpi_defconfig; make`` to build barebox. This will create the following images:
+ 3. Use ``make rpi_defconfig; make`` to build barebox for 32-bit boards or
+ ``make rpi_v8a_defconfig; make`` to build barebox for 64-bit.
+
+ ``rpi_defconfig`` will build at least following images:
- ``images/barebox-raspberry-pi-1.img`` for the BCM2835/ARM1176JZF-S (Raspberry Pi 1, Raspberry Pi Zero)
- ``images/barebox-raspberry-pi-2.img`` for the BCM2836/CORTEX-A7 (Raspberry Pi 2)
- ``images/barebox-raspberry-pi-3.img`` for the BCM2837/CORTEX-A53 (Raspberry Pi 3)
- ``images/barebox-raspberry-pi-cm3.img`` for the BCM2837/CORTEX-A53 (Raspberry Pi CM3)
- - ``images/barebox-raspberry-pi.img``, which is a super set of all the other images
+ - ``images/barebox-raspberry-pi.img``, which is a super set of all the other images,
+ including Raspberry Pi 4 32-bit support.
Copy the respective image for your model to your SD card and name it
``barebox.img``.
- The ``images/barebox-raspberry-pi.img`` is expected to replace the other images
- in the future. It contains the device trees of all supported (and enabled) variants
+ For 64-bit, only ``images/barebox-raspberry-pi.img`` will be created, which is usable
+ for both Raspberry Pi 3 and Raspberry Pi 4 in 64-bit mode. No support for the Raspberry
+ Pi 5 has been contributed yet.
+
+ The ``images/barebox-raspberry-pi.img`` is expected to be the sole image for 32-bit
+ also in the future. It contains the device trees of all supported (and enabled) variants
and determines at runtime what board it runs on and does the right thing.
4. Create a text file ``config.txt`` on the SD card with the following content::
--
2.39.2
next reply other threads:[~2023-12-13 12:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 12:12 Ahmad Fatoum [this message]
2023-12-15 11:04 ` Sascha Hauer
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=20231213121246.1676405-1-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
/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