On Wednesday 16 September 2009 22:17:55 Thomas Ilnseher wrote: > Am Mittwoch, den 16.09.2009, 21:40 +0200 schrieb Gábor Stefanik: > > You are essentially implementing dead code at this point - this will > > only ever be called if hardware-accelerated TX power control is > > enabled - and HW TX power control is unsupported, even for G-PHYs. > Then the question remains, why this brings my device to 54 MBit/s ? > > I did double check again with the old driver: > > wlan0 IEEE 802.11bg ESSID:"tommy" > Mode:Managed Frequency:2.412 GHz Access Point: > Bit Rate=9 Mb/s Tx-Power=20 dBm > Retry long limit:7 RTS thr:off Fragment thr:off > Encryption key:off > Power Management:off > Link Quality=70/70 Signal level=5 dBm > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > Patched driver: > > wlan0 IEEE 802.11bg ESSID:"tommy" > Mode:Managed Frequency:2.412 GHz Access Point: XXX > Bit Rate=54 Mb/s Tx-Power=20 dBm > Retry long limit:7 RTS thr:off Fragment thr:off > Encryption key:off > Power Management:off > Link Quality=70/70 Signal level=10 dBm > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 The iwconfig output doesn't tell you anything about the actual net TX rate. Please benchmark it with iperf. -- 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
