linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Felix Fietkau <nbd@nbd.name>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 11/11] mt76x02: enable AP mode for USB
Date: Mon, 4 Mar 2019 12:04:28 +0100	[thread overview]
Message-ID: <20190304110427.GA2008@redhat.com> (raw)
In-Reply-To: <20190304105506.GB3073@localhost.localdomain>

On Mon, Mar 04, 2019 at 11:55:07AM +0100, Lorenzo Bianconi wrote:
> > Enable AP mode. For now without multi-vif support, this will require
> > more testing and investigation.
> > 
> > Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
> > ---
> >  drivers/net/wireless/mediatek/mt76/mt76x02_util.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/drivers/net/wireless/mediatek/mt76/mt76x02_util.c b/drivers/net/wireless/mediatek/mt76/mt76x02_util.c
> > index 38997076cb03..99c729f6701d 100644
> > --- a/drivers/net/wireless/mediatek/mt76/mt76x02_util.c
> > +++ b/drivers/net/wireless/mediatek/mt76/mt76x02_util.c
> > @@ -142,6 +142,7 @@ void mt76x02_init_device(struct mt76x02_dev *dev)
> >  
> >  	wiphy->interface_modes =
> >  		BIT(NL80211_IFTYPE_STATION) |
> > +		BIT(NL80211_IFTYPE_AP) |
> >  #ifdef CONFIG_MAC80211_MESH
> >  		BIT(NL80211_IFTYPE_MESH_POINT) |
> 
> I think we need to disable DFS channels for the moment (for mt76x{0,2}u) since
> dfs is not supported yet

How this should be done ? Is sufficient to check IEEE80211_CHAN_RADAR
and mt76_is_usb() on set channel end return -EINVAL error ? Or different
way ?

Stanislaw



  parent reply	other threads:[~2019-03-04 11:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-04  9:48 [PATCH 00/11] mt76x02: AP support for USB with PS Stanislaw Gruszka
2019-03-04  9:48 ` [PATCH 01/11] mt76x02: introduce mt76x02_beacon.c Stanislaw Gruszka
2019-03-04  9:48 ` [PATCH 02/11] mt76x02: add hrtimer for pre TBTT for USB Stanislaw Gruszka
2019-03-04  9:48 ` [PATCH 03/11] mt76x02: introduce beacon_ops Stanislaw Gruszka
2019-03-04  9:48 ` [PATCH 04/11] mt76x02u: implement beacon_ops Stanislaw Gruszka
2019-03-04  9:48 ` [PATCH 05/11] mt76x02: generalize some mmio beaconing functions Stanislaw Gruszka
2019-03-04  9:48 ` [PATCH 06/11] mt76x02u: add sta_ps Stanislaw Gruszka
2019-03-04  9:48 ` [PATCH 07/11] mt76x02: disable HW encryption for group frames Stanislaw Gruszka
2019-03-04  9:48 ` [PATCH 08/11] mt76x02u: implement pre TBTT work for USB Stanislaw Gruszka
2019-03-16 19:44   ` Felix Fietkau
2019-03-18  9:50     ` Stanislaw Gruszka
2019-03-18  9:57       ` Felix Fietkau
2019-03-18 10:03         ` Stanislaw Gruszka
2019-03-04  9:48 ` [PATCH 09/11] mt76x02u: add mt76_release_buffered_frames Stanislaw Gruszka
2019-03-04  9:48 ` [PATCH 10/11] mt76: unify set_tim Stanislaw Gruszka
2019-03-04  9:48 ` [PATCH 11/11] mt76x02: enable AP mode for USB Stanislaw Gruszka
2019-03-04 10:55   ` Lorenzo Bianconi
2019-03-04 11:00     ` Felix Fietkau
2019-03-04 11:04     ` Stanislaw Gruszka [this message]
2019-03-04 11:08       ` Lorenzo Bianconi
2019-03-04 12:45         ` Stanislaw Gruszka

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=20190304110427.GA2008@redhat.com \
    --to=sgruszka@redhat.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lorenzo.bianconi@redhat.com \
    --cc=nbd@nbd.name \
    /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).