On Mon, Mar 29, 2010 at 12:15 PM, Krzysztof Halasa <khc@xxxxxxxxx> wrote: > "Luis R. Rodriguez" <mcgrof@xxxxxxxxx> writes: > >> I've documented this specific case here: >> >> http://wireless.kernel.org/en/users/Drivers/ath/#The_0x0_regulatory_domain > > Thanks. > > I'm not sure how the modified regulatory.bin could work, though: > I really don't want to use restricted frequencies etc. when the > regulatory domain is set to US (i.e. when operating in USA), I only want > to use the extra channels etc. when in e.g. Europe. I agree with that wishful thinking, however current legislation does now allow for dynamic enabling of frequencies on devices certified under part 15 rules. We can likely work towards changing the legislation for this but that's something I haven't seen many companies willing to lobby for. We'd need a big company to help with this lobby. > IOW I should be able > to iw reg set US and get the US freqs only. > > A driver modification to ignore the default restrictions (while obeying > the regulatory.bin, on a 0-country cards only, of course) - that would > work. And it would also make our drivers break regulatory rules. We're not going to do that on Linux because proving that we can be responsible is in fact what does allow us to get proper vendor support for 802.11 drivers. See: http://wireless.kernel.org/en/developers/Regulatory/statement Luis -- 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
