From: "John W. Linville" <linville@tuxdriver.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Johan Adolfsson <Johan.Adolfsson@axis.com>,
linux-wireless@vger.kernel.org,
"'Dan Williams'" <dcbw@redhat.com>
Subject: Re: [PATCH] Add module parameter to override regioncode on libertas
Date: Mon, 30 Jun 2008 13:29:08 -0400 [thread overview]
Message-ID: <20080630172908.GA8391@tuxdriver.com> (raw)
In-Reply-To: <20080630154425.GB22984@khazad-dum.debian.net>
On Mon, Jun 30, 2008 at 12:44:26PM -0300, Henrique de Moraes Holschuh wrote:
> Now I get my trusty laptop with the EEPROM-based regdomain driver, and
> travel to somewhere where the channel overlap with the Americas regdomain
> the vendor used is such that the card can actually operate outside of the
> requirements for the local government. If I am lucky, it just won't allow
> me to talk to everyone like what happens in Brazil. If I am not, I could be
> breaking the law.
>
> Where, in the entire scenario above, was the regulatory information in the
> EEPROM useful to me? NEVER. It was a hindrance in every step.
Hardware vendor representatives insist that regulaions should be
enforced as the product of both where you are (or claim to be) _and_
where the device was certified to operate when it was produced. I have
no specific examples to cite of what might happen if e.g. a USA device
is operated on channel 13, but the hardware vendors insist that this
should not be allowed to happen. "It works for me" anecdotes aside,
it seems like a bad idea to encourage (or fail to discourage) users
to override certified hardware regulatory settings.
If this is the only way to influence the regulatory enforcement
then your 2nd example is a valid. But in that case moving to a
cfg80211-based regulatory enforcement seems like a better way to go.
John
--
John W. Linville
linville@tuxdriver.com
prev parent reply other threads:[~2008-06-30 17:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1214580776.10355.16.camel@localhost.localdomain>
2008-06-30 6:36 ` [PATCH] Add module parameter to override regioncode on libertas Johan Adolfsson
2008-06-30 11:05 ` Johannes Berg
2008-06-30 11:58 ` Johan Adolfsson
2008-06-30 14:03 ` John W. Linville
2008-06-30 15:44 ` Henrique de Moraes Holschuh
2008-06-30 17:29 ` John W. Linville [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=20080630172908.GA8391@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=Johan.Adolfsson@axis.com \
--cc=dcbw@redhat.com \
--cc=hmh@hmh.eng.br \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).