From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
Jiri Slaby <jirislaby@gmail.com>,
Nick Kossifidis <mickflemm@gmail.com>,
Bob Copeland <me@bobcopeland.com>, Jouni Malinen <j@w1.fi>,
Vasanthakumar Thiagarajan <vasanth@atheros.com>,
Christian Lamparter <chunkeey@googlemail.com>,
Lennert Buytenhek <buytenh@wantstofly.org>,
Ivo van Doorn <ivdoorn@gmail.com>,
Gertjan van Wingerde <gwingerde@gmail.com>,
Helmut Schaa <helmut.schaa@googlemail.com>
Subject: concurrency advertising -- driver maintainers
Date: Fri, 13 May 2011 14:44:17 +0200 [thread overview]
Message-ID: <1305290657.3487.32.camel@jlt3.sipsolutions.net> (raw)
Please excuse the long CC list. I want to make you aware that I plan to
remove the WIPHY_FLAG_ENFORCE_COMBINATIONS flag again soon, so that all
drivers that don't advertise valid combinations will not be able to have
multiple virtual interfaces.
The affected drivers, as far as I can tell, are:
* ath5k
* ath9k
* carl9170
* hwsim (I'll look at this)
* iwlagn (I'm handling that of course)
* mwl8k
* rt2x00 (see RFC patch)
I'm happy to help out with the restrictions code, please let me know.
I'd like to remove the flag again before it ever goes upstream, but I
understand the timing is bad, unless we hold my patch out of 2.6.40.
For completeness, I checked all drivers, and the following drivers don't
support more than a single virtual interface anyway:
* adm8211
* at76c50x-usb -- but it is broken because it has no checks
* b43
* b43legacy
* iwlegacy
* libertas_tf
* p54
* rtl8180
* rtl8187
* rtlwifi
* wl1251
* wl12xx
* zd1211
(Staging drivers:)
* brcm80211 is broken, allows multiple but can't handle it
* winbond is also broken the same way
johannes
next reply other threads:[~2011-05-13 12:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 12:44 Johannes Berg [this message]
2011-05-13 13:40 ` concurrency advertising -- driver maintainers Johannes Berg
2011-05-13 14:32 ` Sujith
2011-05-13 14:33 ` Johannes Berg
2011-05-13 14:44 ` Sujith
2011-05-13 14:44 ` Gertjan van Wingerde
2011-05-13 14:52 ` Johannes Berg
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=1305290657.3487.32.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=buytenh@wantstofly.org \
--cc=chunkeey@googlemail.com \
--cc=gwingerde@gmail.com \
--cc=helmut.schaa@googlemail.com \
--cc=ivdoorn@gmail.com \
--cc=j@w1.fi \
--cc=jirislaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=me@bobcopeland.com \
--cc=mickflemm@gmail.com \
--cc=vasanth@atheros.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).