From: Denis Kenzior <denkenz@gmail.com>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: brcmfmac & DEL_INTERFACE
Date: Tue, 28 May 2019 15:49:28 -0500 [thread overview]
Message-ID: <134f3c7f-5268-02bb-609b-ffbd48e78209@gmail.com> (raw)
In-Reply-To: <5679a6a1-e4a1-1f55-5b6d-21b178201078@broadcom.com>
Hi Arend,
On 05/28/2019 03:27 PM, Arend Van Spriel wrote:
> On 5/28/2019 8:16 PM, Denis Kenzior wrote:
>> Hi Arend,
>>
>> We noticed that brcmfmac doesn't support .del_virtual_intf for
>> non-p2p/ap interface types. Any chance this can be added?
>>
>> We currently remove all wifi interfaces and re-create the needed ones
>> with SOCKET_OWNER set, and it would be nice if we didn't need to treat
>> brcmfmac specially.
>
> This came up recently. During probe the driver creates a network
> interface that we refer to as primary interface. We consider this
> non-virtual and ownership is with the driver. My guess is that this
> concept comes from the WEXT era, where we did not have the ieee80211 phy
> objects to interact with the driver from user-space. I suppose you don't
> mind the creation of this interface and just want to allow removing it,
> right?
Correct. If we can at least get the DEL_INTERFACE supported, that would
solve our immediate use case.
I do think that the drivers should not be creating a netdev by default
and should wait until userspace asks for it. But that is a separate
topic, with backwards compatibility concerns, so I'll leave it for the
future :)
Regards,
-Denis
prev parent reply other threads:[~2019-05-28 20:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 18:16 brcmfmac & DEL_INTERFACE Denis Kenzior
2019-05-28 20:27 ` Arend Van Spriel
2019-05-28 20:49 ` Denis Kenzior [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=134f3c7f-5268-02bb-609b-ffbd48e78209@gmail.com \
--to=denkenz@gmail.com \
--cc=arend.vanspriel@broadcom.com \
--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