From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Downing, Thomas" <Thomas.Downing@ipc.com>
Cc: Simon Kelley <simon@thekelleys.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: RE: Binary firmware in the kernel - licensing issues.
Date: 06 May 2003 13:46:41 +0100 [thread overview]
Message-ID: <1052225199.1202.4.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <170EBA504C3AD511A3FE00508BB89A9202085B63@exnanycmbx4.ipc.com>
On Maw, 2003-05-06 at 13:54, Downing, Thomas wrote:
> PS: what would be the preferred place to load the firmware
> from, if no option giving the firmware pathname is passed to the
> module at load time?
When a device appears the /sbin/hotplug scripts are called. They
could either load the firmware themselves (since the usbdevfs allows
you to talk directly to the device), or could make a call to give
the firmware to the driver (eg ioctl)
next prev parent reply other threads:[~2003-05-06 13:32 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 12:54 Downing, Thomas
2003-05-06 12:46 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-08 23:36 Adam J. Richter
2003-05-08 16:51 Adam J. Richter
2003-05-08 16:35 Adam J. Richter
2003-05-08 18:26 ` root
2003-05-08 22:19 ` Alan Cox
2003-05-08 15:59 Adam J. Richter
2003-05-08 16:09 ` Jörn Engel
2003-05-08 13:20 Downing, Thomas
2003-05-07 17:14 Adam J. Richter
2003-05-07 11:59 Adam J. Richter
2003-05-07 14:08 ` Simon Kelley
2003-05-06 15:04 Adam J. Richter
2003-05-06 11:38 Simon Kelley
2003-05-06 11:15 ` Alan Cox
2003-05-06 13:28 ` Simon Kelley
2003-05-06 12:44 ` Alan Cox
2003-05-06 13:42 ` Simon Kelley
2003-05-06 12:19 ` Matti Aarnio
2003-05-06 15:16 ` J. Bruce Fields
2003-05-06 15:42 ` Simon Kelley
2003-05-06 15:21 ` Alan Cox
2003-05-07 6:52 ` Simon Kelley
2003-05-07 9:07 ` Filip Van Raemdonck
2003-05-07 9:54 ` Simon Kelley
2003-05-08 8:01 ` Filip Van Raemdonck
2003-05-08 9:44 ` Simon Kelley
2003-05-08 10:56 ` Alan Cox
2003-05-06 15:48 ` Richard B. Johnson
2003-05-06 15:19 ` Alan Cox
2003-05-08 10:20 ` Jörn Engel
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=1052225199.1202.4.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Thomas.Downing@ipc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=simon@thekelleys.org.uk \
/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
all inboxes | Powered by JetHome®