public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Tuttle <thinkinginbinary@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Thorsten Kranzkowski <dl8bcu@dl8bcu.de>,
	Alon Bar-Lev <alon.barlev@gmail.com>,
	Alistair John Strachan <s0348365@sms.ed.ac.uk>,
	"John W. Linville" <linville@tuxdriver.com>,
	joesmidt@byu.net
Subject: Re: Will there be Intel Wireless 3945ABG support?
Date: Tue, 11 Jul 2006 20:42:12 -0400	[thread overview]
Message-ID: <20060712004212.GA26712@phoenix> (raw)
In-Reply-To: <20060711201615.GB11871@Marvin.DL8BCU.ampr.org>

[-- Attachment #1: Type: text/plain, Size: 1979 bytes --]

On July 11 at 16:16 EDT, Thorsten Kranzkowski hastily scribbled:
> On Tue, Jul 11, 2006 at 09:25:45PM +0300, Alon Bar-Lev wrote:
> > 
> > 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...
> 
> Using interesting frequencies or output power would be fun for
> radio amateurs (like me). 2.4GHz is one of our playgrounds after all :-)

Hear, hear!

> Just because Joe Average isn't allowed to use such features doesn't
> mean that there aren't any legitimate users for it.
>  
> Preventing the accidental use of unauthorized features would be enough, 
> I think (warnings that force you to look up the manual to find out the
> correct --force option or similar)
> I expect developers to be sensible enough to only offer 'public legal'
> values in the default options list.

Frankly, I think Intel is misinterpreting how strict the FCC is being
(or maybe the FCC is being too strict).  I would interpret their
mandates as meaning that, as purchased, equipment can't transmit on
unauthorized frequencies, and that it's not "user-modifiable".  User
modification doesn't include things like opening the case of a toy
walkie-talkie up and swapping out a crystal, nor does it include things
like opening up the firmware or driver for something and messing with
it.

Frankly, I'm annoyed that, if Intel understood the full extent of the
problem, that they didn't take a better approach and simply give the
card a set of legal values.  It doesn't need to understand the
subtleties of what they mean.  It just needs to know frequencies 1, 2,
and 3 are okay, but not 4, 5, and 6, and that the max power is xx dBm.

OTOH, I'd love to get one of these cards and play with it.  I'd love a
WiFi card that can run up to 5 or 10 watts.  (1500 is a little much, and
my laptop's battery can't supply it :-)

-- Thomas Tuttle

[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]

  reply	other threads:[~2006-07-12  0:43 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
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 [this message]
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=20060712004212.GA26712@phoenix \
    --to=thinkinginbinary@gmail.com \
    --cc=alon.barlev@gmail.com \
    --cc=dl8bcu@dl8bcu.de \
    --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