From: Johannes Berg <johannes@sipsolutions.net>
To: Michal Sojka <sojkam1@fel.cvut.cz>,
Jan Kaisrlik <kaisrja1@fel.cvut.cz>,
wireless-regdb@lists.infradead.org
Cc: 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 22:24:20 +0200 [thread overview]
Message-ID: <1445027060.2370.25.camel@sipsolutions.net> (raw)
In-Reply-To: <87h9lqeplf.fsf@steelpick.2x.cz>
Hi,
> I thought that the regdb is for unlicensed bands with unrestricted use.
> The 5.9 GHz band is not licensed but it is restricted for ITS
> applications.
It kind of is, at least the current one is.
> In http://marc.info/?l=linux-wireless&m=140183393707445&w=2
> Luis Rodriguez suggested that having a Kconfig option may be the way to
> go, but we may misread what he was saying.
I didn't really follow this.
> I assume that if this band will be in regdb, it will be too easy to use
> this band (e.g. by mistake) for non-ITS applications.
Does the *regulatory* actually prohibit that anyway though?
> Our goal is to make it easier for people to experiment with ITS in
> controlled environment (e.g. in a university lab). So you suggest that
> this should be enabled by providing custom regdb rather than recompiling
> the kernel with CFG80211_CERTIFICATION_ONUS?
Yes, that was exactly my thought.
johannes
next prev parent reply other threads:[~2015-10-16 20:24 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 ` [RFC PATCH 1/2] cfg80211: " Johannes Berg
2015-10-16 16:38 ` Michal Sojka
2015-10-16 20:24 ` Johannes Berg [this message]
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=1445027060.2370.25.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 \
--cc=wireless-regdb@lists.infradead.org \
/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