From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Alon Bar-Lev <alon.barlev@gmail.com>
Cc: 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: Tue, 11 Jul 2006 19:55:19 +0100 [thread overview]
Message-ID: <1152644119.18028.46.camel@localhost.localdomain> (raw)
In-Reply-To: <44B3ED29.4040801@gmail.com>
Ar Maw, 2006-07-11 am 21:25 +0300, ysgrifennodd Alon Bar-Lev:
> And to have a system that you know exactly what running in it...
> Having a binary closed source violate this.
Also if the binary only chunk of code is neccessary to make the open
source bit work then its a derivative work as I understand the
situation, which makes it all rather questionable from a licensing
perspsective.
Hopefully Intel will find a sensible solution to the problem or someone
will just reverse engineer it away.
Alan
next prev parent reply other threads:[~2006-07-11 18:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-11 16:32 Will there be Intel Wireless 3945ABG support? 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 [this message]
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
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=1152644119.18028.46.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=alon.barlev@gmail.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