From: Greg KH <greg@kroah.com>
To: Pavel Roskin <proski@gnu.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Preferred way to load non-free firmware
Date: Tue, 25 Mar 2003 20:11:46 -0800 [thread overview]
Message-ID: <20030326041146.GD20858@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.50.0303252007420.6656-100000@marabou.research.att.com>
On Tue, Mar 25, 2003 at 08:32:50PM -0500, Pavel Roskin wrote:
>
> 1) Register a file on procfs and use "cat" to load the firmware into the
> kernel.
That would work.
> 2) Register a device for the same purpose.
>
> 3) Register a device, but use ioctl().
>
> 4) Open a network socket and use ioctl() on it (like ifconfig does).
That's a nice way, as you don't need to register a device.
> 5) Use one of the the above ways to send the filename to the module and
> let the module load the firmware from file using do_generic_file_read().
Ick, I wouldn't recommend having the kernel do this, it's nicer to have
userspace do the firmware send.
> 6) Provide a script to wrap firmware into a module and load it using
> modprobe.
I don't think that this would be accepted into the main kernel tree, and
vendors might have a problem with it.
> 7) Encode the firmware into a header file, add it to the driver and
> pretend that the copyright issue doesn't exist (like it's done in the
> Keyspan USB driver).
Hey, that's the way I like doing this stuff :)
Almost any of the above would probably work well, and I think all except
#5 and #6 are currently done in the main kernel tree.
Good luck,
greg k-h
next prev parent reply other threads:[~2003-03-26 4:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-26 1:32 Pavel Roskin
2003-03-26 4:11 ` Greg KH [this message]
2003-03-26 10:48 ` Nick Craig-Wood
2003-03-26 12:47 ` Oliver Neukum
2003-03-26 13:52 ` Jeremy Jackson
2003-03-26 16:19 ` Oliver Neukum
2003-03-26 10:51 ` Erik Hensema
[not found] <Pine.LNX.4.50.0303252007420.6656-100000@marabou.research.a tt.com>
2003-03-27 1:38 ` Max Krasnyansky
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=20030326041146.GD20858@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=proski@gnu.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
all inboxes | Powered by JetHome®