From: "Stefan Brüns" <stefan.bruens@rwth-aachen.de>
To: linux-wireless@vger.kernel.org
Subject: Throughput regression in b43 caused by spurious avoidance implementation
Date: Mon, 24 Sep 2012 23:46:05 +0200 [thread overview]
Message-ID: <1698401.RCfH1UvLZM@pebbles> (raw)
Hi everyone,
as I have been plagued by the performance regression in b43 between linux 3.2
and 3.3, I have bisected it:
git bisect good
49d55cef5b1925a5c1efb6aaddaa40fc7c693335 is the first bad commit
commit 49d55cef5b1925a5c1efb6aaddaa40fc7c693335
Author: Rafał Miłecki <zajec5@gmail.com>
Date: Sun Dec 11 13:16:51 2011 +0100
b43: N-PHY: implement spurious tone avoidance
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
:040000 040000 f6177f4c33e1d382a430ad83db1e4b3f9dd66dfd
1b161ac9a16a481f259606edda5039c2be5147f4 M drivers
lspci -v{n,}:
08:00.0 0280: 14e4:432b (rev 01)
Subsystem: 1028:000d
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at f0600000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [58] Vendor Specific Information: Len=78 <?>
Capabilities: [e8] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [d0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Virtual Channel
Capabilities: [160] Device Serial Number 7e-d8-e5-xx-xx-xx-xx
Capabilities: [16c] Power Budgeting <?>
Kernel driver in use: b43-pci-bridge
08:00.0 Network controller: Broadcom Corporation BCM4322 802.11a/b/g/n
Wireless LAN Controller (rev 01)
Subsystem: Dell Wireless 1510 Wireless-N WLAN Mini-Card
Used channel is channel 13, 2.472GHz, AP is AVM 7112, "G-only" mode.
Regards,
Stefan
--
Stefan Brüns / Bergstraße 21 / 52062 Aachen
phone: +49 241 53809034 mobile: +49 151 50412019
next reply other threads:[~2012-09-24 22:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 21:46 Stefan Brüns [this message]
2012-09-25 6:29 ` Throughput regression in b43 caused by spurious avoidance implementation Rafał Miłecki
2012-12-17 3:39 ` Stefan Brüns
2013-04-26 9:51 ` Rafał Miłecki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1698401.RCfH1UvLZM@pebbles \
--to=stefan.bruens@rwth-aachen.de \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.