netdev - Re: [PATCH] firmware: convert e100 driver to 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]

Date:	Sun, 15 Jun 2008 19:42:05 +0100
From:	David Woodhouse <dwmw2@...radead.org>
To:	Jaswinder Singh <jaswinderlinux@...il.com>
Cc:	Jeff Garzik <jeff@...zik.org>, netdev@...r.kernel.org,
	e1000-devel@...ts.sourceforge.net,
	Auke Kok <auke-jan.h.kok@...el.com>
Subject: Re: [PATCH] firmware: convert e100 driver to request_firmware()

On Mon, 2008-06-16 at 00:04 +0530, Jaswinder Singh wrote:
> driver source code will goto drivers directory and firmware will goto
> firmware directory.
> Please let us know, how can we keep them in same directory.

Realistically speaking, we can't. Although we'll preserve the option to
build firmware blobs into the kernel image, the primary means of using
them should be running 'make firmware_install' and having them put
into /lib/firmware. It's better for them to be in the firmware/
directory.

If we had the source it might make a _certain_ amount of sense to keep
it with the driver, but this is just a binary blob which we received
from the manufacturer and can't modify anyway (and haven't updated since
the git tree began). It doesn't really help to keep it with the driver.

-- 
dwmw2

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html