<br><div class="gmail_quote">2011/3/8 Rafał Miłecki <span dir="ltr"><<a href="mailto:zajec5@gmail.com" target="_blank">zajec5@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
W dniu 4 marca 2011 01:37 użytkownik chris@martin.cc <chris@martin.cc> napisał:<br>
<div>> Maybe the way to investigate this further is to look at what is being<br>
> passed between<br>
> mac80211 and b43, with the different firmwares.<br>
><br>
> I will add some debugging on the weekend and see what I can uncover.<br>
<br>
</div>Maybe it'd make sense to check what we get from hardware with older<br>
vs. newer firmware?<br>
<br>
Attached patch was compile-tested only.<br>
<br>
It may put a lot of messages in your dmesg, don't try to run it for too long ;)<br>
<font color="#888888"><br></font></blockquote><div><br></div><div>Rafal</div><div><br></div><div>I think something went wrong with the patch you attached.</div><div>when I detach it, it contains </div>
<div> </div></div><div> Building modules, stage 2.</div><div> MODPOST 1 modules</div><div><br></div><div>And nothing else.</div><div><br></div><div><br></div><div>Further.. When I was testing the driver (both in AP and STA modes) I had it disconnected form the network, and disconnected from the bridge. As a result there would have been very little data transmitted. However there is lots of 802.11 traffic in the air. So I think that we will find the problem on the receive path rather than the transmit path, Just my 2c worth until I get some logging in there.</div>
<div><br></div><div><br clear="all">----------------------------------------------------------<br>Chris Martin<br>m: +61 419 812 371<br>----------------------------------------------------------<br>
<br></div>