linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Sid Hayn <sidhayn@gmail.com>
Cc: Matthias Brugger <matthias.bgg@gmail.com>,
	Lorenzo Bianconi <lorenzo.bianconi@redhat.com>,
	linux-mediatek@lists.infradead.org,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Felix Fietkau <nbd@nbd.name>
Subject: Re: mt76x[02]u 802.11w support
Date: Tue, 18 Dec 2018 09:09:39 +0100	[thread overview]
Message-ID: <20181218080939.GA16795@redhat.com> (raw)
In-Reply-To: <20181217154628.GA4773@redhat.com>

On Mon, Dec 17, 2018 at 04:46:28PM +0100, Stanislaw Gruszka wrote:
> On Mon, Dec 17, 2018 at 10:07:43AM -0500, Sid Hayn wrote:
> > Interestingly when I asked for the monitor mode patch to be ported it
> > was initially refused and then just kind of happened a few weeks
> > later.
> 
> It was not quite like that. It was refused to apply on 4.19-rcX due to
> -next merge -rc conflict that it will cause. And it was promised
> that fixes will be backported thought -stable.
> 
> Regarding this case, there is no single commit that add 802.11w support
> we could request to add to -stable. It was added together with other
> features in:
> 
> commit 0ae976a11b4fb5704b597e103b5189237641c1a1
> Author: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
> Date:   Thu Sep 6 11:18:41 2018 +0200
> 
>     mt76x0: init hw capabilities
> 
> which depend on switching mt76x0u to mt76-usb layer.
> 
> So I'm not sure how this request should be satisfied.

Can you check if adding

ieee80211_hw_set(rt2x00dev->hw, MFP_CAPABLE);

is sufficient to add support for 802.11w ? 

Most likely it is, since in 4.19 mt76x0_set_key() do not allow to
set unsupported ciphers. However it returns -EINVAL instead of
-EOPNOTSUPP, so I want to be sure.

Thanks
Stanislaw

  reply	other threads:[~2018-12-18  8:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-13 14:26 mt76x[02]u 802.11w support Sid Hayn
2018-12-13 14:39 ` Lorenzo Bianconi
2018-12-15  3:43   ` Sid Hayn
2018-12-16 10:39     ` Matthias Brugger
2018-12-17 15:07       ` Sid Hayn
2018-12-17 15:46         ` Stanislaw Gruszka
2018-12-18  8:09           ` Stanislaw Gruszka [this message]
2018-12-18 18:38             ` Sid Hayn
2018-12-19  7:47               ` Stanislaw Gruszka
2018-12-19 17:08                 ` Sid Hayn

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=20181218080939.GA16795@redhat.com \
    --to=sgruszka@redhat.com \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lorenzo.bianconi@redhat.com \
    --cc=matthias.bgg@gmail.com \
    --cc=nbd@nbd.name \
    --cc=sidhayn@gmail.com \
    /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).