linux-kernel - Re: [PATCH] firmware: Allow release-specific firmware dir

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20080910.164220.56492718.davem@davemloft.net>
Date:	Wed, 10 Sep 2008 16:42:20 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	dwmw2@...radead.org
Cc:	jeffm@...e.com, linux-kernel@...r.kernel.org,
	akpm@...ux-foundation.org, torvalds@...ux-foundation.org,
	herbert@...dor.apana.org.au
Subject: Re: [PATCH] firmware: Allow release-specific firmware dir

From: David Woodhouse <dwmw2@...radead.org>
Date: Wed, 10 Sep 2008 16:36:56 -0700

> On Wed, 2008-09-10 at 16:24 -0700, David Miller wrote:
> > From: David Woodhouse <dwmw2@...radead.org>
> > Date: Wed, 10 Sep 2008 16:15:11 -0700
> > 
> > > It's definitely not something we should be doing upstream though.
> > 
> > So you think it's ok that every Debian user has to learn this
> > magic incantation just to use current kernels?
> 
> They don't. Debian uses firmware from /lib/firmware if it doesn't exist
> in /lib/firmware/$(version) -- so they can install to the normal
> location quite happily, and it should work just fine.

That's not what I've heard from people more clueful from me.

For example, Herbert Xu (CC:'d) told me that because of this directory
usage, his wireless card couldn't find it's firmware with current
kernels.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/