From: Michael Buesch <mbuesch@freenet.de>
To: Gene Heskett <gene.heskett@verizon.net>
Subject: Re: [Announce] Intel PRO/Wireless 3945ABG Network Connection
Date: Sat, 25 Feb 2006 14:19:56 +0100
User-Agent: KMail/1.8.3
References: <43FF88E6.6020603@linux.intel.com> <20060225105340.GA23643@infradead.org> <200602250619.04567.gene.heskett@verizon.net>
In-Reply-To: <200602250619.04567.gene.heskett@verizon.net>
Cc: Christoph Hellwig <hch@infradead.org>,
       James Ketrenos <jketreno@linux.intel.com>,
       NetDev <netdev@vger.kernel.org>, linux-kernel@vger.kernel.org
MIME-Version: 1.0
Content-Type: multipart/signed;
  boundary="nextPart32602744.TUGWFVttba";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <200602251419.56541.mbuesch@freenet.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2657
Lines: 60

--nextPart32602744.TUGWFVttba
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Saturday 25 February 2006 12:19, Gene Heskett wrote:
> On Saturday 25 February 2006 05:53, Christoph Hellwig wrote:
> >On Sat, Feb 25, 2006 at 05:49:47AM -0500, Gene Heskett wrote:
> >> As someone (a broadcast engineer with 40+ years of carrying what
> >> used to be a 1st phone) obviously more familiar with the FCC R&R
> >> than you apparently are, Christoph, I'll have to argue that point.
> >
> >Please stop spreading the bullshit.  Please quote the FCC regulation
> > on this.
>=20
> Its not "bullshit" as you so "eloquently" put it, Christoph.  As for=20
> looking it up, I'd imagine your ability to run a search engine at=20
> fcc.gov exceeds mine.  Hint, its probably in the section called "Rules=20
> that apply to all". These rules go back to about the time of when they=20
> outlawed any transmit tunability in CB radios in the later 70's, so its=20
> not a new item by any means as its just an extension of that edict to=20
> cover this newer technology. The fact that it effectively put a stop to=20
> conference call type use of single sideband because no 2 radios were on=20
> the same, now non-adjustable frequency was an undesirable thing, but=20
> thats the breaks.  I might try and look it up after I've had some zz's,=20
> as I just came from doing transmitter maintainance overnight.

Well, be it this or that way. I don't see how a binary blob is
able to prevent that the user operates the device on illegal
freqs. In fact, it is a void protection and is just inconvenient.
An open source regdomain implementation is just as safe against
modifications, as this binary blob. There is no point in doing this
binary.
In fact, if you really want to prevent people from doing
Something Bad (tm), you must take technologies such as Trusted Computing.
And even that can, by the opinion of many people, circumvented somehow.
The best way to prevent, that a device is driven on illegal freqs,
is by not selling the device.

=2D-=20
Greetings Michael.

--nextPart32602744.TUGWFVttba
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQBEAFl8lb09HEdWDKgRAsiQAKCKMdxVPv2X3fb5mMGOLWLujwcUiACgmG6H
hhGRwg2P6DAT/O202bUHH7g=
=Kynt
-----END PGP SIGNATURE-----

--nextPart32602744.TUGWFVttba--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/