> > I would have to mention at this point that A-MSDU deaggregation is > > obligatory according to the 802.11n, so excluding it would be a spec > > violation. > > Right. But does that really matter for purposes of getting the code into > a development tree? What we're aiming for here is getting the code out > of your hands so that it won't conflict with other stuff that's work in > progress, rather than aiming for spec compliance (which is something I'd > aim for when merging this stuff up into Linus's tree) > Oh, sorry for misunderstanding you folks. Yes, getting the code into the development tree will be excellent. I am already working on the rx_h_data fix we talked about, and will sent it over early next week to wrap things up. Thanks ron > > What I will do is to put some out-of-band effort here, fixing the > > rx_h_data infrastructure, so it will be able to support rx_h_amsdu as > > well, thus eliminating the EAPOL bug. > > Thanks much! > > johannes > > - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
