All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@buildroot.org
Cc: Mahyar Koshkouei <mahyar.koshkouei@gmail.com>,
	Julien Grossholtz <julien.grossholtz@openest.io>,
	Martin Bark <martin@barkynet.com>
Subject: [Buildroot] [PATCH/next v1 6/7] board/raspberrypi/readme.txt: add missing dtb files
Date: Thu, 11 Nov 2021 21:04:38 +0100	[thread overview]
Message-ID: <20211111200439.15379-6-ps.report@gmx.net> (raw)
In-Reply-To: <20211111200439.15379-1-ps.report@gmx.net>

Add missing dtb files:
 - bcm2708-rpi-cm.dtb from genimage-raspberrypi.cfg
 - bcm2708-rpi-zero.dtb from genimage-raspberrypi0.cfg:
 - bcm2708-rpi-zero-w.dtb from genimage-raspberrypi0w.cfg
 - bcm2710-rpi-cm3.dtb from genimage-raspberrypi3.cfg
 - bcm2837-rpi-3-b.dtb from genimage-raspberrypi3-64.cfg

Signed-off-by: Peter Seiderer <ps.report@gmx.net>
---
 board/raspberrypi/readme.txt | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/board/raspberrypi/readme.txt b/board/raspberrypi/readme.txt
index 98c44d80a1..d20096b5e6 100644
--- a/board/raspberrypi/readme.txt
+++ b/board/raspberrypi/readme.txt
@@ -76,11 +76,16 @@ After building, you should obtain this tree:
     output/images/
     +-- bcm2708-rpi-b.dtb           [1]
     +-- bcm2708-rpi-b-plus.dtb      [1]
+    +-- bcm2708-rpi-cm.dtb          [1]
+    +-- bcm2708-rpi-zero.dtb        [1]
+    +-- bcm2708-rpi-zero-w.dtb      [1]
     +-- bcm2709-rpi-2-b.dtb         [1]
     +-- bcm2710-rpi-3-b.dtb         [1]
     +-- bcm2710-rpi-3-b-plus.dtb    [1]
+    +-- bcm2710-rpi-cm3.dtb         [1]
     +-- bcm2711-rpi-4-b.dtb         [1]
     +-- bcm2711-rpi-cm4.dtb         [1]
+    +-- bcm2837-rpi-3-b.dtb         [1]
     +-- boot.vfat
     +-- rootfs.ext4
     +-- rpi-firmware/
-- 
2.33.1

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2021-11-11 20:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-11 20:04 [Buildroot] [PATCH/next v1 1/7] configs/raspberrypi*: bump kernel version to 9878a11 (5.10.78) Peter Seiderer
2021-11-11 20:04 ` [Buildroot] [PATCH/next v1 2/7] package/rpi-firmware: bump version to fa9a006 Peter Seiderer
2021-11-12 22:13   ` Yann E. MORIN
2021-11-11 20:04 ` [Buildroot] [PATCH/next v1 3/7] package/rpi-userland: bump version to bab9bf8 Peter Seiderer
2021-11-12 22:14   ` Yann E. MORIN
2021-11-11 20:04 ` [Buildroot] [PATCH/next v1 4/7] package/rpi-bt-firmware: bump version to 3888ba2 Peter Seiderer
2021-11-12 22:18   ` Yann E. MORIN
2021-11-11 20:04 ` [Buildroot] [PATCH/next v1 5/7] package/rpi-wifi-firmware: " Peter Seiderer
2021-11-12 22:18   ` Yann E. MORIN
2021-11-11 20:04 ` Peter Seiderer [this message]
2021-11-12 22:18   ` [Buildroot] [PATCH/next v1 6/7] board/raspberrypi/readme.txt: add missing dtb files Yann E. MORIN
2021-11-11 20:04 ` [Buildroot] [PATCH/next v1 7/7] board/raspberrypi: add Raspberry Pi Zero 2 W Peter Seiderer
2021-11-12 22:19   ` Yann E. MORIN
2021-11-12 22:13 ` [Buildroot] [PATCH/next v1 1/7] configs/raspberrypi*: bump kernel version to 9878a11 (5.10.78) Yann E. MORIN

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=20211111200439.15379-6-ps.report@gmx.net \
    --to=ps.report@gmx.net \
    --cc=buildroot@buildroot.org \
    --cc=julien.grossholtz@openest.io \
    --cc=mahyar.koshkouei@gmail.com \
    --cc=martin@barkynet.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.