On Mon, Nov 02, 2015 at 07:38:57PM +0100, Michal Sojka wrote: > We discussed that about a year ago [1]. The thing is that regulatory > documents do not talk about modes (at least in Europe). They only talk > about channel widths, EIRP etc. and say that the band is designated for > Intelligent Transportation System (ITS) applications. Only the ITS > standards (e.g. ETSI EN 302 663) talk about OCB mode. From the last > year's discussion I took away that we should not restrict these bands to > OCB only, because regulatory documents do not require it. But I might > get it wrong. > > [1] http://www.mail-archive.com/linux-kernel at vger.kernel.org/msg656581.html In some sense, I agree with that, but taken into account that I'm much more concerned about accidentally using this band, I think there is justification for adding that extra constraint of allowing only the OCB mode to be used even if the regulatory requirements may not explicitly say so. Especially the behavior of including these channels with active scanning allowed in all full scans is something that really must not be enabled. > Hmm, ath9k is the hardware that we can currently play with. Can you > suggest another hardware that supports 5.9 GHz and a driver that would > be more convenient to develop with? I don't think there is any hardware alternative that would be more convenient for this type of efforts than chips supported by ath9k. It is just that the needs of this project are somewhat in conflict with the needs of regulatory rule enforcement for most other use cases.. :) -- Jouni Malinen PGP id EFC895FA
