| Message ID | 1448303241-27747-8-git-send-email-sojkam1@fel.cvut.cz (mailing list archive) |
|---|---|
| State | Changes Requested |
| Delegated to: | Johannes Berg |
| Headers | show |
On Mon, 2015-11-23 at 19:27 +0100, Michal Sojka wrote: > This option is meant for use by drivers and other subsystems to > enable > support for the Intelligent Transportation System (ITS-G5) band. The > option depends on CFG80211_CERTIFICATION_ONUS as the use of this band > is > restricted. EU allows using it only for certain applications, USA > require certification. Hm. Why do we need this now? I see that you're checking it in ath9k, to enable the "ITSG5" channels, but why wouldn't you always do that, now that you have the extra checks with the user regdb being required and all? johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, Nov 26 2015, Johannes Berg wrote: > On Mon, 2015-11-23 at 19:27 +0100, Michal Sojka wrote: >> This option is meant for use by drivers and other subsystems to >> enable >> support for the Intelligent Transportation System (ITS-G5) band. The >> option depends on CFG80211_CERTIFICATION_ONUS as the use of this band >> is >> restricted. EU allows using it only for certain applications, USA >> require certification. > > Hm. Why do we need this now? I see that you're checking it in ath9k, to > enable the "ITSG5" channels, but why wouldn't you always do that, now > that you have the extra checks with the user regdb being required and > all? Because in [1] Jouni said that "kernel config option + custom regdb would certainly be much closer to what I'd like to see from the regulatory enforcement view point" I also like the fact that the help text mentions the relevant regulatory documents. I guess the users would appreciate that. -Michal [1] http://www.mail-archive.com/ath9k-devel@lists.ath9k.org/msg13795.html -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, 2015-11-26 at 22:10 +0100, Michal Sojka wrote: > > Because in [1] Jouni said that > > "kernel config option + custom regdb would certainly be much > closer to what I'd like to see from the regulatory enforcement view > point" > > I also like the fact that the help text mentions the relevant > regulatory documents. I guess the users would appreciate that. > Fair enough, but I'm not really convinced that the Kconfig option is needed for what Jouni really required. In any case, I spoke with him yesterday and we don't think that your patches are going to work as is - we'll need to change the regulatory flags it seems. I'll comment more specifically on the patches. johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Fri, Nov 27 2015, Johannes Berg wrote: > On Thu, 2015-11-26 at 22:10 +0100, Michal Sojka wrote: >> >> Because in [1] Jouni said that >> >> "kernel config option + custom regdb would certainly be much >> closer to what I'd like to see from the regulatory enforcement view >> point" >> >> I also like the fact that the help text mentions the relevant >> regulatory documents. I guess the users would appreciate that. >> > > Fair enough, but I'm not really convinced that the Kconfig option is > needed for what Jouni really required. > > In any case, I spoke with him yesterday and we don't think that your > patches are going to work as is - we'll need to change the regulatory > flags it seems. I'll comment more specifically on the patches. OK. I'll wait for that. -Michal -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/net/wireless/Kconfig b/net/wireless/Kconfig index da72ed3..faa0ab1 100644 --- a/net/wireless/Kconfig +++ b/net/wireless/Kconfig @@ -132,6 +132,33 @@ config CFG80211_REG_RELAX_NO_IR support this feature by declaring the appropriate channel flags and capabilities in their registration flow. +config CFG80211_REG_ITSG5_BAND + bool "cfg80211 support for ITS-G5 band (5.9 GHz)" + def_bool n + depends on CFG80211_CERTIFICATION_ONUS + ---help--- + This option enables support for Inteligent Transportation System (ITS) + band i.e. frequencies from 5.850 to 5.925 GHz. In Europe, the band is + standardized in the ETSI EN 302 663 standard. The use of this band is + restricted by regulatory documents mentioned below. Enable this option + only if you comply with them. + + In Europe, the band is split into several sub-bands regulated by + separate documents: + + - ITS-G5A (5.875 to 5.905 GHz) band is reserved for ITS road safety + related applications and is regulated by Commission Decision + 2008/671/EC. + + - ITS-G5B (5.855 to 5.875 GHz) band is reserved for ITS non-safety + applications and is regulated by ECC Recommendation ECC/REC/(08)01. + + - ITS-G5D (5.905 to 5.925 GHz) band is reserved for future ITS + applications and is regulated by ECC Decision ECC/DEC(02)01. + + In the US, the band is regulated by FCC 03-324 and the devices using it + must be certified. + config CFG80211_DEFAULT_PS bool "enable powersave by default" depends on CFG80211
This option is meant for use by drivers and other subsystems to enable support for the Intelligent Transportation System (ITS-G5) band. The option depends on CFG80211_CERTIFICATION_ONUS as the use of this band is restricted. EU allows using it only for certain applications, USA require certification. Signed-off-by: Michal Sojka <sojkam1@fel.cvut.cz> --- net/wireless/Kconfig | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+)