public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Luke-Jr <luke@dashjr.org>
To: sclark46@earthlink.net
Cc: Lee Revell <rlrevell@joe-job.com>,
	Alistair John Strachan <s0348365@sms.ed.ac.uk>,
	Panagiotis Issaris <takis.issaris@uhasselt.be>,
	linux-kernel@vger.kernel.org, linux-netdev@vger.kernel.org
Subject: Re: WLAN drivers
Date: Sun, 5 Feb 2006 03:46:45 +0000	[thread overview]
Message-ID: <200602050346.48198.luke@dashjr.org> (raw)
In-Reply-To: <43E39E77.90403@earthlink.net>

On Friday 03 February 2006 18:18, Stephen Clark wrote:
> The module includes a binary hal module that keeps the card from being
> abused - programmed out of FCC specs. Why is so different from a card that
> has to have firmware loaded on it that in essence does the same thing -
> prevents the driver writer from programming the card out of FCC specs.

How about let the user decide to comply with FCC (or not)? Maybe it's been 
exported? Maybe the user has a hack to make it receive an AM radio signal? 
Plenty of legal possibilities.

  parent reply	other threads:[~2006-02-05  3:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-03 12:18 WLAN drivers Panagiotis Issaris
2006-02-03 12:35 ` Alistair John Strachan
2006-02-03 18:06   ` Lee Revell
2006-02-03 18:18     ` Stephen Clark
2006-02-03 18:33       ` Lee Revell
2006-02-05  3:46       ` Luke-Jr [this message]
2006-02-03 19:14     ` Alistair John Strachan
2006-02-03 19:19       ` Joel Jaeggli
2006-02-03 19:35       ` Lee Revell
2006-02-03 18:44   ` Lee Revell
2006-02-03 14:24 ` Denis Vlasenko
2006-02-03 18:49 ` Jan Kiszka
     [not found] ` <mailman.1138977902.23981.linux-kernel2news@redhat.com>
2006-02-03 19:14   ` Pete Zaitcev
2006-02-03 19:22     ` Alistair John Strachan
2006-02-03 19:38       ` Lee Revell
2006-02-14 16:07     ` David Gómez
2006-02-03 19:32 ` Alessandro Suardi

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=200602050346.48198.luke@dashjr.org \
    --to=luke@dashjr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-netdev@vger.kernel.org \
    --cc=rlrevell@joe-job.com \
    --cc=s0348365@sms.ed.ac.uk \
    --cc=sclark46@earthlink.net \
    --cc=takis.issaris@uhasselt.be \
    /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