From: David Miller <davem@davemloft.net>
To: jketreno@linux.intel.com
Cc: alan@lxorguk.ukuu.org.uk, alon.barlev@gmail.com,
s0348365@sms.ed.ac.uk, linville@tuxdriver.com, joesmidt@byu.net,
linux-kernel@vger.kernel.org
Subject: Re: Will there be Intel Wireless 3945ABG support?
Date: Tue, 11 Jul 2006 18:19:51 -0700 (PDT) [thread overview]
Message-ID: <20060711.181951.56872620.davem@davemloft.net> (raw)
In-Reply-To: <44B443E4.1000707@linux.intel.com>
From: James Ketrenos <jketreno@linux.intel.com>
Date: Tue, 11 Jul 2006 17:35:48 -0700
> The obvious distinction between scsi firmware and the regulatory
> daemon blob being discussed here is that the regulatory daemon runs
> on the host vs. an adapter. However, if you consider the
> communication interface between the kernel and the user space daemon
> to be analogous to the communication interface between the kernel
> driver and the firmware that runs on an adapter, then the
> distinction of running on the host is irrelevant.
The core issue is whether the userland blob could stand alone and is
something that could exist independant of Linux and the kernel side
GPL'd driver.
Difficult areas arise when you design a set of interfaces specifically
to talk to the binary blob, and which exist for no other purpose and
do not provide some well defined "standard" API such as the SCSI
command set, as an example. It is just a backdoor into the binary
blob, and therefore this could make it more likely to be considered
a derivative work.
Firmware that runs on the card is also a tricky area, and not everyone
agrees on that issue as well.
Unfortunately, none of this is fun stuff :-/
next prev parent reply other threads:[~2006-07-12 1:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-11 16:32 Joseph Michael Smidt
2006-07-11 16:47 ` Otavio Salvador
2006-07-11 17:12 ` John W. Linville
2006-07-11 18:09 ` Alistair John Strachan
2006-07-11 18:25 ` Alon Bar-Lev
2006-07-11 18:43 ` Alistair John Strachan
2006-07-11 18:55 ` Alan Cox
2006-07-11 19:18 ` Matthieu CASTET
2006-07-11 20:22 ` Daniel Bonekeeper
2006-07-11 22:22 ` Matthew Garrett
2006-07-11 23:54 ` H. Peter Anvin
2006-07-12 0:04 ` Matthew Garrett
2006-07-12 0:35 ` James Ketrenos
2006-07-12 1:19 ` David Miller [this message]
2006-07-12 11:30 ` Alan Cox
2006-07-12 17:17 ` Alon Bar-Lev
2006-07-12 22:09 ` David Schwartz
2006-07-11 20:16 ` Thorsten Kranzkowski
2006-07-12 0:42 ` Thomas Tuttle
2006-07-12 0:57 ` H. Peter Anvin
2006-07-12 1:10 ` David Miller
2006-07-12 1:15 ` Valdis.Kletnieks
2006-07-12 8:19 ` Alistair John Strachan
2006-07-12 8:23 ` Alistair John Strachan
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=20060711.181951.56872620.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alon.barlev@gmail.com \
--cc=jketreno@linux.intel.com \
--cc=joesmidt@byu.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=s0348365@sms.ed.ac.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®