Re: putting future iwlwifi firmware into intel/ ?

[Johannes Berg <johannes@sipsolutions.net>]

On Wed, 2024-04-17 at 07:42 -0500, Mario Limonciello wrote:
> 
> 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.

Yeah, I guess. Though not actually sure, do we need to support new
kernel + old firmware install?

johannes