linux-kernel - Re: Staging: sxg: Add support to download the firmware using request

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: <20090406023349.GA1314@suse.de>
Date:	Sun, 5 Apr 2009 19:33:49 -0700
From:	Greg KH <gregkh@...e.de>
To:	David Woodhouse <dwmw2@...radead.org>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Mithlesh Thukral <mithlesh@...syssoft.com>,
	Christopher Harrer <charrer@...critech.com>
Subject: Re: Staging: sxg: Add support to download the firmware using
	request_firmware()

On Sun, Apr 05, 2009 at 06:19:55PM -0700, David Woodhouse wrote:
> On Sun, 2009-04-05 at 18:07 -0700, Greg KH wrote:
> > Who do we email to add this to?
> 
> Clone git.kernel.org/pub/scm/linux/kernel/git/dwmw2/linux-firmware.git,
> add your firmware (and update the WHENCE file accordingly), and send me
> a pull request. Preferably with a Signed-off-by: from within the company
> that owns the firmware in question.

Care to document this somewhere in the kernel tree so we know about it?

> > And finally, what's wrong with adding new firmware images into the
> > firmware/ directory?  What is the issue here?
> 
> We're working on _removing_ this crap from the kernel source tree -- not
> adding new instances of it.

Firmware isn't "crap", it's needed by devices, and I don't see the
problem of distributing it within the kernel tree, especially when the
license of the firmware is just fine, like these files are.

> We have a separate repository in which we're collecting
> redistributable firmware images, and the distributions are moving
> towards shipping that instead of just the legacy stuff from the kernel
> tree. Add any new firmware to that repository instead, as described
> above.

Are there releases of the firmware tree published and announced
anywhere so the distros know to do this?

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/