Jiri,
thanks a lot for your work on nl80211! New netlink interface is
one of the most important things regarding 802.11 stack now.
Wait till you see my weekend patch series ;)
Seems ineffective to me. Couldn't you require users of nl80211 to fill
ieee80211_ptr field in all of their
Another thing that crossed my mind: Should we have a netlink call for
adding virtual interfaces as well? Because then, the ipw2x00 drivers can
have their monitor interface(s) added the same way.
johannes
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to
On Mon, Aug 21, 2006 at 08:44:52AM +0200, Johannes Berg wrote:
Another thing that crossed my mind: Should we have a netlink call for
adding virtual interfaces as well? Because then, the ipw2x00 drivers can
have their monitor interface(s) added the same way.
Yes.
--
John W. Linville
[EMAIL
Here's a respun patch hopefully addressing most of Jiri's comments, and
allowing to add/remove virtual interfaces via netlink as well.
I introduced a new notion of 'wiphy' which is just a number handed out
by nl80211 for each registered backend, and I also changed it so that
each backend must
Johannes,
thanks a lot for your work on nl80211! New netlink interface is
one of the most important things regarding 802.11 stack now.
Fri, 18 Aug 2006 16:49:25 +0200, Johannes Berg wrote:
[...]
+/**
+ * struct nl80211_driver - backend description for wireless configuration
+ *
+ * This
Here's a new version with a cleaned up interface and methods for each
command instead of multiplexing the commands right away. This cuts down
code in nl80211 users because attributes are already checked and
unpacked etc.
Packet injection also still works :P
johannes
--- /dev/null 1970-01-01
Hey,
This is a patch laying the groundwork for nl80211. I've decided to
implement it below net/wireless/ so that when we add further things like
configfs support for some things that can just be added there.
Currently, it lays the groundwork for netlink userspace communication.
None of the
