mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Max Krasnyansky <maxk@qualcomm.com>
To: Pavel Roskin <proski@gnu.org>, linux-kernel@vger.kernel.org
Subject: Re: Preferred way to load non-free firmware
Date: Wed, 26 Mar 2003 17:38:57 -0800	[thread overview]
Message-ID: <5.1.0.14.2.20030326173416.0efdc710@unixmail.qualcomm.com> (raw)
In-Reply-To: <Pine.LNX.4.50.0303252007420.6656-100000@marabou.research.a tt.com>

At 05:32 PM 3/25/2003, Pavel Roskin wrote:
>Hello!
>
>I'm writing a Linux device driver for a device that requires non-free
>firmware in order to function.  The firmware can be easily extracted from
>the Windows driver for that device.  The device is a PCMCIA wireless card.
>
>The firmware is about 60k in size, and it mostly consists of executable
>code for ARM processor.  Reimplementing it is out of question for me.
>
>What would be the best approach to handle this situation:
>
>1) Register a file on procfs and use "cat" to load the firmware into the
>kernel.
>
>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).
>
>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().
>
>6) Provide a script to wrap firmware into a module and load it using
>modprobe.
>
>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).
>
>Better ideas?

8) Have the driver call external user-space firmware loader that uses
either iopl/outb/inb or mmap(/dev/mem) and loads firmware directly.

Max






       reply	other threads:[~2003-03-27  1:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.50.0303252007420.6656-100000@marabou.research.a tt.com>
2003-03-27  1:38 ` Max Krasnyansky [this message]
2003-03-26  1:32 Pavel Roskin
2003-03-26  4:11 ` Greg KH
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

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=5.1.0.14.2.20030326173416.0efdc710@unixmail.qualcomm.com \
    --to=maxk@qualcomm.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®