Received-SPF: pass (google.com: domain of linux-wireless+bounces-6446-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:40f1:3f00::1 as permitted sender) client-ip=2604:1380:40f1:3f00::1;
Message-ID: <f65765b29ea7503fbbaa5e047c95a82de6fc2083.camel@sipsolutions.net>
Subject: Re: putting future iwlwifi firmware into intel/ ?
From: Johannes Berg <johannes@sipsolutions.net>
To: Mario Limonciello <superm1@gmail.com>, linux-firmware@kernel.org
Cc: linux-wireless@vger.kernel.org, miriam.rachel.korenblit@intel.com
Date: Wed, 17 Apr 2024 14:39:39 +0200
In-Reply-To: <9aa64d50-cb4d-4118-bc27-86c23410ff8b@gmail.com>
References: 
	<fec30176f437d565d4c1dfc4944373f117d75a64.camel@sipsolutions.net>
	 <9aa64d50-cb4d-4118-bc27-86c23410ff8b@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.50.4 (3.50.4-1.fc39) 
Precedence: bulk
MIME-Version: 1.0

On Wed, 2024-04-17 at 07:31 -0500, Mario Limonciello wrote:
>=20
> On 4/17/24 06:18, Johannes Berg wrote:
> > Hi,
> >=20
> > 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 tha=
t
> > just over 30% of the files/dirs in the top-level firmware tree are
> > iwlwifi-* files.
> >=20
> > While we can't move the files that older drivers might consume, we coul=
d
> > e.g. change the driver to look up future versions/future hardware under
> > intel/ instead? Would that be worth doing?
> >=20
> > johannes
> >=20
>=20
> How about moving them all now and then creating compat symlinks for=20
> older kernels at linux-firmware 'make install' time?
>=20

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