DistroKit Mailinglist
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: distrokit@pengutronix.de
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [DistroKit] [PATCH 09/10] v7a: rpi4: place DT into /boot for VideoCore consumption
Date: Fri, 30 Sep 2022 18:21:58 +0200	[thread overview]
Message-ID: <20220930162159.814389-10-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20220930162159.814389-1-a.fatoum@pengutronix.de>

This is a somewhat ugly hack. The VideoCore will pass this device tree
to barebox, which doesn't care much for it. As a side effect of the
device tree passing, the VideoCore parses the device tree and will
detect that the mini-uart is enabled and take care not to scale clock
rate on the VideoCore, which the mini-uart is sourced from as that would
upset the baudrate.

There may be some config.txt entry we can use to avoid this, but for
now, just place the device tree into the boot partition.

Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
 configs/platform-v7a/config/images/rpi2.config | 1 +
 1 file changed, 1 insertion(+)

diff --git a/configs/platform-v7a/config/images/rpi2.config b/configs/platform-v7a/config/images/rpi2.config
index 08bb33b125a5..3dc404d36379 100644
--- a/configs/platform-v7a/config/images/rpi2.config
+++ b/configs/platform-v7a/config/images/rpi2.config
@@ -2,6 +2,7 @@ image rpi2-boot.vfat {
 	vfat {
 		files = { @FIRMWARE_RPI2@ }
 		file barebox.img { image = barebox-raspberry-pi.img }
+		file bcm2711-rpi-4-b.dtb { image = barebox-bcm2711-rpi-4.dtb }
 	}
 	size = 32M
 }
-- 
2.30.2




  parent reply	other threads:[~2022-09-30 16:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-30 16:21 [DistroKit] [PATCH 00/10] v7a: add Raspberry Pi 4 32-bit support Ahmad Fatoum
2022-09-30 16:21 ` [DistroKit] [PATCH 01/10] v7a: barebox: version bump v2022.06.0 → v2022.09.0 Ahmad Fatoum
2022-09-30 16:21 ` [DistroKit] [PATCH 02/10] v7a: barebox: switch to new broken-cd device parameter Ahmad Fatoum
2022-09-30 16:21 ` [DistroKit] [PATCH 03/10] v7a: rpi2: move rpi-firmware directory to top-level workspace Ahmad Fatoum
2022-09-30 16:21 ` [DistroKit] [PATCH 04/10] rpi-firmware: Update firmware to v1.20220331 for Rpi4 support Ahmad Fatoum
2022-09-30 16:21 ` [DistroKit] [PATCH 05/10] barebox: deploy new barebox-raspberry-pi.img Ahmad Fatoum
2022-09-30 16:21 ` [DistroKit] [PATCH 06/10] v7a: kernel: configure for 32-bit Raspberry Pi 4 support Ahmad Fatoum
2022-09-30 16:21 ` [DistroKit] [PATCH 07/10] v7a: dts: build Raspberry Pi 4 device trees Ahmad Fatoum
2022-09-30 16:21 ` [DistroKit] [PATCH 08/10] v7a: rpi4: add boot loader spec support Ahmad Fatoum
2022-09-30 16:21 ` Ahmad Fatoum [this message]
2022-09-30 16:21 ` [DistroKit] [PATCH 10/10] v7a: barebox: enable of_diff command Ahmad Fatoum
2022-09-30 16:55 ` [DistroKit] [PATCH 00/10] v7a: add Raspberry Pi 4 32-bit support Robert Schwebel

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=20220930162159.814389-10-a.fatoum@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=distrokit@pengutronix.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