mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: James Ketrenos <jketreno@linux.intel.com>
Cc: Alon Bar-Lev <alon.barlev@gmail.com>,
	Alistair John Strachan <s0348365@sms.ed.ac.uk>,
	"John W. Linville" <linville@tuxdriver.com>,
	joesmidt@byu.net, linux-kernel@vger.kernel.org
Subject: Re: Will there be Intel Wireless 3945ABG support?
Date: Wed, 12 Jul 2006 12:30:39 +0100	[thread overview]
Message-ID: <1152703839.22943.15.camel@localhost.localdomain> (raw)
In-Reply-To: <44B443E4.1000707@linux.intel.com>

Ar Maw, 2006-07-11 am 17:35 -0700, ysgrifennodd James Ketrenos:
> 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.  

"It isn't a pirate copy of the movie because my copy is on VHS and
theirs is on DVD"

Derivative works are not really a question of where something is, think
about a distributed computation, or a tool which partly compiles a
program into VHDL for high performance execution.

I'm not sure this is a useful kernel list argument anyway since I am
sure Intel legal will have considered the question and reached their own
conclusions and also vendors and Intel will continue beating each other
up until a neat solution is found.

> There are no questions from a licensing standpoint.

For Intel sure, if it owns all the bits then it can do what it likes
with its bits.


> To that end I would encourage anyone that may be interested in using
> such a piece of code to read the regulatory notice packaged with our
> drivers, and linked for your reference here[1].

Oh I understand *why* the issue arises, and as a licensed radio amateur
I'm quite well aware of the concerns. I'm also permitted to use 2.4Ghz
at higher power for amateur purposes.

Alan

  parent reply	other threads:[~2006-07-12 11:13 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
2006-07-12 11:30           ` Alan Cox [this message]
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=1152703839.22943.15.camel@localhost.localdomain \
    --to=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®