From: Mario Limonciello <superm1@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>, linux-firmware@kernel.org
Cc: linux-wireless@vger.kernel.org, miriam.rachel.korenblit@intel.com
Subject: Re: putting future iwlwifi firmware into intel/ ?
Date: Wed, 17 Apr 2024 07:42:30 -0500 [thread overview]
Message-ID: <b0e70576-a53f-4d03-a503-ddf1f98bbe9d@gmail.com> (raw)
In-Reply-To: <f65765b29ea7503fbbaa5e047c95a82de6fc2083.camel@sipsolutions.net>
On 4/17/24 07:39, Johannes Berg wrote:
> On Wed, 2024-04-17 at 07:31 -0500, Mario Limonciello wrote:
>>
>> On 4/17/24 06:18, Johannes Berg wrote:
>>> Hi,
>>>
>>> Since I was just looking at some firmware related thing (files for the
>>> hardware that might be shared between Intel BT and WiFi), I noticed that
>>> just over 30% of the files/dirs in the top-level firmware tree are
>>> iwlwifi-* files.
>>>
>>> While we can't move the files that older drivers might consume, we could
>>> e.g. change the driver to look up future versions/future hardware under
>>> intel/ instead? Would that be worth doing?
>>>
>>> johannes
>>>
>>
>> How about moving them all now and then creating compat symlinks for
>> older kernels at linux-firmware 'make install' time?
>>
>
> Didn't realize there even was a 'make install' time :-)
>
> But then I guess it'd be simpler in the driver since we could just
> unconditionally add the intel/ prefix to the request_firmware call.
>
> johannes
Do both. All the stuff already there add the compat symlinks in linux
firmware so that current and older kernels work with older hardware.
Any "new firmware" only put in the new path, and add commits to the
kernel to look for "all" firmware in the new path.
Should hopefully cover everything without too much pain then.
next prev parent reply other threads:[~2024-04-17 12:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 11:18 putting future iwlwifi firmware into intel/ ? Johannes Berg
2024-04-17 12:31 ` Mario Limonciello
2024-04-17 12:39 ` Johannes Berg
2024-04-17 12:42 ` Mario Limonciello [this message]
2024-04-17 12:45 ` Johannes Berg
2024-04-17 13:58 ` Mario Limonciello
2024-04-17 14:09 ` Johannes Berg
2024-04-17 14:14 ` Mario Limonciello
2024-04-17 12:56 ` Kalle Valo
2024-04-17 14:11 ` Johannes Berg
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=b0e70576-a53f-4d03-a503-ddf1f98bbe9d@gmail.com \
--to=superm1@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-firmware@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=miriam.rachel.korenblit@intel.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).