public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org,
	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 17:57:26 -0700	[thread overview]
Message-ID: <44B448F6.5060508@zytor.com> (raw)
In-Reply-To: <20060712004212.GA26712@phoenix>

Thomas Tuttle wrote:
> 
> 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.
> 

Unfortunately you're wrong.  Some manufacturers have gotten rapped for 
marketing equipment that can be modded by stuff like desoldering diodes.

The FCC has some incredibly heavy-weight regulations, like:

- Problem: unlicensed high-power CB operation
- Solution: ban amplifiers that work anywhere near the CB band, 
including several amateur radio bands (even for sale to users with valid 
amateur licenses)

- Problem: unencrypted cell phones
- Solutions: ban scanners that work on the cell phone bands

... etc ...

	-hpa

  reply	other threads:[~2006-07-12  0:58 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
2006-07-12  0:57           ` H. Peter Anvin [this message]
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=44B448F6.5060508@zytor.com \
    --to=hpa@zytor.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