linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jouni Malinen <j@w1.fi>
To: Arend van Spriel <arend@broadcom.com>
Cc: "hostap@lists.shmoo.com" <hostap@lists.shmoo.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Kalle Valo <kvalo@codeaurora.org>
Subject: Re: hostapd and 11h support
Date: Wed, 24 Dec 2014 21:04:52 +0200	[thread overview]
Message-ID: <20141224190452.GA6933@w1.fi> (raw)
In-Reply-To: <549B05F0.9020704@broadcom.com>

On Wed, Dec 24, 2014 at 07:29:04PM +0100, Arend van Spriel wrote:
> The firmware on the device *can* have CAC logic built-in. When it
> *is* built-in it is however disabled by default. Based on your
> feedback I will just detect firmware support, enable dfs in
> firmware, and signal DFS offload to hostapd. I would suggest
> introducing a new common capability flag for this instead of using a
> QCA vendor specific one. That would be odd ;-)

I see nothing odd in other drivers using the already defined QCA vendor
specific nl80211 command. Anyway, I have no issues with a new nl80211
capability flag added for this purpose. You'll probably have better
chances of getting that accepted with an upstream driver using it.

-- 
Jouni Malinen                                            PGP id EFC895FA

  reply	other threads:[~2014-12-24 19:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-24  9:32 hostapd and 11h support Arend van Spriel
2014-12-24 17:32 ` Jouni Malinen
2014-12-24 18:29   ` Arend van Spriel
2014-12-24 19:04     ` Jouni Malinen [this message]
2014-12-24 20:40       ` Arend van Spriel
2014-12-25  9:10         ` Jouni Malinen

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=20141224190452.GA6933@w1.fi \
    --to=j@w1.fi \
    --cc=arend@broadcom.com \
    --cc=hostap@lists.shmoo.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.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 NNTP newsgroup(s).