Historical ath9k-devel archives
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH] ath9k: Support 4.9Ghz channels on AR9580 adapter.
Date: Tue, 21 Jun 2016 07:25:22 -0700	[thread overview]
Message-ID: <CAA93jw4YEEBw+2kd+0MB1R-YHHCeyLRDNZoPVtNrovJG1wy8TA@mail.gmail.com> (raw)
In-Reply-To: <20160621094146.GA3196@w1.fi>

On Tue, Jun 21, 2016 at 2:41 AM, Jouni Malinen <j@w1.fi> wrote:
> On Tue, Jun 21, 2016 at 11:02:20AM +1000, Julian Calaby wrote:
>> I've only done this work as I hate to see people's efforts go to
>> waste and I feel that there's enough roadblocks in the way of
>> actually using this functionality that casual idiots won't be able
>> to.
>
> Are these really ready to go to the upstream kernel in this state and
> without the other changes that would be needed to operate correctly?
> What is the use case for these and how have these been tested?

So far as I know the use case for these is to make it possible to build
open source wifi systems that enable emergency services. This
strikes me as a worthy goal.

      parent reply	other threads:[~2016-06-21 14:25 UTC|newest]

Thread overview: 10+ 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-06-20 20:34 ` [ath9k-devel] " Kalle Valo
2016-06-20 20:41   ` Ben Greear
2016-06-20 23:53     ` Julian Calaby
2016-06-21  0:00       ` Ben Greear
2016-06-21  1:02       ` [ath9k-devel] [PATCH] " Julian Calaby
2016-06-21  9:41         ` Jouni Malinen
2016-06-21 10:16           ` Julian Calaby
2016-06-21 14:17           ` Ben Greear
2016-06-21 14:25           ` Dave Taht [this message]

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=CAA93jw4YEEBw+2kd+0MB1R-YHHCeyLRDNZoPVtNrovJG1wy8TA@mail.gmail.com \
    --to=dave.taht@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).