|| ||Johannes Berg <firstname.lastname@example.org>|
|| ||Jiri Benc <email@example.com>|
|| ||[RFC 0/3] more power to cfg80211|
|| ||Wed, 22 Nov 2006 20:18:53 +0100|
"John W. Linville" <firstname.lastname@example.org>,
Simon Barber <email@example.com>,
Jouni Malinen <firstname.lastname@example.org>,
Hong Liu <email@example.com>,
David Kimdon <firstname.lastname@example.org>,
Michael Wu <email@example.com>,
Michael Buesch <firstname.lastname@example.org>,
Ivo van Doorn <email@example.com>|
The following patches are mostly proof-of-concept code for moving over
stuff to cfg80211 (like the wiphy thing).
I've changed net_dev->ieee80211_ptr to be of struct wiphy because it
allows accessing the wiphy by netdev easily then, and since wireless
drivers are (after these patches) expected to register with cfg80211
anyway it doesn't really change much. They need wiphy_priv() then but
There's lots left, cfg80211 could put some default things into sysfs, we
could notify it of added/removed netdevs (it knows when userspace does
this, but not when the driver does by default) and put links from
class/ieee80211/<wiphy>/dev:eth1 -> ../../net/eth1
and things like that.
I'm not really sure this is the best thing we can do so I'm posting this
for some review before I actually dive in and do those modifications.
Also, I need to put back a symlink from class/ieee80211/<wiphy>/device
to the hardware device. Just discovered that I apparently forgot :)
The patches are tested and work fine but we lose functionality, I
removed the possibility to create and remove virtual interfaces in
d80211 because I wanted to put it into cfg80211 already (well, just
needs the d80211 cfg handler...) but then didn't put it in so far.
If you feel this is something worth pursuing please shout and I'll fix
these issues and submit the patches for actual inclusion.