mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Thomas Tuttle <thinkinginbinary@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	Thorsten Kranzkowski <dl8bcu@dl8bcu.de>,
	Alon Bar-Lev <alon.barlev@gmail.com>,
	"John W. Linville" <linville@tuxdriver.com>,
	joesmidt@byu.net
Subject: Re: Will there be Intel Wireless 3945ABG support?
Date: Wed, 12 Jul 2006 09:19:44 +0100	[thread overview]
Message-ID: <200607120919.44561.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <20060712004212.GA26712@phoenix>

On Wednesday 12 July 2006 01:42, Thomas Tuttle wrote:
> 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.

If you give Matthieu's link[1] a quick read, the OpenBSD developer that 
reverse engineered the regulatory blob seems to indicate that the FCC 
regulations are just an excuse, so Intel can hide their IP inside the blob.

I'm not sure to what extent this is accurate, but it would seem that you would 
leave the driver functionally impaired if you simply removed the regulatory 
checks.

[1] http://kerneltrap.org/node/6650

-- 
Cheers,
Alistair.

Final year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.

  parent reply	other threads:[~2006-07-12  8: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
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 [this message]
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=200607120919.44561.s0348365@sms.ed.ac.uk \
    --to=s0348365@sms.ed.ac.uk \
    --cc=alon.barlev@gmail.com \
    --cc=dl8bcu@dl8bcu.de \
    --cc=joesmidt@byu.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=thinkinginbinary@gmail.com \
    /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®