From: "John W. Linville" <linville@tuxdriver.com>
To: Oliver Neukum <oliver@neukum.org>
Cc: Jon Masters <jcm@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] binary firmware and modules
Date: Mon, 17 Apr 2006 10:22:19 -0400 [thread overview]
Message-ID: <20060417142214.GI5042@tuxdriver.com> (raw)
In-Reply-To: <200604151154.22787.oliver@neukum.org>
On Sat, Apr 15, 2006 at 11:54:22AM +0200, Oliver Neukum wrote:
> Am Samstag, 15. April 2006 10:10 schrieb Jon Masters:
> > The attached patch introduces MODULE_FIRMWARE as one way of advertising
> Strictly speaking, what is the connection with modules? Statically
The same as MODULE_AUTHOR, MODULE_LICENSE, etc. The divide is more
logical than physical.
> compiled drivers need their firmware, too. Secondly, do all drivers
> know at compile time which firmware they'll need?
They have to know what they will request, do they not?
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2006-04-17 14:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-15 8:10 [RFC] binary firmware and modules Jon Masters
2006-04-15 9:54 ` Oliver Neukum
2006-04-17 14:22 ` John W. Linville [this message]
2006-04-17 14:29 ` Arjan van de Ven
2006-04-17 14:38 ` Marcel Holtmann
2006-04-17 15:15 ` Duncan Sands
2006-04-17 16:10 ` Marcel Holtmann
2006-04-18 13:16 ` Jon Masters
2006-04-18 13:37 ` Duncan Sands
2006-04-18 14:14 ` Jon Masters
2006-04-18 15:14 ` Duncan Sands
2006-04-19 0:01 ` Jon Masters
2006-04-18 14:22 ` Marcel Holtmann
2006-04-18 14:59 ` Duncan Sands
2006-04-18 15:41 ` Marcel Holtmann
2006-04-19 13:28 ` Mark Lord
2006-04-19 13:37 ` Marcel Holtmann
2006-04-19 14:10 ` Jon Masters
2006-04-18 14:25 ` Marcel Holtmann
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=20060417142214.GI5042@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=jcm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@neukum.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.