From: David Woodhouse <dwmw2@infradead.org>
To: Jaswinder Singh <jaswinderlinux@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>,
netdev@vger.kernel.org, e1000-devel@lists.sourceforge.net,
Auke Kok <auke-jan.h.kok@intel.com>
Subject: Re: [PATCH] firmware: convert e100 driver to request_firmware()
Date: Sun, 15 Jun 2008 19:42:05 +0100 [thread overview]
Message-ID: <1213555326.26255.518.camel@pmac.infradead.org> (raw)
In-Reply-To: <3f9a31f40806151134n1b5e4de7m2ccd9c8a9e98cdb4@mail.gmail.com>
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
next prev parent reply other threads:[~2008-06-15 18:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-15 9:42 [PATCH] firmware: convert e100 driver to request_firmware() David Woodhouse
2008-06-15 17:50 ` Jeff Garzik
2008-06-15 17:51 ` David Woodhouse
2008-06-15 18:07 ` Jeff Garzik
2008-06-15 18:34 ` Jaswinder Singh
2008-06-15 18:42 ` David Woodhouse [this message]
2008-06-15 19:00 ` Jeff Garzik
2008-06-15 18:44 ` Jeff Garzik
2008-06-15 22:09 ` David Woodhouse
2008-06-15 23:30 ` Jeff Garzik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1213555326.26255.518.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=auke-jan.h.kok@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jaswinderlinux@gmail.com \
--cc=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).