From: Michael Riesch <michael.riesch@wolfvision.net>
To: ptxdist@pengutronix.de
Cc: m.tretter@pengutronix.de, Michael Riesch <michael.riesch@wolfvision.net>
Subject: [ptxdist] [PATCH v5 0/5] Add support for Rockchip firmware blobs
Date: Mon, 24 Jan 2022 13:09:37 +0100 [thread overview]
Message-ID: <20220124120942.557161-1-michael.riesch@wolfvision.net> (raw)
Hi all,
The fifth version of this patch series considers the comments by
Michael Olbrich. As a consequence, the fourth patch is split into
a generic part that is ready to be applied as far as I am concerned,
and a RFC patch that showcases the usage of the features introduced
in this series. It has been pointed out that the exact usage of the
features may need further discussion. However, this discussion is
restricted to the name and the location of the binary blobs and is
not expected to require changes in the generic part.
Looking forward to your comments!
Best regards,
Michael
Michael Riesch (5):
platforms: add section for non-free firmware blobs
add package for rockchip firmware binaries
scripts: add helper to inject files into a source directory
barebox: add integration of firmware blobs
barebox.rockchip: add binary firmware blobs for quartz64 and
rk3568-evb1
platforms/Kconfig | 10 ++++
platforms/barebox.in | 8 +++
platforms/barebox.rockchip.in | 14 +++++
platforms/firmware-rockchip.in | 41 ++++++++++++++
rules/barebox.make | 6 +++
rules/barebox.rockchip.make | 18 +++++++
rules/firmware-rockchip.make | 74 ++++++++++++++++++++++++++
rules/post/ptxd_make_world_inject.make | 19 +++++++
scripts/lib/ptxd_make_world_inject.sh | 42 +++++++++++++++
9 files changed, 232 insertions(+)
create mode 100644 platforms/barebox.rockchip.in
create mode 100644 platforms/firmware-rockchip.in
create mode 100644 rules/barebox.rockchip.make
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:[~2022-01-24 12:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 12:09 Michael Riesch [this message]
2022-01-24 12:09 ` [ptxdist] [PATCH v5 1/5] platforms: add section for non-free " Michael Riesch
2022-01-24 12:09 ` [ptxdist] [PATCH v5 2/5] add package for rockchip firmware binaries Michael Riesch
2022-01-28 12:31 ` Michael Olbrich
2022-01-28 12:46 ` Michael Riesch
2022-01-28 12:59 ` Michael Olbrich
2022-01-28 13:46 ` Michael Riesch
2022-01-24 12:09 ` [ptxdist] [PATCH v5 3/5] scripts: add helper to inject files into a source directory Michael Riesch
2022-01-28 12:27 ` Michael Olbrich
2022-01-24 12:09 ` [ptxdist] [PATCH v5 4/5] barebox: add integration of firmware blobs Michael Riesch
2022-01-28 12:28 ` Michael Olbrich
2022-01-24 12:09 ` [ptxdist] [RFC PATCH v5 5/5] barebox.rockchip: add binary firmware blobs for quartz64 and rk3568-evb1 Michael Riesch
2022-01-28 12:33 ` Michael Olbrich
2022-01-28 15:26 ` Michael Riesch
2022-01-28 16:10 ` Michael Olbrich
2022-01-28 16:48 ` Michael Riesch
2022-01-28 20:08 ` Michael Olbrich
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=20220124120942.557161-1-michael.riesch@wolfvision.net \
--to=michael.riesch@wolfvision.net \
--cc=m.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