From: Gene Heskett <gene.heskett@verizon.net>
To: Christoph Hellwig <hch@infradead.org>,
James Ketrenos <jketreno@linux.intel.com>,
NetDev <netdev@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [Announce] Intel PRO/Wireless 3945ABG Network Connection
Date: Sat, 25 Feb 2006 06:19:04 -0500 [thread overview]
Message-ID: <200602250619.04567.gene.heskett@verizon.net> (raw)
In-Reply-To: <20060225105340.GA23643@infradead.org>
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.
Its not "bullshit" as you so "eloquently" put it, Christoph. As for
looking it up, I'd imagine your ability to run a search engine at
fcc.gov exceeds mine. Hint, its probably in the section called "Rules
that apply to all". These rules go back to about the time of when they
outlawed any transmit tunability in CB radios in the later 70's, so its
not a new item by any means as its just an extension of that edict to
cover this newer technology. The fact that it effectively put a stop to
conference call type use of single sideband because no 2 radios were on
the same, now non-adjustable frequency was an undesirable thing, but
thats the breaks. I might try and look it up after I've had some zz's,
as I just came from doing transmitter maintainance overnight.
>> So basicly, you can accept it with the wrappers Intel provides, or
>> linux will not have access to the use of these devices, any of them
>> that fit in the category of "software radios".
>
>We have support for other software radios. If intel doesn't do the
> right thing support for their hardware will have to wait until
> someone has reverse-engineered their daemon [1].
>
>[1] they disallow it in their license, but that's completely void in
> many countries.
I don't think you'll find that to be the case here in the states.
--
Cheers, Gene
People having trouble with vz bouncing email to me should add the word
'online' between the 'verizon', and the dot which bypasses vz's
stupid bounce rules. I do use spamassassin too. :-)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
next prev parent reply other threads:[~2006-02-25 11:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-24 22:29 James Ketrenos
2006-02-24 23:34 ` Dax Kelson
2006-02-24 23:48 ` Jeff V. Merkey
2006-02-25 13:26 ` Michael Buesch
2006-02-25 8:41 ` Christoph Hellwig
2006-02-25 10:49 ` Gene Heskett
2006-02-25 10:53 ` Christoph Hellwig
2006-02-25 11:19 ` Gene Heskett [this message]
2006-02-25 13:19 ` Michael Buesch
2006-02-26 1:09 ` Stephen Evanchik
2006-02-25 12:29 ` Stefan Rompf
2006-02-25 14:19 ` Jan Engelhardt
2006-02-25 19:09 ` Gene Heskett
2006-02-25 19:41 ` Michael Buesch
2006-02-25 22:07 ` Matthieu CASTET
2006-02-25 22:19 ` John Stoffel
2006-02-25 22:28 ` matthieu castet
2006-02-25 22:47 ` Larry Finger
2006-02-26 20:20 ` Alejandro Bonilla
2006-02-26 0:58 ` Alan Cox
2006-02-27 17:10 ` Christoph Hellwig
2006-02-27 17:34 ` Stephen Hemminger
2006-03-03 20:04 ` Kasper Sandberg
2006-03-03 20:31 ` Jeff Garzik
2006-02-26 17:54 ` Pavel Machek
2006-02-27 14:27 ` Dick Streefland
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=200602250619.04567.gene.heskett@verizon.net \
--to=gene.heskett@verizon.net \
--cc=gene.heskett@verizononline.net \
--cc=hch@infradead.org \
--cc=jketreno@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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®