All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: seanhodges@bluebottle.com
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: Thu, 21 Aug 2008 18:58:51 +0200	[thread overview]
Message-ID: <200808211858.51899.mb@bu3sch.de> (raw)
In-Reply-To: <200808211643.m7LGhuaq002925@mi0.bluebottle.com>

On Thursday 21 August 2008 18:16:23 Sean Hodges wrote:
> On Sat, 2008-08-16 at 00:29 +0200, 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.
> > 
> > http://bu3sch.de/patches/wireless-testing/20080816-0023/patches/002-b43-phy-ops.patch
> > Apply against wireless-testing.git
> 
> As a novice to driver development, is there some way I can help with
> testing this?
> 
> I have no experience of driver development/testing, but have an N-PHY

To say it once again:
Despite the fact that the subject of this email mentiones N and LP PHYs, it
implements _nothing_ N and LP related. It just _prepares_ the code for the
future when we will add N and LP stuff (and other PHY stuff. Also A/B/G related).

-- 
Greetings Michael.

  parent reply	other threads:[~2008-08-21 16:59 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 ` [PATCH RFT] b43: Rewrite PHY API for N-PHY/LP-PHY Larry Finger
2008-08-21 13:07   ` Michael Buesch
2008-08-21 16:16 ` Sean Hodges
     [not found] ` <200808211643.m7LGhuaq002925@mi0.bluebottle.com>
2008-08-21 16:58   ` Michael Buesch [this message]
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=200808211858.51899.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=seanhodges@bluebottle.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 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.