On Thu, Mar 4, 2010 at 2:24 AM, Daniel Halperin <dhalperi@xxxxxxxxxxxxxxxxx> wrote: > On Mar 3, 2010, at 2:54 PM, Daniel Halperin wrote: > My hypothesis as to why this code used to work is that I was using the CONFIG_WIRELESS_OLD_REGULATORY. Can you test the same by disabling CONFIG_WIRELESS_OLD_REGULATORY ? There is a way for a driver to claim a custom world regulatory domain, this can be done wiphy_apply_custom_regulatory(), ath/regd.c uses that. Otherwise indeed the pegged regulatory domain will be used as a basis for disabling further channels. 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
