From: Robert Schwebel <r.schwebel@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: distrokit@pengutronix.de, ore@pengutronix.de
Subject: Re: [DistroKit] [PATCH 0/2] v7a: rpi: unify rpi{2, 3, cm3} into common rpi.hdimg
Date: Tue, 26 Apr 2022 15:24:45 +0200 [thread overview]
Message-ID: <YmfynXuhxFKXmTHF@pengutronix.de> (raw)
In-Reply-To: <20220426083821.1829442-1-a.fatoum@pengutronix.de>
On Tue, Apr 26, 2022 at 10:38:19AM +0200, Ahmad Fatoum wrote:
> barebox has had the ability to generate an extra image that's bootable
> like a kernel for a while now. With small adjustment, we can let the
> videocore use this image and pass it the appropriate device tree
> depending on the board used. Moving this decision into the VideoCore
> allows us to use the same DistroKit hdimg for all of the Raspberry Pi 2,
> Rasperry Pi 3 and Raspberry Pi CM3.
>
> The patches added in this series are all already part of the barebox
> next branch and will thus expectedly go away with v2022.06.0.
>
> Series tested on Raspberry Pi 3b and Raspberry Pi 2.
Merged into next, waiting for the (modified) testsuite.
rsc
--
Pengutronix e.K. | Dipl.-Ing. Robert Schwebel |
Steuerwalder Str. 21 | https://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-9 |
_______________________________________________
DistroKit mailing list
DistroKit@pengutronix.de
next prev parent reply other threads:[~2022-04-26 13:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 8:38 Ahmad Fatoum
2022-04-26 8:38 ` [DistroKit] [PATCH 1/2] v7a: barebox: update v2022.01.0 → v2022.04.0 Ahmad Fatoum
2022-04-26 8:38 ` [DistroKit] [PATCH 2/2] v7a: rpi: unify rpi{2, 3, cm3}.hdimg into common rpi.hdimg Ahmad Fatoum
2022-04-26 8:47 ` Ahmad Fatoum
2022-04-26 13:24 ` Robert Schwebel [this message]
2022-05-03 11:34 ` [DistroKit] [PATCH 0/2] v7a: rpi: unify rpi{2, 3, cm3} " Roland Hieber
2022-05-16 12:02 ` Ahmad Fatoum
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=YmfynXuhxFKXmTHF@pengutronix.de \
--to=r.schwebel@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=distrokit@pengutronix.de \
--cc=ore@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