Re: [arch-general] [arch-dev-public] RFC: crda PKBUILD
Thomas B,bd(Bchler wrote:
Aaron Griffin schrieb:
Couldn't we set it as a dep of the wireless tools? That seems like it would install for the right people then. Considering you want to shut things off in the kernel, this will make some (most? no idea) wireless non-functional without this, right? It seems an optdepend of kernel26 would be easy to miss
To set a new regulatory domain, 'iw' is required. 'iw' should be added to core too.
I think I remember that the wireless stack will fall back to a default (minimal) set of channels if crda is missing (which is not too different from the current behaviour).
That's right, WORLD regulatory domain would be chosen if CRDA is missing. But it has a limited set of channels than what people were using so far, so expect a rash of 'wireless not working' bugs. :) The best method to accommodate the new regulatory infrastructure would be to set the country code on bootup, with the user's choice stored in /etc/rc.conf. Sujith -- http://sujith-m.blogspot.com
Sujith schrieb:
I think I remember that the wireless stack will fall back to a default (minimal) set of channels if crda is missing (which is not too different from the current behaviour).
That's right, WORLD regulatory domain would be chosen if CRDA is missing. But it has a limited set of channels than what people were using so far, so expect a rash of 'wireless not working' bugs. :)
I think you could still set the domain via a cfg80211 module option or it would be determined automatically by some country code set in the EEPROM if possible. There's not too much documentation about this ...
Thomas B,bd(Bchler wrote:
Sujith schrieb:
I think I remember that the wireless stack will fall back to a default (minimal) set of channels if crda is missing (which is not too different from the current behaviour).
That's right, WORLD regulatory domain would be chosen if CRDA is missing. But it has a limited set of channels than what people were using so far, so expect a rash of 'wireless not working' bugs. :)
I think you could still set the domain via a cfg80211 module option or it would be determined automatically by some country code set in the EEPROM if possible. There's not too much documentation about this ...
Nope, no cfg80211 module option exists to choose the country code. But you are correct, drivers _can_ hint CRDA of the country code programmed in the EEPROM, but not all drivers have been converted to make use of this feature. Another way to choose a regulatory domain is to just enforce what the AP advertises (802.11d). This page pretty much covers all of this: http://wireless.kernel.org/en/developers/Regulatory#Theregulatorydatabase I have CC'd the main developer behind CRDA, he can probably advise on the best way a distribution can incorporate all this. Sujith -- http://sujith-m.blogspot.com
Sujith schrieb:
Nope, no cfg80211 module option exists to choose the country code.
There's a difference?
But you are correct, drivers _can_ hint CRDA of the country code programmed in the EEPROM, but not all drivers have been converted to make use of this feature.
Intel does it afaik. Anyway, Intel's cards are limited by their ucode anyway.
Another way to choose a regulatory domain is to just enforce what the AP advertises (802.11d).
Which is not implemented yet, or is it?
This page pretty much covers all of this: http://wireless.kernel.org/en/developers/Regulatory#Theregulatorydatabase
I didn't know this link, thank you.
participants (2)
-
Sujith
-
Thomas Bächler