From: Stephen Hemminger <shemminger@osdl.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Christoph Hellwig <hch@infradead.org>,
James Ketrenos <jketreno@linux.intel.com>,
NetDev <netdev@vger.kernel.org>,
linux-kernel@vger.kernel.org, okir@suse.de
Subject: Re: [Announce] Intel PRO/Wireless 3945ABG Network Connection
Date: Mon, 27 Feb 2006 09:34:04 -0800 [thread overview]
Message-ID: <20060227093404.4020ac6a@localhost.localdomain> (raw)
In-Reply-To: <20060227171029.GA763@infradead.org>
On Mon, 27 Feb 2006 17:10:29 +0000
Christoph Hellwig <hch@infradead.org> wrote:
> On Sun, Feb 26, 2006 at 12:58:02AM +0000, Alan Cox wrote:
> > On Sad, 2006-02-25 at 08:41 +0000, Christoph Hellwig wrote:
> > > the regualatory problems are not true.
> >
> > They are although the binary interpretation isn't AFAIK from law but
> > from lawyers. The same is actually true in much of the EU. The actual
> > requirement is that the transmitting device must be reasonably
> > tamperproof. Some of the lawyers have decided that for a software radio
> > tamperproof means "binary".
>
> Exactly. There's no strong requirement, it's just over-zealous corporate
> lawyers. That's why we need to push Intel strongly here.
It is not Intel, but the regulators that need a stronger clue. Vendors
don't have any incentive to force change on this. They just want to sell
as much hardware as possible.
Does anyone know who the actual FCC administrators in charge of this are?
next prev parent reply other threads:[~2006-02-27 17:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-24 22:29 [Announce] Intel PRO/Wireless 3945ABG Network Connection 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
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 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 [this message]
2006-03-03 20:04 ` Kasper Sandberg
2006-03-03 20:31 ` Jeff Garzik
2006-02-26 17:54 ` Pavel Machek
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=20060227093404.4020ac6a@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hch@infradead.org \
--cc=jketreno@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=okir@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).