From: Roger James <roger@beardandsandals.co.uk>
To: linux-wireless@vger.kernel.org
Subject: Re: The mac80211 softmac driver subsystem and handling of monitor interfaces
Date: Wed, 16 Mar 2016 09:53:14 +0000 [thread overview]
Message-ID: <56E92D0A.9090905@beardandsandals.co.uk> (raw)
On 15 Mar 2016 13:08, Johannes Berg <johannes@sipsolutions.net> wrote:
>
> On Tue, 2016-03-15 at 13:01 +0000, Roger James wrote:
> >
> > roger@dragon:~/linux-mainline$ find . -name "*.[ch]" -exec grep -n
> > IEEE80211_HW_WANT_MONITOR_VIF {} \; -print
> > 1851: * @IEEE80211_HW_WANT_MONITOR_VIF: The driver would like to be
> > informed of
> > 1928: IEEE80211_HW_WANT_MONITOR_VIF,
> > ./include/net/mac80211.h
> >
> > Is that what you meant. Nobody seems to be using it. Even mac80211
> > itself. Or am I being stupid again :-)
> >
>
> There are macros generating the checks and setting it, so you want to
> grep without the IEEE80211_HW_ prefix
>
> johannes
> --
Thanks guys I have got it now.
However that only accounts for the ath10k, iwldvm, and iwlmvm drivers. I
realise that there is a lot of history here, but is what the remaining
drivers doing in any way deprecated? Also can anyone give me a heads up
on what the architectural difference is between hooking the monitor
config change and and setting the want monitor flag. Is one way
preferable to the other? Both seem to inform the driver that there is a
transition between having no monitor virtual interfaces and having one
or more.
Cheers,
Roger
next reply other threads:[~2016-03-16 9:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 9:53 Roger James [this message]
2016-03-16 9:56 ` The mac80211 softmac driver subsystem and handling of monitor interfaces Johannes Berg
-- strict thread matches above, loose matches on Subject: below --
2016-03-15 10:42 Roger James
2016-03-15 12:15 ` Johannes Berg
2016-03-15 13:01 ` Roger James
2016-03-15 13:08 ` Johannes Berg
2016-03-15 16:42 ` Roger James
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=56E92D0A.9090905@beardandsandals.co.uk \
--to=roger@beardandsandals.co.uk \
--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).