From: Igor Russkikh <irusskikh@marvell.com>
To: David Marchand <david.marchand@redhat.com>, <dev@dpdk.org>
Subject: Re: [dpdk-dev] [EXT] [PATCH 0/2] Support compressed firmwares
Date: Wed, 2 Jun 2021 12:35:10 +0200 [thread overview]
Message-ID: <e4466ecd-d1a0-d23a-f438-e594322e0e00@marvell.com> (raw)
In-Reply-To: <20210602095836.24901-1-david.marchand@redhat.com>
> Fedora 34 only provides compressed firmwares.
>
> Introduce an internal driver helper to handle transparently compression.
>
> I chose libarchive for decompressing as it seems widely available and
> DPDK had used it in the past.
>
> Windows support only matters for net/ice and firmware loading was skipped
> in this driver before this series. Since I don't know if/how we want to
> load firmwares on Windows, I let an empty stub for this OS.
>
> This series has been compile tested on Linux (I'll trust the CI for
> others OSes).
> I only tested basic init with a net/ice device (no DCF test).
>
> So please drivers maintainers, check nothing is broken.
Hi David,
We (Marvell QED) already provide packed version of FW in linux-firmware:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/qed
But thats a custom name, and zlib.
I'm just wondering if its a good solution to try transparently load .xz variant?
User may not expect that. M.b. through this api, give a driver an option to specify
archive format? Or even autodetect it from content?
Regards,
Igor
next prev parent reply other threads:[~2021-06-02 10:38 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 9:58 [dpdk-dev] " David Marchand
2021-06-02 9:58 ` [dpdk-dev] [PATCH 1/2] net/ice: factorize firmware loading David Marchand
2021-06-02 9:58 ` [dpdk-dev] [PATCH 2/2] eal: handle compressed firmwares David Marchand
2021-06-02 11:13 ` Jerin Jacob
2021-06-02 15:46 ` David Marchand
2021-06-02 11:30 ` [dpdk-dev] [EXT] " Igor Russkikh
2021-06-02 21:19 ` [dpdk-dev] " Dmitry Kozlyuk
2021-06-03 7:23 ` David Marchand
2021-06-03 7:53 ` David Marchand
2021-06-03 8:14 ` Bruce Richardson
2021-06-02 10:35 ` Igor Russkikh [this message]
2021-06-02 11:05 ` [dpdk-dev] [EXT] [PATCH 0/2] Support " David Marchand
2021-06-02 11:23 ` Igor Russkikh
2021-06-03 16:55 ` [dpdk-dev] [PATCH v2 " David Marchand
2021-06-03 16:55 ` [dpdk-dev] [PATCH v2 1/2] net/ice: factorize firmware loading David Marchand
2021-06-28 7:58 ` David Marchand
2021-06-03 16:55 ` [dpdk-dev] [PATCH v2 2/2] eal: handle compressed firmwares David Marchand
2021-06-03 22:29 ` Dmitry Kozlyuk
2021-06-04 7:27 ` David Marchand
2021-06-04 21:40 ` Dmitry Kozlyuk
2021-06-07 9:28 ` David Marchand
2021-06-14 13:17 ` [dpdk-dev] [PATCH v2 0/2] Support " David Marchand
2021-06-29 8:06 ` [dpdk-dev] [PATCH v3 " David Marchand
2021-06-29 8:06 ` [dpdk-dev] [PATCH v3 1/2] net/ice: factorize firmware loading David Marchand
2021-07-05 1:43 ` Wang, Haiyue
2021-07-05 3:33 ` Wang, Haiyue
2021-07-05 7:08 ` David Marchand
2021-07-05 8:02 ` Wang, Haiyue
2021-07-05 8:33 ` David Marchand
2021-07-05 9:59 ` Zhang, Qi Z
2021-07-05 11:46 ` Wang, Haiyue
2021-07-05 11:44 ` Wang, Haiyue
2021-07-05 13:18 ` Wang, Haiyue
2021-07-05 13:34 ` David Marchand
2021-06-29 8:06 ` [dpdk-dev] [PATCH v3 2/2] eal: handle compressed firmwares David Marchand
2021-06-29 12:45 ` Aaron Conole
2021-07-05 6:35 ` Wang, Haiyue
2021-07-05 6:54 ` David Marchand
2021-07-05 13:19 ` Wang, Haiyue
2021-07-06 14:29 ` [dpdk-dev] [PATCH v4 0/2] Support " David Marchand
2021-07-06 14:29 ` [dpdk-dev] [PATCH v4 1/2] net/ice: factorize firmware loading David Marchand
2021-07-06 14:29 ` [dpdk-dev] [PATCH v4 2/2] eal: handle compressed firmwares David Marchand
2021-07-07 12:08 ` [dpdk-dev] [PATCH v5 0/2] Support " David Marchand
2021-07-07 12:08 ` [dpdk-dev] [PATCH v5 1/2] net/ice: factorize firmware loading David Marchand
2021-07-07 12:08 ` [dpdk-dev] [PATCH v5 2/2] eal: handle compressed firmware David Marchand
2021-07-07 15:03 ` [dpdk-dev] [PATCH v5 0/2] Support compressed firmwares David Marchand
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=e4466ecd-d1a0-d23a-f438-e594322e0e00@marvell.com \
--to=irusskikh@marvell.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.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).