From: Takashi Iwai <tiwai@suse.de>
To: Hideki Yamane <henrich@iijmio-mail.jp>
Cc: Takashi Iwai <tiwai@suse.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Luis Chamberlain <mcgrof@kernel.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 0/4] firmware: Add ZSTD-compressed file support
Date: Wed, 02 Feb 2022 11:56:56 +0100 [thread overview]
Message-ID: <s5hh79hzgcn.wl-tiwai@suse.de> (raw)
In-Reply-To: <20220202023618.2f676b6b319188c470a15e0b@iijmio-mail.jp>
On Tue, 01 Feb 2022 18:36:18 +0100,
Hideki Yamane wrote:
>
> Hi,
>
> On Fri, 28 Jan 2022 09:13:36 +0100
> Takashi Iwai <tiwai@suse.de> wrote:
> > It's totally untested, and it'd be appreciated if
> > anyone can confirm that it's working and used. Then we can happily
> > re-submit the patches for the merge.
>
> I've built it with 5.16.4 based one in Debian experimental repository
> and it seems to work (note: build failure with 5.15.15 in Debian unstable).
>
>
> How to check:
> 1. compress firmware files under /lib/firmware with zstd
> 2. boot with distro kernel that is not enable this feature
> 3. Wifi that needs firmware doesn't work as expected (*1)
> 4. boot with patched kernel
> 5. Wifi works :) (*2)
Good to know that it's working. (BTW, you can see more details when
you enable the debug, e.g. "firmware_class.dyndbg=+p" boot option.)
The next step is actually using this in some distro (or privately).
If the feature is confirmed to be needed, I'll resubmit the latest
patches for the merge request.
thanks,
Takashi
prev parent reply other threads:[~2022-02-02 10:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 15:49 [PATCH RFC 0/4] firmware: Add ZSTD-compressed file support Takashi Iwai
2021-01-27 15:49 ` [PATCH RFC 1/4] firmware: Add the support for ZSTD-compressed firmware files Takashi Iwai
2021-02-17 13:16 ` Luis Chamberlain
2021-02-17 13:22 ` Takashi Iwai
2021-02-17 13:24 ` Luis Chamberlain
2021-02-17 13:34 ` Takashi Iwai
2021-02-17 14:17 ` Greg Kroah-Hartman
2021-02-17 14:21 ` Takashi Iwai
2021-01-27 15:49 ` [PATCH RFC 2/4] selftests: firmware: Simplify test patterns Takashi Iwai
2021-01-27 15:49 ` [PATCH RFC 3/4] selftest: firmware: Fix the request_firmware_into_buf() test for XZ format Takashi Iwai
2021-01-27 15:49 ` [PATCH RFC 4/4] selftest: firmware: Add ZSTD compressed file tests Takashi Iwai
2021-01-27 17:09 ` [PATCH RFC 0/4] firmware: Add ZSTD-compressed file support Greg Kroah-Hartman
2022-01-27 18:22 ` Hideki Yamane
2022-01-27 18:41 ` Greg Kroah-Hartman
2022-01-28 0:33 ` Hideki Yamane
2022-01-28 6:54 ` Greg Kroah-Hartman
2022-01-28 8:13 ` Takashi Iwai
2022-02-01 17:36 ` Hideki Yamane
2022-02-02 10:56 ` Takashi Iwai [this message]
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=s5hh79hzgcn.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=gregkh@linuxfoundation.org \
--cc=henrich@iijmio-mail.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=rafael@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).