From: dick.streefland@altium.nl (Dick Streefland)
To: linux-kernel@vger.kernel.org
Subject: Re: [Announce] Intel PRO/Wireless 3945ABG Network Connection
Date: Mon, 27 Feb 2006 14:27:17 -0000 [thread overview]
Message-ID: <698.44030c45.bc404@altium.nl> (raw)
In-Reply-To: 43FF88E6.6020603@linux.intel.com
James Ketrenos <jketreno@linux.intel.com> wrote:
| As a result of this change, some of the capabilities currently required
| to be provided on the host include enforcement of regulatory limits for
| the radio transmitter (radio calibration, transmit power, valid
| channels, 802.11h, etc.) In order to meet the requirements of all
| geographies into which our adapters ship (over 100 countries) we have
| placed the regulatory enforcement logic into a user space daemon that
| we provide as a binary under the same license agreement as the
| microcode. We provide that binary pre-compiled as both a 32-bit and
| 64-bit application. The daemon utilizes a sysfs interface exposed by
| the driver in order to communicate with the hardware and configure the
| required regulatory parameters.
I fail to see how a binary-only daemon can be used to enforce
regulatory limits. What stops a user from running a daemon for
another country, enforcing different limits?
--
Dick Streefland //// Altium BV
dick.streefland@altium.nl (@ @) http://www.altium.com
--------------------------------oOO--(_)--OOo---------------------------
prev parent reply other threads:[~2006-02-27 14:27 UTC|newest]
Thread overview: 26+ 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 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 [this message]
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=698.44030c45.bc404@altium.nl \
--to=dick.streefland@altium.nl \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.