lkml.org 
[lkml]   [2009]   [Aug]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: ath5k - strange regulatory domain change
Date
On Friday 07 August 2009, you wrote:
> The way the EEPROM was programmed for this type of
> regulatory domain was to give you a group number under which other
> countries fall under. If you ended up getting a direct alpha2
> programmed in the EEPROM instead you would still end up matching the
> alpha2 to a group number. The group number leads you to a regulatory
> domain that all those countries in that group number adhere to. So it
> was a way to group up regulatory domain rules between countries. The
> "CN" you see just so happens to be the alpha2 for the first country in
> the same group regulatory domain group.
>
> What we can do is to elaborate on that on the dmesg and also maybe

That would be very welcome.

> pick the most common country on the group so it will tend to match the
> country users are on.

I think that would just be moving the problem from one group of users to
another, possibly only marginally smaller, group of users.

As far as I can see the largest group is ETSI1_WORLD and contains 33
countries, followed by NULL1_WORLD (is that a real group?) with 22.
That's probably too many to list them all.
OTOH, all other groups contain at most 7 countries, which could possibly
be listed.

Probably the simplest option would be to just display some identification
of the domain group itself and point users to documentation which
explains what countries fall under what groups. That would at least avoid
the confusion caused by randomly picking a matching country.
Variation could be to display the country if the group only contains one
country, but that could also be considered an inconsistent user
interface.

Cheers,
FJP


\
 
 \ /
  Last update: 2009-08-07 19:43    [W:0.046 / U:0.124 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site