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 v6 0/5] Add support for Rockchip firmware blobs
Date: Sat, 29 Jan 2022 08:03:25 +0100 [thread overview]
Message-ID: <20220129070330.2601433-1-michael.riesch@wolfvision.net> (raw)
Hi all,
The sixth version of this patch series considers further comments
by Michael Olbrich. Again, the series includes an RFC patch that
showcases the usage of the introduced features. After fixing the
dependencies (as pointed out by Michael) a circular dependency
of Kconfig symbols popped up. I tried to fix this by introducing
a new symbol BAREBOX_DEPENDENCIES. This approach seems to work
just fine here, but as I am no Kconfig expert please review it
carefully.
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.firmware.in | 7 +++
platforms/barebox.in | 13 +++++
platforms/barebox.rockchip.in | 16 ++++++
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 +++++++++++++++
10 files changed, 246 insertions(+)
create mode 100644 platforms/barebox.firmware.in
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-29 7:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 7:03 Michael Riesch [this message]
2022-01-29 7:03 ` [ptxdist] [PATCH v6 1/5] platforms: add section for non-free " Michael Riesch
2022-01-30 15:49 ` [ptxdist] [APPLIED] " Michael Olbrich
2022-01-29 7:03 ` [ptxdist] [PATCH v6 2/5] add package for rockchip firmware binaries Michael Riesch
2022-01-29 7:03 ` [ptxdist] [PATCH v6 3/5] scripts: add helper to inject files into a source directory Michael Riesch
2022-01-30 15:49 ` [ptxdist] [APPLIED] " Michael Olbrich
2024-04-19 9:48 ` [ptxdist] [PATCH v6 3/5] " Alexander Dahl
2024-05-02 10:08 ` Michael Olbrich
2024-04-23 13:52 ` Alexander Dahl
2024-04-23 16:27 ` Michael Riesch
2022-01-29 7:03 ` [ptxdist] [PATCH v6 4/5] barebox: add integration of firmware blobs Michael Riesch
2022-01-30 15:49 ` [ptxdist] [APPLIED] " Michael Olbrich
2022-01-29 7:03 ` [ptxdist] [RFC PATCH v6 5/5] barebox.rockchip: add binary firmware blobs for quartz64 and rk3568-evb1 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=20220129070330.2601433-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