From: Simon Wunderlich <sw@simonwunderlich.de>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: ath10k@lists.infradead.org, ath9k-devel@qca.qualcomm.com,
linux-wireless@vger.kernel.org,
Mathias Kretschmer <mathias.kretschmer@fit.fraunhofer.de>,
Ben Greear <greearb@candelatech.com>,
Julian Calaby <julian.calaby@gmail.com>
Subject: Re: [v2,1/3] ath9k: Support channels in licensed bands
Date: Tue, 18 Apr 2017 16:50:52 +0200 [thread overview]
Message-ID: <3170657.DNPqgEf8fi@prime> (raw)
In-Reply-To: <20170418143654.8AC0A60FAA@smtp.codeaurora.org>
[-- Attachment #1: Type: text/plain, Size: 2496 bytes --]
Hi,
On Tuesday, April 18, 2017 2:36:54 PM CEST Kalle Valo wrote:
> Simon Wunderlich <sw@simonwunderlich.de> wrote:
> > From: Ben Greear <greearb@candelatech.com>
> >
> > Many chips support channels in licensed bands. Add support for those,
> > along with a corresponding kernel config option to disable them by
> > default. Note that these channels are not selectable even if the
> > option has been compiled unless the user modifies the regulatory
> > database to explicitly enable the corresponding channels.
> >
> > NOTE: These channels must not be used in most regulatory
> > domains unless you have a license from the FCC or similar!
> >
> > Signed-off-by: Ben Greear <greearb@candelatech.com>
> > [Hide this support behind a Kconfig option]
> > Signed-off-by: Julian Calaby <julian.calaby@gmail.com>
> > [only use the 20 mhz channels, add 5 ghz, change to 4.9ghz to licensed
> > bands, simplify] Signed-off-by: Simon Wunderlich <sw@simonwunderlich.de>
> > Signed-off-by: Mathias Kretschmer <mathias.kretschmer@fit.fraunhofer.de>
>
> I am not sure that we should support unlicensed bands in Linux and hence
> hesitant to apply these. My view is that due to regulatory restrictions we
> should not make it too easy to use unlicensed bands. But I'm open for
> discussion, this is a challenging area and my knowledge here is limited.
thanks for your reply! I agree that we should not make it too easy, and
therefore there are the following "obstacles" which should avoid accidental
use of license bands:
* we have the kernel CONFIG option which features a big fat warning
* regulatory database must be tampered with to enabel the channels. In
distributions, the regdb also gets signed. There is also the "internal regdb"
CONFIG option if you compile your own kernel (rarely used, except for
OpenWRT). In each case, a user must actively add the 4.9 GHz channels into it,
because they are not included in the default regdb (and this should not
change).
* CFG80211_CERTIFICATION_ONUS is also required, which also says "you are on
your own".
I had a comparison with ath5k, which also allows using those channels without
at least the special configuration option (there is one enabling even more
channels). The regdb "obstacle" is in place as well. However, ath5k is for
very old chips and therefore the threat is limited.
In my personal view, we have quite a few obstacles which I consider "enough",
but would be interesting to hear others opinions ...
Cheers,
Simon
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Simon Wunderlich <sw@simonwunderlich.de>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: Julian Calaby <julian.calaby@gmail.com>,
linux-wireless@vger.kernel.org, ath9k-devel@qca.qualcomm.com,
ath10k@lists.infradead.org, Ben Greear <greearb@candelatech.com>,
Mathias Kretschmer <mathias.kretschmer@fit.fraunhofer.de>
Subject: Re: [v2,1/3] ath9k: Support channels in licensed bands
Date: Tue, 18 Apr 2017 16:50:52 +0200 [thread overview]
Message-ID: <3170657.DNPqgEf8fi@prime> (raw)
In-Reply-To: <20170418143654.8AC0A60FAA@smtp.codeaurora.org>
[-- Attachment #1.1: Type: text/plain, Size: 2496 bytes --]
Hi,
On Tuesday, April 18, 2017 2:36:54 PM CEST Kalle Valo wrote:
> Simon Wunderlich <sw@simonwunderlich.de> wrote:
> > From: Ben Greear <greearb@candelatech.com>
> >
> > Many chips support channels in licensed bands. Add support for those,
> > along with a corresponding kernel config option to disable them by
> > default. Note that these channels are not selectable even if the
> > option has been compiled unless the user modifies the regulatory
> > database to explicitly enable the corresponding channels.
> >
> > NOTE: These channels must not be used in most regulatory
> > domains unless you have a license from the FCC or similar!
> >
> > Signed-off-by: Ben Greear <greearb@candelatech.com>
> > [Hide this support behind a Kconfig option]
> > Signed-off-by: Julian Calaby <julian.calaby@gmail.com>
> > [only use the 20 mhz channels, add 5 ghz, change to 4.9ghz to licensed
> > bands, simplify] Signed-off-by: Simon Wunderlich <sw@simonwunderlich.de>
> > Signed-off-by: Mathias Kretschmer <mathias.kretschmer@fit.fraunhofer.de>
>
> I am not sure that we should support unlicensed bands in Linux and hence
> hesitant to apply these. My view is that due to regulatory restrictions we
> should not make it too easy to use unlicensed bands. But I'm open for
> discussion, this is a challenging area and my knowledge here is limited.
thanks for your reply! I agree that we should not make it too easy, and
therefore there are the following "obstacles" which should avoid accidental
use of license bands:
* we have the kernel CONFIG option which features a big fat warning
* regulatory database must be tampered with to enabel the channels. In
distributions, the regdb also gets signed. There is also the "internal regdb"
CONFIG option if you compile your own kernel (rarely used, except for
OpenWRT). In each case, a user must actively add the 4.9 GHz channels into it,
because they are not included in the default regdb (and this should not
change).
* CFG80211_CERTIFICATION_ONUS is also required, which also says "you are on
your own".
I had a comparison with ath5k, which also allows using those channels without
at least the special configuration option (there is one enabling even more
channels). The regdb "obstacle" is in place as well. However, ath5k is for
very old chips and therefore the threat is limited.
In my personal view, we have quite a few obstacles which I consider "enough",
but would be interesting to hear others opinions ...
Cheers,
Simon
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 146 bytes --]
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-04-18 14:50 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 13:30 [PATCH v2 0/3] Channels in licensed bands, noise floor override Simon Wunderlich
2017-03-23 13:30 ` Simon Wunderlich
2017-03-23 13:30 ` [PATCH v2 1/3] ath9k: Support channels in licensed bands Simon Wunderlich
2017-03-23 13:30 ` Simon Wunderlich
2017-04-18 14:36 ` [v2,1/3] " Kalle Valo
2017-04-18 14:36 ` Kalle Valo
[not found] ` <20170418143654.8AC0A60FAA@smtp.codeaurora.org>
2017-04-18 14:50 ` Simon Wunderlich [this message]
2017-04-18 14:50 ` Simon Wunderlich
2017-04-18 16:38 ` Steve deRosier
2017-04-18 16:38 ` Steve deRosier
[not found] ` <CALLGbRK2d1wZpfLnXu_UDWxVPA9LvejFyEFpzMub56uLH0+DTw@mail.gmail.com>
2017-04-18 17:09 ` Ben Greear
2017-04-18 17:09 ` Ben Greear
2017-04-21 11:29 ` Simon Wunderlich
2017-04-21 11:29 ` Simon Wunderlich
2017-04-21 12:40 ` Mathias Kretschmer
2017-04-21 12:40 ` Mathias Kretschmer
2017-05-09 12:57 ` Simon Wunderlich
2017-05-09 12:57 ` Simon Wunderlich
2017-05-09 17:50 ` Adrian Chadd
2017-05-09 17:50 ` Adrian Chadd
[not found] ` <CAKR_QV+0cPXbiScO3cS52R97o=wGh4+zgmqaRM7QbotmEJD51Q@mail.gmail.com>
2017-05-10 16:17 ` Ben Greear
2017-05-10 16:17 ` Ben Greear
2017-05-11 11:38 ` Kalle Valo
2017-05-11 11:38 ` Kalle Valo
2017-05-12 14:12 ` Ben Greear
2017-05-12 14:12 ` Ben Greear
2017-05-12 19:21 ` Steve deRosier
2017-05-12 19:21 ` Steve deRosier
2017-05-12 19:44 ` Ben Greear
2017-05-12 19:44 ` Ben Greear
2017-05-13 12:12 ` Arend Van Spriel
2017-05-13 12:12 ` Arend Van Spriel
2017-03-23 13:30 ` [PATCH v2 2/3] ath10k: add support for " Simon Wunderlich
2017-03-23 13:30 ` Simon Wunderlich
2017-03-23 13:30 ` [PATCH v2 3/3] ath9k: add noise floor override option Simon Wunderlich
2017-03-23 13:30 ` Simon Wunderlich
2017-04-19 14:08 ` [v2,3/3] " Kalle Valo
2017-04-19 14:08 ` Kalle Valo
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=3170657.DNPqgEf8fi@prime \
--to=sw@simonwunderlich.de \
--cc=ath10k@lists.infradead.org \
--cc=ath9k-devel@qca.qualcomm.com \
--cc=greearb@candelatech.com \
--cc=julian.calaby@gmail.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mathias.kretschmer@fit.fraunhofer.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.