On Fri, Jul 31, 2009 at 12:45 AM, Johannes Berg<johannes@xxxxxxxxxxxxxxxx> wrote: > On Thu, 2009-07-30 at 17:43 -0700, Luis R. Rodriguez wrote: > >> By doing so though we also disallowed beacon hints on devices >> registering their wiphy with custom world regulatory domains >> enabled, this happens to be currently ath5k, ath9k and ar9170. >> The passive scan and beacon restrictions on those devices would >> never be lifted even if we did find a beacon and the hardware did >> support such enhancements when world roaming. > > I dislike this solution, it just adds proliferation of possible > behaviours. Agreed. > Can't those devices Which devices? > just set the _flags_ in their reg > notifier, So if you mean devices that used custom reg stuff, the answer is no because the patch which introduced the regression would prevent the setting of the passive scan flag and beaconing restrictions so the reg_notifier would never notice the difference. If you mean iwlwifi devices then yes, this is possible but it also means a big change and I'd like to see this regression fixed on 2.6.31. > and clear the corresponding bit in the orig_flags? iwlwifi would just have to touch flags, not orig_flags as orig_flags should not be touched. How about using the patch as is for now for wireless-testing and 2.6.31, and then have iwlwifi write their own reg_notifier() ? 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
