mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Michael Riesch <michael.riesch@wolfvision.net>
Subject: Re: [ptxdist] [APPLIED] platforms: add section for non-free firmware blobs
Date: Sun, 30 Jan 2022 16:49:47 +0100	[thread overview]
Message-ID: <20220130154947.9355-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20220129070330.2601433-2-michael.riesch@wolfvision.net>

Thanks, applied as 16449115567eb71adeea9230fa3244bd6c483c76.

Michael

[sent from post-receive hook]

On Sun, 30 Jan 2022 16:49:46 +0100, Michael Riesch <michael.riesch@wolfvision.net> wrote:
> Add a dedicated section for non-free firmware binary blobs, such
> as SDRAM initialization binaries.
> 
> Signed-off-by: Michael Riesch <michael.riesch@wolfvision.net>
> Message-Id: <20220129070330.2601433-2-michael.riesch@wolfvision.net>
> [mol: menu instead of menuconfig to avoid dependency issues]
> [mol: add dummy menu file]
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> 
> diff --git a/platforms/Kconfig b/platforms/Kconfig
> index 0bfe34cdc16d..d9adc4931cdd 100644
> --- a/platforms/Kconfig
> +++ b/platforms/Kconfig
> @@ -40,3 +40,7 @@ source "generated/hosttools_noprompt.in"
>  source "generated/hosttools_platform.in"
>  
>  source "generated/platform_project_specific.in"
> +
> +menu "non-free firmware blobs       "
> +source "generated/non_free_firmware.in"
> +endmenu
> diff --git a/platforms/non_free_firmware.in b/platforms/non_free_firmware.in
> new file mode 100644
> index 000000000000..c0635859ac0c
> --- /dev/null
> +++ b/platforms/non_free_firmware.in
> @@ -0,0 +1,7 @@
> +## SECTION=non_free_firmware
> +
> +#
> +# This file does only exist to create a defined entry in the "non_free_firmware"
> +# section, so that the toplevel Kconfig can include generated/non_free_firmware.in
> +# even if no package is in that category.
> +#

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de


  reply	other threads:[~2022-01-30 15:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-29  7:03 [ptxdist] [PATCH v6 0/5] Add support for Rockchip " Michael Riesch
2022-01-29  7:03 ` [ptxdist] [PATCH v6 1/5] platforms: add section for non-free " Michael Riesch
2022-01-30 15:49   ` Michael Olbrich [this message]
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=20220130154947.9355-1-m.olbrich@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=michael.riesch@wolfvision.net \
    --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