From: Larry Finger <Larry.Finger@lwfinger.net>
To: Michael Buesch <mb@bu3sch.de>
Cc: linux-wireless@vger.kernel.org, bcm43xx-dev@lists.berlios.de
Subject: Re: [PATCH RFT] b43: Rewrite PHY API for N-PHY/LP-PHY
Date: Wed, 20 Aug 2008 17:40:32 -0500 [thread overview]
Message-ID: <48AC9D60.9000902@lwfinger.net> (raw)
In-Reply-To: <200808160029.56876.mb@bu3sch.de>
Michael Buesch wrote:
> This is the first part for the rewrite of the b43 PHY API.
> This is needed in order to make development of N and LP code possible.
>
> PLEASE TEST TEST TEST TEST TEST
>
> Lots of testing on lots of different devices is needed to ensure this
> doesn't introduce regressions due to typos.
> 95% of the patch just moves large parts of the PHY code from one file
> to another. More move-patches will follow.
> 5% of the patch introduces an "ops" based PHY API.
>
> Please test on all of your devices.
I have now tested on a BCM4311/2 with positive results. The transmit
throughput is roughly the same at 20.7 Mbs with a 54 Mbs bulk rate.
Larry
next prev parent reply other threads:[~2008-08-20 22:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-15 22:29 [PATCH RFT] b43: Rewrite PHY API for N-PHY/LP-PHY Michael Buesch
2008-08-16 4:01 ` Larry Finger
2008-08-16 18:09 ` Larry Finger
2008-08-16 19:36 ` Michael Buesch
2008-08-17 19:26 ` [PATCH RFT] b43: Rewrite PHY API for N-PHY/LP-PHY -- good on 4311 Ehud Gavron
2008-08-17 20:42 ` Larry Finger
2008-08-18 7:41 ` Holger Schurig
2008-08-18 12:57 ` Michael Buesch
2008-08-18 13:48 ` Larry Finger
2008-08-18 13:01 ` Michael Buesch
2008-08-20 22:40 ` Larry Finger [this message]
2008-08-21 13:07 ` [PATCH RFT] b43: Rewrite PHY API for N-PHY/LP-PHY Michael Buesch
2008-08-21 16:16 ` Sean Hodges
[not found] ` <200808211643.m7LGhuaq002925@mi0.bluebottle.com>
2008-08-21 16:58 ` Michael Buesch
2008-08-21 20:27 ` Sean Hodges
2008-08-22 11:06 ` Rafał Miłecki
2008-08-24 12:24 ` Benoît Knecht
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=48AC9D60.9000902@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
/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).