Re: [PATCH 0/11] convert d80211 to a proper protocol

2006-11-08 Thread Jeff Garzik
Jiri Benc wrote: On Mon, 06 Nov 2006 22:09:54 +0100, Johannes Berg wrote: What did happen with d80211: add a function to get the wiphy index d80211: add a perm_addr hardware property d80211: add a struct device* hardware property d80211: add a ethtool_ops hardware property patches? Well after s

Re: [PATCH 0/11] convert d80211 to a proper protocol

2006-11-08 Thread Johannes Berg
On Wed, 2006-11-08 at 13:09 +0100, Jiri Benc wrote: > Unfortunately, in case of broadcast and multicast frames, we probably > need to go through decryption handlers for each interface individually. > At least I wasn't able to find a solution which allows to perform > decryption only once for each

Re: [PATCH 0/11] convert d80211 to a proper protocol

2006-11-08 Thread Johannes Berg
On Wed, 2006-11-08 at 12:58 +0100, Jiri Benc wrote: > Ok. Personally, I don't care if we pass net_device or ieee80211_local > to drivers. I see pros and cons of both solutions. As I said in the other patchset, I'd prefer to not change the API for these cleanups unless we have to, so dropping this

Re: [PATCH 0/11] convert d80211 to a proper protocol

2006-11-08 Thread Jiri Benc
On Tue, 07 Nov 2006 00:06:34 +0100, Johannes Berg wrote: > Keeping with the protocol theme, we need to rewrite the rx path to do > the following in the order listed: > > 1) if any monitor interfaces are up, copy the skb, add the > prism/radiotap/whatever header and then clone it to all monito

Re: [PATCH 0/11] convert d80211 to a proper protocol

2006-11-08 Thread Jiri Benc
On Mon, 06 Nov 2006 22:09:54 +0100, Johannes Berg wrote: > > What did happen with > > d80211: add a function to get the wiphy index > > d80211: add a perm_addr hardware property > > d80211: add a struct device* hardware property > > d80211: add a ethtool_ops hardware property > > patches? > > Well

Re: [PATCH 0/11] convert d80211 to a proper protocol

2006-11-07 Thread Johannes Berg
On Tue, 2006-11-07 at 20:02 +0100, Ivo van Doorn wrote: > > http://johannes.sipsolutions.net/files/d80211-cleanup/ > > You might want to fix the rights to the folder again ;) Ahrg, sorry. I should make http://johannes.sipsolutions.net/patches/ and leave that open all the way. johannes signatu

Re: [PATCH 0/11] convert d80211 to a proper protocol

2006-11-07 Thread Ivo van Doorn
Hi, > http://johannes.sipsolutions.net/files/d80211-cleanup/ You might want to fix the rights to the folder again ;) Ivo - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info

Re: [PATCH 0/11] convert d80211 to a proper protocol

2006-11-07 Thread Johannes Berg
I've put a new patchset up at http://johannes.sipsolutions.net/files/d80211-cleanup/ It now contains: 001-cfg80211-fix-Makefile.patch 002-cfg80211-wext-compat.patch as before. 003-d80211-reduce-mdev-1.patch 004-d80211-reduce-mdev-2.patch 005-d80211-cleanup-rxmgmt.patch 006-d80211-scan-sanity.pa

Re: [PATCH 0/11] convert d80211 to a proper protocol

2006-11-06 Thread Johannes Berg
On Mon, 2006-11-06 at 21:01 +0100, Jiri Benc wrote: > This definitely breaks AP mode. In the code, there is heavily (ab)used > the fact that the master device is in fact an AP device. I tried to fix > that but it was so difficult I gave up. It is needed to rewrite the > whole RX path (and even tha

Re: [PATCH 0/11] convert d80211 to a proper protocol

2006-11-06 Thread Johannes Berg
[reordering a bit] > >This changes the 'cookie' that d80211 returns from alloc_hw > >to be an opaque value to the driver. Turned out that it wasn't > >such a great idea but since it was generally a clean up I kept > >this patch to base my other patches on. > > ACK. > What did hap

Re: [PATCH 0/11] convert d80211 to a proper protocol

2006-11-06 Thread Jiri Benc
On Sun, 05 Nov 2006 16:39:34 +0100, Johannes Berg wrote: > 003-d80211-cookie.patch >d80211: change the cookie to be opaque > >This changes the 'cookie' that d80211 returns from alloc_hw >to be an opaque value to the driver. Turned out that it wasn't >such a great idea but since it

Re: [PATCH 0/11] convert d80211 to a proper protocol

2006-11-05 Thread Johannes Berg
On Sun, 2006-11-05 at 18:05 +0100, Johannes Berg wrote: hey, I thought I caught this one before it went out to add the last paragraph :/ sorry. the other one is the intended copy. johannes signature.asc Description: This is a digitally signed message part

Re: [PATCH 0/11] convert d80211 to a proper protocol

2006-11-05 Thread Johannes Berg
Hi, > Previously the open() and stop() methods in ieee80211_hw had been > deprecated and the driver should enable or disable the radio > based on the add_interface and remove_interface() functions. > Now that the driver should provide open() and stop() for the netdevice > structure does this mean

Re: [PATCH 0/11] convert d80211 to a proper protocol

2006-11-05 Thread Johannes Berg
Hi, > Previously the open() and stop() methods in ieee80211_hw had been > deprecated and the driver should enable or disable the radio > based on the add_interface and remove_interface() functions. > Now that the driver should provide open() and stop() for the netdevice > structure does this mean

Re: [PATCH 0/11] convert d80211 to a proper protocol

2006-11-05 Thread Ivo van Doorn
Hi, > I figured I'd look how hard it actually was to convert d80211 to a > proper protocol. And contrary to my own expectations I succeeded in > doing that in just over a day. Just like 8021q, it has virtual devices. > > The patchset is huge and can be found at > http://johannes.sipsolutions.net/

[PATCH 0/11] convert d80211 to a proper protocol

2006-11-05 Thread Johannes Berg
Hi, I figured I'd look how hard it actually was to convert d80211 to a proper protocol. And contrary to my own expectations I succeeded in doing that in just over a day. Just like 8021q, it has virtual devices. The patchset is huge and can be found at http://johannes.sipsolutions.net/files/d80211