Search Linux Wireless

AW: Drivers that do not honor regulatory restrictions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Johannes Berg wrote: 
> No, that would've been the driver, the firmware has nothing to do with 
> the radio frequency at all. 
>  
> johannes 
 
Actually it was mac80211. In ieee80211_ioctl.c the allowed frequencies for Japan are defined this way: 
 
1574 static const struct ieee80211_channel_range ieee80211_mkk_channels[] = { 
 1575         { 2412, 2472, 20, 6 } /* IEEE 802.11b/g, channels 1..13 */, 
 1576         { 5170, 5240, 20, 6 } /* IEEE 802.11a, channels 34..48 */, 
 1577         { 5260, 5320, 20, 6 } /* IEEE 802.11a, channels 52..64 */, 
 1578         { 0 } 
 1579 }; 

This prevents channel 14 from being used. Changing line 1575 to 
 
1575         { 2412, 2484, 20, 6 } /* IEEE 802.11b/g, channels 1..13 */, 

did the trick.

BTW: ieee80211_ioctl_set_regulatory_domain changes conf->regulatory_domain, but this seems not to change the selected frequency table (that one is selected solely based on the module parameter "ieee80211_regdom". Why are there two places to store the regdomain (that seem to be used from different places)?
 
--   
Regards 
  
       Joerg 
 
 
 




       __________________________________ Yahoo! Clever - Der einfachste Weg, Fragen zu stellen und Wissenswertes mit Anderen zu teilen. www.yahoo.de/clever

-
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux