From: Alon Bar-Lev <alon.barlev@gmail.com>
To: Alistair John Strachan <s0348365@sms.ed.ac.uk>
Cc: "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 21:25:45 +0300 [thread overview]
Message-ID: <44B3ED29.4040801@gmail.com> (raw)
In-Reply-To: <200607111909.22972.s0348365@sms.ed.ac.uk>
Alistair John Strachan wrote:
> On Tuesday 11 July 2006 18:12, John W. Linville wrote:
>> On Tue, Jul 11, 2006 at 10:32:43AM -0600, Joseph Michael Smidt wrote:
>>> Will 2.6.18 or 2.6.19 support Intel Wireless 3945ABG? Please cc me since
>>> I am not subscribed. Thanks.
>> It will not be in 2.6.18. Making 2.6.19 is not out of the question,
>> but it may take some work.
>
> Has some agreement been met regarding the mandatory use of the binary
> regulatory daemon? The webpage seems to suggest it is still necessary, and
> I'm sure that would disqualify merging the driver with Linux proper.
>
Why not?
The whole point is running a system that you know you can support for many years,
even without a vendor support...
And to have a system that you know exactly what running in it...
Having a binary closed source violate this.
Also there is no good reason why supplying this daemon as closed source... All they
wish is people don't mess with their frequencies, and sooner or later someone will...
Best Regards,
Alon Bar-Lev.
next prev parent reply other threads:[~2006-07-11 18:26 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 [this message]
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
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=44B3ED29.4040801@gmail.com \
--to=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