From: Michael Buesch <mb@bu3sch.de>
To: John Linville <linville@tuxdriver.com>
Cc: bcm43xx-dev@lists.berlios.de, linux-wireless@vger.kernel.org
Subject: Please pull latest and greatest bcm43xx
Date: Sat, 16 Jun 2007 20:17:47 +0200 [thread overview]
Message-ID: <200706162017.47516.mb@bu3sch.de> (raw)
John,
Please pull for-linville branch of my tree.
It contains a lot of bugfixes and makes a _big_ step towards
mergability for mainline.
It's not 100% ready for a merge, yet, but we are making good progress.
The transmission power problems on the 4306, that were one of the big
merge blockers, seem almost all fixed. I get good performance now.
I also added lots of txpower debugging stuff so one can actually
see what's going on and how it's scaling.
Together with Michael Wu's sta-locking rewrite patch for
mac80211 we have the most critical merge blockers resolved now.
I'd like people to test this code.
It will spew a big assertion failure and a stacktrace on loading.
Ignore that for now. It's known and considered nonfatal for now.
The following changes since commit 9181e959da76d85d688d8ec763702ed2f3b4edf9:
John W. Linville:
rt2x00firmware.c: include delay.h to avoid build error on ppc64
are found in the git repository at:
http://bu3sch.de/git/wireless-dev.git/ for-linville
Michael Buesch:
bcm43xx-mac80211: Don't stop the mac80211 software queues in pwork.
Merge branch 'master' of git://git.kernel.org/.../linville/wireless-dev
bcm43xx-mac80211: Use the mac80211 provided workqueue
bcm43xx-mac80211: Fix mutex leakage in pwork.
bcm43xx-mac80211: Flush the workqueue to make sure periodic work has finished.
bcm43xx-mac80211: Implement runtime debugging mechanism.
bcm43xx-mac80211: Code to inject TX ring overflows.
bcm43xx-mac80211: Rewrite the attenuation adjustment.
Merge branch 'master' of git://git.kernel.org/.../linville/wireless-dev
ssb: Fix maxpwr and itssi read.
bcm43xx-mac80211: Add more txpower debugging.
bcm43xx-mac80211: add debugfs file to manually control txpower
bcm43xx-mac80211: Some LO cleanups
Merge branch 'master' of git://git.kernel.org/.../linville/wireless-dev
bcm43xx-mac80211: Use the dynamic min/max values for adjusting the attenuation.
drivers/net/wireless/mac80211/bcm43xx/bcm43xx.h | 29 +
.../wireless/mac80211/bcm43xx/bcm43xx_debugfs.c | 210 +++++++++
.../wireless/mac80211/bcm43xx/bcm43xx_debugfs.h | 21 +
.../net/wireless/mac80211/bcm43xx/bcm43xx_dma.c | 63 +++
.../net/wireless/mac80211/bcm43xx/bcm43xx_dma.h | 10
drivers/net/wireless/mac80211/bcm43xx/bcm43xx_lo.c | 107 ++--
drivers/net/wireless/mac80211/bcm43xx/bcm43xx_lo.h | 6
.../net/wireless/mac80211/bcm43xx/bcm43xx_main.c | 64 +--
.../net/wireless/mac80211/bcm43xx/bcm43xx_phy.c | 515 ++++++++++++-----------
.../net/wireless/mac80211/bcm43xx/bcm43xx_phy.h | 23 +
.../net/wireless/mac80211/bcm43xx/bcm43xx_xmit.c | 18 +
.../net/wireless/mac80211/bcm43xx/bcm43xx_xmit.h | 2
drivers/ssb/pci.c | 12
include/linux/ssb/ssb_regs.h | 12
14 files changed, 693 insertions(+), 399 deletions(-)
--
Greetings Michael.
next reply other threads:[~2007-06-16 18:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-16 18:17 Michael Buesch [this message]
2007-06-16 19:13 ` Please pull latest and greatest bcm43xx Andrew J. Barr
2007-06-17 15:48 ` Jory A. Pratt
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=200706162017.47516.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).