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]

Date:	Thu, 11 Sep 2008 13:57:38 -0700
From:	Greg KH <greg@...ah.com>
To:	David Woodhouse <dwmw2@...radead.org>
Cc:	Marcel Holtmann <marcel@...tmann.org>,
	Thierry Vignaud <tvignaud@...driva.com>,
	David Miller <davem@...emloft.net>, jeffm@...e.com,
	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	torvalds@...ux-foundation.org
Subject: Re: [PATCH] firmware: Allow release-specific firmware dir

On Thu, Sep 11, 2008 at 01:38:38PM -0700, David Woodhouse wrote:
> On Thu, 2008-09-11 at 13:15 -0700, Greg KH wrote:
> > This is the firmware that is in the kernel source tree, that has been
> > moved to use request_firmware, and was originally tied tightly to the
> > kernel drivers themselves.
> 
> Not really. Most of it hasn't changed for years; it isn't _really_ tied
> that closely to the kernel. 

Some are and some aren't (I have two in my -staging tree that are
changing as the driver changes, so it does happen.)

> You can just ignore what the kernel ships with, and install the firmware
> from the linux-firmware.git repository instead.

So you are now forcing distros to ship the linux-firmware.git repo
instead?  That's not nice and is a totally new dependancy for them to
handle.

What about the very basic fact that kernel versions will stomp on files
from other kernel versions if you install multiple kernels on the same
machine?  That's just bad and ripe for problems in any package
management system.

thanks,

greg k-h
--
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/