Johannes Berg <johannes@...> writes:
>
> On Tue, 2016-03-15 at 13:01 +0000, Roger James wrote:
> >
> > roger <at> dragon:~/linux-mainline$ find . -name "*.[ch]" -exec grep -n
> > IEEE80211_HW_WANT_MONITOR_VIF {} \; -print
> > 1851: * <at> 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
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@...
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
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
��.n��������+%������w��{.n�����{���zW����ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
