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: <20080529204736.GZ22636@parisc-linux.org>
Date:	Thu, 29 May 2008 14:47:36 -0600
From:	Matthew Wilcox <matthew@....cx>
To:	Arjan van de Ven <arjan@...ux.intel.com>
Cc:	Greg KH <greg@...ah.com>, James.Bottomley@...senPartnership.com,
	ksummit-2008-discuss@...ts.linux-foundation.org,
	David Woodhouse <dwmw2@...radead.org>,
	David Miller <davem@...emloft.net>,
	linux-kernel@...r.kernel.org
Subject: Re: [Ksummit-2008-discuss] RFC: Moving firmware blobs out of	the kernel.

On Thu, May 29, 2008 at 01:29:38PM -0700, Arjan van de Ven wrote:
> I very much would like to see a kernel-firmware or something tarbal that contains
> a copy of all relevant "freely distributable" firmware, that users can just install
> independent of the actual kernel version (and that kbuild would just pick up somehow).
> That way we can deal with a lot more firmware without having to pollute the kernel / kernel release process
> (after all, the timing is different in terms of releasing) while making it easy
> to get the lot of it.

There's definitely two schools of thought on this.  Sometimes firmware
changes (or adds) an interface.  If the kernel driver has to accommodate
new and old firmware, that adds complexity, and we all know that added
complexity means more bugs.  So I can definitely see some vendors
wanting to distribute their firmware with the kernel.

-- 
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ