On 15.12.2009 20:00 you wrote: > Does setting the coverage class make sense for all modes of operation? > If not it'd be good to catch those early and avoid setting them and also > properly document them. The coverage class is a physical device parameter, not interface parameter, so it's independent on whether the interface is AP or STA, there could even be multiple interfaces on one physical device. It's the same as RTS threshold, for example. And it has to be a physical device parameter, because in the end it just sets some hardware registers.
> The AP seems to pass the coverage class on country IE, so I guess > this means we can support this for AP mode and IBSS and only through the > country IE for STA. Mind you that would mean hostapd would need to kick > the coverage class as well and some new code on cfg80211 reg.c > country_ie_2_rd() to parse it. This part is not implemented yet, I wanted to do the low level setting first, as the regulatory stuff is quite complex. It's still usable for long distance point-to-point links (that are now impossible with in-kernel drivers). Hostapd would then use the same API. Lukas Turek
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
