[ath9k-devel] Country code setting issue

[Alexander Simon <simon_alex@web.de>]

Am Mittwoch, 8. Dezember 2010, 19:06:40 schrieben Sie:
> That's beyond the scope of what code can do, but current legislations
> forces us to respect this and not allow users to say they know better.
> This can be corrected once legislations allows us to shift liability
> down to the user if the user chooses to indicate they know better and
> they are wrong.
Isn't that already the case? I mean it's open source. Anyone could see that 
the user would have overwritten a eeprom setting.
Additionally there are Windows drivers that allow some user to enable eg 
channel 12 and 13.  Madwifi had an modoption for that.

> No, 00 on Atheros cards which are built for STAs means US by design:
As i understand regd.c, there is no check if the card is driven as a AP.
I have a SR71-A which i would say is an industrial card, not only STA...

> No, by design 00 on Atheros cards is the US for cards shipped on
> client cards. And without knowing what country you are in cfg80211
> defaults to the world regulatory domain which is the intersection of
> all regulatory domains.
I didn't find this piece of code in madwifi?!?? So it does not seem to be 
"standard".

> Maybe I'll change the print message to make it clearer to you that
> this is by design and not a programmer's choice.
Well, I understand the problem and also did before.
Of course, the problem is caused by Atheros (or card suppliers) and their 
wrong EEPROMs, but personally I don't think they will fix it.

So the problem remains: As Long as there is no card with a proper EEPROM, all 
this doesn't make any sense.
This piece of code is responsible that no european user can use channel 12&13.
But all these card operate at 27dBm on 2.4GHz which is NOT covered by any 
european legislation.
So, by allowing the user setting the CC, you couldn't make it worse.