linux-kernel - Re: RFC: install firmware in a kernel-dependent directory

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: <499722DF.3020208@googlemail.com>
Date:	Sat, 14 Feb 2009 21:00:31 +0100
From:	Michael Riepe <michael.riepe@...glemail.com>
To:	Jaswinder Singh Rajput <jaswinderlinux@...il.com>,
	linux-kernel@...r.kernel.org
CC:	David Woodhouse <dwmw2@...radead.org>
Subject: Re: RFC: install firmware in a kernel-dependent directory

Hi!

Jaswinder Singh Rajput wrote:

> firmware version depends on hardware version not by kernel (software) version.

That means that it shouldn't be delivered with the kernel in the first
place, right? Neither built in nor as a separate file. Maybe that's an
even better solution: distribute it separately.

Which firmware to use is a matter of policy, in my opinion. I may want
to use a modified firmware, for example, and put that into /lib/firmware
where it belongs. But each time I install a new kernel, it will be
replaced with the standard version.

-- 
Michael "Tired" Riepe <michael.riepe@...glemail.com>
X-Tired: Each morning I get up I die a little
--
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/