From: Johannes Berg <johannes@sipsolutions.net>
To: Jan Kaisrlik <kaisrja1@fel.cvut.cz>
Cc: sojkam1@fel.cvut.cz, linux-wireless@vger.kernel.org,
bernd.lehmann@volkswagen.de, jan-niklas.meier@volkswagen.de,
s.sander@nordsys.de
Subject: Re: [RFC PATCH 1/2] cfg80211: Add support for ITS-G5 band (5.9 GHz)
Date: Fri, 16 Oct 2015 14:06:37 +0200 [thread overview]
Message-ID: <1444997197.2370.22.camel@sipsolutions.net> (raw)
In-Reply-To: <1444994885-21825-1-git-send-email-kaisrja1@fel.cvut.cz> (sfid-20151016_132820_779190_3F5069D0)
On Fri, 2015-10-16 at 13:28 +0200, Jan Kaisrlik wrote:
> The patch adds support for Intelligent Transportation System (ITS-G5)
> band as defined by ETSI EN 302 663 standard. This band is enabled by
> a new configuration option CFG80211_REG_ITSG5_BAND, which depends on
> CFG80211_CERTIFICATION_ONUS.
That Kconfig option seems unnecessary - after all, the regulatory
database still has a say in this?
Even the NL80211_RRF_ITSG5 flag seems somewhat unnecessary - if the
regulatory database did in fact provide information on these channels,
then we can assume they're usable, no?
IOW - I don't really see the point of this patch - can't we treat these
channels just like regular ones, and rely on the regulatory information
to prevent their use in all but special scenarios (where the integrator
is providing a proper database)?
johannes
next prev parent reply other threads:[~2015-10-16 12:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 11:28 [RFC PATCH 1/2] cfg80211: Add support for ITS-G5 band (5.9 GHz) Jan Kaisrlik
2015-10-16 11:28 ` [RFC PATCH 2/2] ath9k: " Jan Kaisrlik
2015-10-16 12:06 ` Johannes Berg [this message]
2015-10-16 16:38 ` [RFC PATCH 1/2] cfg80211: " Michal Sojka
2015-10-16 20:24 ` Johannes Berg
2015-10-16 20:46 ` Michal Sojka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1444997197.2370.22.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=bernd.lehmann@volkswagen.de \
--cc=jan-niklas.meier@volkswagen.de \
--cc=kaisrja1@fel.cvut.cz \
--cc=linux-wireless@vger.kernel.org \
--cc=s.sander@nordsys.de \
--cc=sojkam1@fel.cvut.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox