On Wednesday 30 April 2008 15:07:29 Johannes Berg wrote: > > > Any testing of this series is welcome, even just the first patch by itself > > (especially with drivers other than b43), it doesn't make sense to test with > > patch 2 and not 3 though, so if you're going to test one by one treat 2/3 as > > a set. > > I have, of course, tested this series with b43 (and founds dozens of > bugs...) Michael, thanks for your dma overflow injection feature :) :) > One thing that turned up was that if I enable dma overflow with this > patchset then b43 hardware spews lots of PHY TX errors. I have verified > that the ieee80211_tx_control info is correct, and the frame data is > also fine, so I'm not sure what's up there. Could that be unrelated to > this patch? I haven't tested dma overflow injection w/o this series yet. Hm, not sure. It could be a b43 bug, of course. But last time I tested the overflow injection, it worked fine. And that's not too long ago. Probably 3 or 4 weeks. Of course, we should test this again with the QOS patch applied and removed now. If that patch does actually trigger it, then we probably still need to search for a b43 bug. Is the QOS callback (forgot its name) called when we have an overflow? -- Greetings Michael. -- 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
