On 06/15/2012 10:21 AM, Kalle Valo wrote: > On 06/15/2012 11:16 AM, Johannes Berg wrote: >>> As for a name, I thought about it for a while and given that we have different >>>> "wireless" technologies -- bluetooth, NFC, naming this CONFIG_WIRELESS_EXPERT >>>> seemed odd, and given that our 802.11 framework is under cfg80211 naming it >>>> CONFIG_CFG80211_EXPERT seemed appropriate. But even if its under cfg80211 >>>> perhaps something more explicit about the implications may be better, how >>>> about CONFIG_CFG80211_MAY_BREAK_CERTIFICATION ? >> >> Or you could just be explicit about it and call it >> CONFIG_WIRELESS_REGULATORY_BREAKAGE or something like that :-) > > CONFIG_WIRELESS_CERTIFIED? > > Kalle > Kalle, That one looks familiar ;-) Although that name makes sense for a feature like DFS, I think the intended use is also to hide features from unaware users that will definitely violate with regulatory requirements. Luis, Is this flag purely intended for 802.11 device drivers or can it also be used to hide certain features in stack (ie. cfg80211 or mac80211). If it is only for device drivers I would suggest to have it depend on CONFIG_WLAN. Suggestion for the config option: CONFIG_WLAN_CERTIFIED_OR_SCIENTIFIC_USE Gr. AvS -- 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
