From: Luis R. Rodriguez <lrodriguez@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Regulatory domains
Date: Wed, 23 Feb 2011 19:28:01 -0800 [thread overview]
Message-ID: <20110224022334.GI19293@tux> (raw)
In-Reply-To: <20110223204014.28607.qmail@stuge.se>
On Wed, Feb 23, 2011 at 12:40:14PM -0800, Peter Stuge wrote:
> Luis R. Rodriguez wrote:
> > Unfortunately due to regulatory considerations which have also come
> > under recent stress [4] we cannot feature-wise let users overwrite
> > their own EEPROM, even if they know better.
>
> I think this is good in the driver, but there was some discussion
> about writing to the EEPROM from outside the driver.
We cannot take that step for a while and specifically some countries
explicitly prohibit this.
> > This is simply the state of affairs today, but hopefully would
> > change.
>
> That external tool for changing EEPROM contents, or at least reg
> domain, would avoid punishing users,
No one is punishing users, at least intentionally, the design
philosophy assumes that when you get your 802.11 card it is
programmed correctly. This proves to be wrong at times, but
I'm just stating the facts and current industry and regulatory
assumptions.
> while work continues on changing
> state of affairs for the future.
If regulatory agencies would allow for such tools to be distributed
and pass liability down to the user if they do this, that likely
would make it possible to release this sort of code, but its not
the case today.
> > The way I see it, we should be dynamicaly figuring out our location
> > using GPS / other trusted feeds and propagate this to 802.11
> > devices
>
> If you exclude user input from that set of trusted feeds you just
> make yourself a lot of unfriends. :\
Regulatory agencies like the FCC have made it 100% clear that user input
cannot be supported as a feature for selecting your country, see:
http://wireless.kernel.org/en/developers/Regulatory/CRDA#Helping_compliance_by_allowing_to_change_regulatory_domains
> > you can .. verify the EEPROM contents of a card you purchase to
> > ensure it fits your own country.
>
> That's ridiculous.
Agreed but its what we have today. In the end I believe we stand to gain
if we were able to legally change dynamically the regulatory domain, I'd
prefer to leave the user out of this, the user does not need to be involved,
and we can use new techniques to figure with close 100% realiability your
location. I do believe this will help with communications but its just the
state where we are today.
Luis
next prev parent reply other threads:[~2011-02-24 3:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 14:20 [ath9k-devel] What would be the best chipset for wireless router/AP on linux? crocket
2011-02-23 16:19 ` Peter Stuge
2011-02-23 17:57 ` Luis R. Rodriguez
2011-02-23 20:40 ` [ath9k-devel] Regulatory domains Peter Stuge
2011-02-23 22:56 ` Adrian Chadd
2011-02-24 2:14 ` Luis R. Rodriguez
2011-02-24 2:24 ` Peter Stuge
2011-02-24 3:28 ` Luis R. Rodriguez [this message]
2011-02-24 3:49 ` Peter Stuge
2011-02-24 7:54 ` [ath9k-devel] What would be the best chipset for wireless router/AP on linux? crocket
2011-02-24 8:08 ` Luis R. Rodriguez
2011-02-24 8:20 ` Peter Stuge
2011-02-24 8:27 ` Luis R. Rodriguez
2011-02-24 8:48 ` Peter Stuge
2011-02-24 16:12 ` Luis R. Rodriguez
2011-02-24 15:28 ` David Willmore
2011-02-24 16:26 ` Luis R. Rodriguez
2011-02-24 17:12 ` David Willmore
2011-02-24 9:30 ` crocket
2011-02-24 9:36 ` Peter Stuge
2011-02-24 15:21 ` Petr Štetiar
2011-02-24 15:47 ` David Willmore
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=20110224022334.GI19293@tux \
--to=lrodriguez@atheros.com \
--cc=ath9k-devel@lists.ath9k.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.