From: "Henry Ptasinski" <henryp@broadcom.com>
To: "David Woodhouse" <dwmw2@infradead.org>
Cc: "Gábor Stefanik" <netrolller.3d@gmail.com>,
"Rafał Miłecki" <zajec5@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"b43-dev@lists.infradead.org" <b43-dev@lists.infradead.org>,
"Henry Ptasinski" <henryp@broadcom.com>
Subject: Re: [PATCH 2/3] b43: LCN-PHY: implement disabling radio
Date: Fri, 26 Aug 2011 12:30:58 -0700 [thread overview]
Message-ID: <20110826193058.GO4888@broadcom.com> (raw)
In-Reply-To: <1313414343.3990.6.camel@shinybook.infradead.org>
On Mon, Aug 15, 2011 at 06:18:57AM -0700, David Woodhouse wrote:
> On Mon, 2011-08-15 at 01:24 +0200, Gábor Stefanik wrote:
> > Doesn't brcm80211 support this PHY? (Because then, reverse-engineering
> > wl is pointless.)
>
> I'd be great to "clean up" the interface between brcm80211 and its phy
> code, so that the phy code can be moved out of drivers/staging. And once
> we've done that, we can make b43 use it too.
>
> That way we not only get LCN PHY code, but also hopefully support for
> *other* PHYs as and when they are produced.
If you have any specific cleanup suggestions for the phy code, please send them
along.
- Henry
next prev parent reply other threads:[~2011-08-26 19:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-14 21:27 [PATCH 1/3] b43: LCN-PHY: add very basic PHY ops Rafał Miłecki
2011-08-14 21:27 ` Rafał Miłecki
2011-08-14 21:27 ` [PATCH 2/3] b43: LCN-PHY: implement disabling radio Rafał Miłecki
2011-08-14 21:27 ` Rafał Miłecki
2011-08-14 23:24 ` Gábor Stefanik
2011-08-14 23:24 ` Gábor Stefanik
2011-08-15 8:14 ` Rafał Miłecki
2011-08-15 8:14 ` Rafał Miłecki
2011-08-15 13:18 ` David Woodhouse
2011-08-15 13:18 ` David Woodhouse
2011-08-26 19:30 ` Henry Ptasinski [this message]
2011-08-14 21:27 ` [PATCH 3/3] b43: LCN-PHY: switch analog Rafał Miłecki
2011-08-14 21:27 ` 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=20110826193058.GO4888@broadcom.com \
--to=henryp@broadcom.com \
--cc=b43-dev@lists.infradead.org \
--cc=dwmw2@infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netrolller.3d@gmail.com \
--cc=zajec5@gmail.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.