From: Nicolas Schier <n.schier@avm.de>
To: Kevin Martin <kevinmbecause@gmail.com>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
Russ Weight <russ.weight@linux.dev>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Nicolas Schier <nicolas@fjasle.eu>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] firmware_loader: Enable compressed files in EXTRA_FIRMWARE
Date: Tue, 2 Jan 2024 07:46:55 +0100 [thread overview]
Message-ID: <ZZOxXw7ZrmumszkO@buildd.core.avm.de> (raw)
In-Reply-To: <cd370037f8c21dc851a2a33a07250459c9c98708.1703042082.git.kevinmbecause@gmail.com>
On Wed, Dec 20, 2023 at 05:29:33AM -0500, Kevin Martin wrote:
> The linux-firmware packages on Gentoo, Fedora, Arch, and others compress
> the firmware files. This works well with CONFIG_FW_LOADER_COMPRESS, but
> does not work with CONFIG_EXTRA_FIRMWARE. This patch allows the build
> system to decompress firmware files specified by CONFIG_EXTRA_FIRMWARE.
> Uncompressed files are used first, then the compressed files are used.
>
> Signed-off-by: Kevin Martin <kevinmbecause@gmail.com>
> ---
Tested-by: Nicolas Schier <n.schier@avm.de>
next prev parent reply other threads:[~2024-01-02 6:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 10:22 [PATCH 0/2] " Kevin Martin
2023-12-20 10:22 ` [PATCH 1/2] kbuild: Enable decompression for use by EXTRA_FIRMWARE The build system can currently only compress files. This patch adds the functionality to decompress files. Decompression is needed for building firmware files into the kernel if those files are compressed on the filesystem. Compressed firmware files are in use by Gentoo, Fedora, Arch, and others Kevin Martin
2024-01-02 6:46 ` Nicolas Schier
2024-01-03 12:00 ` Masahiro Yamada
2024-01-04 7:04 ` Kevin Martin
2024-01-04 14:13 ` Masahiro Yamada
2023-12-20 10:29 ` [PATCH 2/2] firmware_loader: Enable compressed files in EXTRA_FIRMWARE Kevin Martin
2024-01-02 6:46 ` Nicolas Schier [this message]
2024-01-03 12:22 ` Masahiro Yamada
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=ZZOxXw7ZrmumszkO@buildd.core.avm.de \
--to=n.schier@avm.de \
--cc=gregkh@linuxfoundation.org \
--cc=kevinmbecause@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=nicolas@fjasle.eu \
--cc=rafael@kernel.org \
--cc=russ.weight@linux.dev \
/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
all inboxes | Powered by JetHome®