> 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) > 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. > I hope that this fix will be ready soon in order to enable the merge, > and then i will move on to next steps. Thanks much! johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
