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]

Date:	Sat, 14 Feb 2009 21:50:16 +0100
From:	David Woodhouse <dwmw2@...radead.org>
To:	Michael Riepe <michael.riepe@...glemail.com>
Cc:	Jaswinder Singh Rajput <jaswinderlinux@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: RFC: install firmware in a kernel-dependent directory

On Sat, 2009-02-14 at 21:00 +0100, Michael Riepe wrote:
>  
> 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.

We do. See the linux-firmware.git repository, which contains a bunch of
extra firmware too; not just the bits we've stripped out of legacy
drivers.

You can completely ignore the firmware that's shipped with the kernel,
and you're right -- it should go away. In time I hope it will.

-- 
dwmw2

--
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/