From: Jeff Garzik <jeff@garzik•org>
To: David Woodhouse <dwmw2@infradead•org>
Cc: e1000-devel@lists•sourceforge.net, netdev@vger•kernel.org,
Auke Kok <auke-jan.h.kok@intel•com>,
Jaswinder Singh <jaswinderlinux@gmail•com>
Subject: Re: [PATCH] firmware: convert e100 driver to request_firmware()
Date: Sun, 15 Jun 2008 15:00:06 -0400 [thread overview]
Message-ID: <485566B6.4030206@garzik.org> (raw)
In-Reply-To: <1213555326.26255.518.camel@pmac.infradead.org>
David Woodhouse wrote:
> 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.
Of course you can. That's where we keep binary firmwares now -- with
the drivers.
And, shockingly enough, it makes maintenance nice and easy to keep
everything in one location.
> 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.
You have not built any logical connection with this statement.
Kernel modules are installed via 'make modules_install', and we don't
have any special directory requirements for that.
There is absolutely no reason why 'make firmware_install' cannot work on
firmwares in existing directories.
Jeff
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
next prev parent reply other threads:[~2008-06-15 19:00 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
2008-06-15 19:00 ` Jeff Garzik [this message]
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=485566B6.4030206@garzik.org \
--to=jeff@garzik$(echo .)org \
--cc=auke-jan.h.kok@intel$(echo .)com \
--cc=dwmw2@infradead$(echo .)org \
--cc=e1000-devel@lists$(echo .)sourceforge.net \
--cc=jaswinderlinux@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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