All of lore.kernel.org
 help / color / mirror / Atom feed
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 17:00:13 -0700	[thread overview]
Message-ID: <5768838D.8000201@candelatech.com> (raw)
In-Reply-To: <CAGRGNgWOScCrLPyqRNus2319BPOehv3awQChoHw=RRMcSDUqzQ@mail.gmail.com>

On 06/20/2016 04:53 PM, Julian Calaby wrote:
> Hi Ben,
>
> On Tue, Jun 21, 2016 at 6:41 AM, Ben Greear <greearb@candelatech.com> wrote:
>> 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?
>
> Maybe hide this behind CFG80211_CERTIFICATION_ONUS or equivalent?
> (Maybe a new symbol CFG80211_LICENSE_REQUIRED with big scary
> feds-will-come-knocking warnings in the help text?)

That would be fine with me.  As I said though, there are more patches
than this one needed for full features and interoperability.
The person that sent me the mac80211/wireless patches,
and hostapd for that matter, may be able to put something together for upstream,
but I am not sure if they will have time.

I don't currently feel motivated enough to try to clean it all up and
try to push it upstream myself.

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: Julian Calaby <julian.calaby@gmail.com>
Cc: Kalle Valo <kvalo@qca.qualcomm.com>,
	linux-wireless <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 17:00:13 -0700	[thread overview]
Message-ID: <5768838D.8000201@candelatech.com> (raw)
In-Reply-To: <CAGRGNgWOScCrLPyqRNus2319BPOehv3awQChoHw=RRMcSDUqzQ@mail.gmail.com>

On 06/20/2016 04:53 PM, Julian Calaby wrote:
> Hi Ben,
>
> On Tue, Jun 21, 2016 at 6:41 AM, Ben Greear <greearb@candelatech.com> wrote:
>> 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?
>
> Maybe hide this behind CFG80211_CERTIFICATION_ONUS or equivalent?
> (Maybe a new symbol CFG80211_LICENSE_REQUIRED with big scary
> feds-will-come-knocking warnings in the help text?)

That would be fine with me.  As I said though, there are more patches
than this one needed for full features and interoperability.
The person that sent me the mac80211/wireless patches,
and hostapd for that matter, may be able to put something together for upstream,
but I am not sure if they will have time.

I don't currently feel motivated enough to try to clean it all up and
try to push it upstream myself.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  reply	other threads:[~2016-06-21  0:00 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   ` [ath9k-devel] " Ben Greear
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       ` Ben Greear [this message]
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=5768838D.8000201@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.