From: Ben Greear <greearb@candelatech.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k: Support 4.9Ghz channels on AR9580 adapter.
Date: Mon, 20 Jun 2016 13:41:09 -0700 [thread overview]
Message-ID: <576854E5.5030206@candelatech.com> (raw)
In-Reply-To: <300e3070916441609ff73ea8e06ddb77@euamsexm01a.eu.qualcomm.com>
On 06/20/2016 01:34 PM, Kalle Valo wrote:
> Ben Greear <greearb@candelatech.com> wrote:
>> From: Ben Greear <greearb@candelatech.com>
>>
>> NOTE: These channels must not be used in most regulatory
>> domains unless you have a license from the FCC or similar!
>>
>> A proper regulatory database is also required to actually use
>> these channels.
>>
>> Signed-off-by: Ben Greear <greearb@candelatech.com>
>
> I feel that the license is a problem and this doesn't belong to the kernel.
> The patch has been dropped.
It's not a lot different from having to be in normal FCC regulations w/regard to
DFS channels, tx power, and such, but maybe having driver support is considered to make it
too easy for users to hack around restrictions?
Another part of this is that Cisco APs, at least, use fractional center
frequencies (4942.5, for instance) when using 5Mhz bandwidths on 4.9Ghz
channels, and that requires more patches that I don't think I even bothered
to post.
I'll keep this in my trees, someone needing it can just clone it and/or borrow
patches as needed.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
WARNING: multiple messages have this Message-ID (diff)
From: Ben Greear <greearb@candelatech.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, ath9k-devel@lists.ath9k.org
Subject: Re: ath9k: Support 4.9Ghz channels on AR9580 adapter.
Date: Mon, 20 Jun 2016 13:41:09 -0700 [thread overview]
Message-ID: <576854E5.5030206@candelatech.com> (raw)
In-Reply-To: <300e3070916441609ff73ea8e06ddb77@euamsexm01a.eu.qualcomm.com>
On 06/20/2016 01:34 PM, Kalle Valo wrote:
> Ben Greear <greearb@candelatech.com> wrote:
>> From: Ben Greear <greearb@candelatech.com>
>>
>> NOTE: These channels must not be used in most regulatory
>> domains unless you have a license from the FCC or similar!
>>
>> A proper regulatory database is also required to actually use
>> these channels.
>>
>> Signed-off-by: Ben Greear <greearb@candelatech.com>
>
> I feel that the license is a problem and this doesn't belong to the kernel.
> The patch has been dropped.
It's not a lot different from having to be in normal FCC regulations w/regard to
DFS channels, tx power, and such, but maybe having driver support is considered to make it
too easy for users to hack around restrictions?
Another part of this is that Cisco APs, at least, use fractional center
frequencies (4942.5, for instance) when using 5Mhz bandwidths on 4.9Ghz
channels, and that requires more patches that I don't think I even bothered
to post.
I'll keep this in my trees, someone needing it can just clone it and/or borrow
patches as needed.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2016-06-20 20:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 22:40 [ath9k-devel] [PATCH] ath9k: Support 4.9Ghz channels on AR9580 adapter greearb at candelatech.com
2016-05-12 22:40 ` greearb
2016-06-20 20:34 ` [ath9k-devel] " Kalle Valo
2016-06-20 20:34 ` Kalle Valo
2016-06-20 20:41 ` Ben Greear [this message]
2016-06-20 20:41 ` Ben Greear
2016-06-20 23:53 ` [ath9k-devel] " Julian Calaby
2016-06-20 23:53 ` Julian Calaby
2016-06-21 0:00 ` [ath9k-devel] " Ben Greear
2016-06-21 0:00 ` Ben Greear
2016-06-21 1:02 ` [ath9k-devel] [PATCH] " Julian Calaby
2016-06-21 1:02 ` Julian Calaby
2016-06-21 9:41 ` [ath9k-devel] " Jouni Malinen
2016-06-21 9:41 ` Jouni Malinen
2016-06-21 10:16 ` [ath9k-devel] " Julian Calaby
2016-06-21 10:16 ` Julian Calaby
2016-06-21 14:17 ` [ath9k-devel] " Ben Greear
2016-06-21 14:17 ` Ben Greear
2016-06-21 14:25 ` [ath9k-devel] " Dave Taht
2016-06-21 14:25 ` Dave Taht
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=576854E5.5030206@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath9k-devel@lists.ath9k.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 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.