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 v2 1/3] platforms: add section for non-free firmware blobs
Date: Mon, 6 Dec 2021 08:54:29 +0100 [thread overview]
Message-ID: <20211206075431.1238025-2-michael.riesch@wolfvision.net> (raw)
In-Reply-To: <20211206075431.1238025-1-michael.riesch@wolfvision.net>
Add a dedicated section for non-free firmware binary blobs, such
as SDRAM initialization binaries.
Signed-off-by: Michael Riesch <michael.riesch@wolfvision.net>
---
platforms/Kconfig | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/platforms/Kconfig b/platforms/Kconfig
index 0bfe34cdc..047ac2b13 100644
--- a/platforms/Kconfig
+++ b/platforms/Kconfig
@@ -40,3 +40,13 @@ source "generated/hosttools_noprompt.in"
source "generated/hosttools_platform.in"
source "generated/platform_project_specific.in"
+
+menuconfig NON_FREE_FIRMWARE
+ bool
+ prompt "non-free firmware blobs "
+ help
+ Enable integration of non-free firmware blobs.
+
+if NON_FREE_FIRMWARE
+source "generated/non_free_firmware.in"
+endif
--
2.30.2
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next prev parent reply other threads:[~2021-12-06 7:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 7:54 [ptxdist] [PATCH v2 0/3] Add support for Rockchip " Michael Riesch
2021-12-06 7:54 ` Michael Riesch [this message]
2021-12-06 7:54 ` [ptxdist] [PATCH v2 2/3] add package for rockchip firmware binaries Michael Riesch
2021-12-06 7:54 ` [ptxdist] [PATCH v2 3/3] barebox: add integration of firmware blobs Michael Riesch
2021-12-08 7:59 ` Michael Olbrich
2021-12-09 5:22 ` 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=20211206075431.1238025-2-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