From: Kalle Valo <kvalo@kernel.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-firmware@kernel.org, linux-wireless@vger.kernel.org,
miriam.rachel.korenblit@intel.com
Subject: Re: putting future iwlwifi firmware into intel/ ?
Date: Wed, 17 Apr 2024 15:56:47 +0300 [thread overview]
Message-ID: <87v84gi1v4.fsf@kernel.org> (raw)
In-Reply-To: <fec30176f437d565d4c1dfc4944373f117d75a64.camel@sipsolutions.net> (Johannes Berg's message of "Wed, 17 Apr 2024 13:18:03 +0200")
Johannes Berg <johannes@sipsolutions.net> writes:
> 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?
Yes, please. It would be nice to cleanup linux-firmware.git top level
directory. But what about this:
* convert iwlwifi to first use _all_ files under intel/ and then as a
fallback top level directory
* move existing iwlwifi firmware files to intel/ but create symlinks from
the old location to the new one (using 'Link:' in WHENCE)
* add new files only to intel/ directory
* after few (4?) years remove the symlinks from linux-firmware and the
fallback from iwlwifi
This should ensure backwards compatibility, right?
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-04-17 12:56 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
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 [this message]
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=87v84gi1v4.fsf@kernel.org \
--to=kvalo@kernel.org \
--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