From: Michael Riesch <michael.riesch@wolfvision.net>
To: ptxdist@pengutronix.de
Cc: michael.tretter@pengutronix.de,
Michael Riesch <michael.riesch@wolfvision.net>
Subject: [ptxdist] [PATCH 0/3] Add support for Rockchip firmware blobs
Date: Fri, 3 Dec 2021 17:54:37 +0100 [thread overview]
Message-ID: <20211203165440.1180588-1-michael.riesch@wolfvision.net> (raw)
Hi all,
Integrating binary firmware blobs provided by vendors into our BSPs
is a nasty part of our job, isn't it... But maybe we can at least
share the efforts to reduce the pain. In this spirit I look forward
to your comments on these patches:
The first patch adds a section dedicated to non-free firmware blobs,
as has been suggested in the firmware-imx rule in DistroKit.
This allows to group the firmware blob rules at a defined point and
disable them with a single switch, if required.
The second patch adds a rule to download the Rockchip binaries, where
the files for the RK3566/RK3568 are in the focus for now. Barebox
support for those two SoCs is coming along rather nicely, but those
blobs are a mandatory requirement.
In similar cases, a separate rule file for barebox have been added to
a ptxdist setup that takes care of integrating the firmware blobs
into the source tree. Maybe a generic approach would eliminate the
need for a different rule file only to copy a few files.
Therefore, the third patch allows to configure files that are
injected into the barebox source tree during preparation. This patch
can be considered as RFC, as my knowledge of the ptxdist internals as
well as my shell script skills leave a lot to be desired. Still I
think you can get the gist.
Have a nice weekend!
Best regards,
Michael
Michael Riesch (3):
platforms: add section for non-free firmware blobs
add package for rockchip firmware binaries
barebox: add integration of firmware blobs
platforms/Kconfig | 10 ++++
platforms/barebox.in | 23 ++++++++
platforms/firmware-rockchip.in | 35 ++++++++++++
rules/barebox.make | 6 +++
rules/firmware-rockchip.make | 75 ++++++++++++++++++++++++++
rules/post/ptxd_make_world_inject.make | 19 +++++++
scripts/lib/ptxd_make_world_inject.sh | 21 ++++++++
7 files changed, 189 insertions(+)
create mode 100644 platforms/firmware-rockchip.in
create mode 100644 rules/firmware-rockchip.make
create mode 100644 rules/post/ptxd_make_world_inject.make
create mode 100644 scripts/lib/ptxd_make_world_inject.sh
--
2.30.2
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next reply other threads:[~2021-12-03 16:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 16:54 Michael Riesch [this message]
2021-12-03 16:54 ` [ptxdist] [PATCH 1/3] platforms: add section for non-free " Michael Riesch
2021-12-03 16:54 ` [ptxdist] [PATCH 2/3] add package for rockchip firmware binaries Michael Riesch
2021-12-03 17:55 ` Christian Melki
2021-12-04 7:10 ` Michael Riesch
2021-12-04 15:37 ` Christian Melki
2021-12-06 6:06 ` Michael Riesch
2021-12-05 0:56 ` Roland Hieber
2021-12-05 1:00 ` Roland Hieber
2021-12-05 9:07 ` Michael Riesch
2021-12-06 6:27 ` Michael Riesch
2021-12-03 16:54 ` [ptxdist] [RFC PATCH 3/3] barebox: add integration of firmware blobs Michael Riesch
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=20211203165440.1180588-1-michael.riesch@wolfvision.net \
--to=michael.riesch@wolfvision.net \
--cc=michael.tretter@pengutronix.de \
--cc=ptxdist@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