From: Johannes Berg <johannes@sipsolutions.net>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
"Gábor Stefanik" <netrolller.3d@gmail.com>,
linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
b43-dev@lists.infradead.org
Subject: [PATCH 0/4] Make N-PHY support experimental
Date: Thu, 09 Dec 2010 16:25:38 +0100 [thread overview]
Message-ID: <1291908338.3540.16.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4D00F3C3.6040801@lwfinger.net>
On Thu, 2010-12-09 at 09:20 -0600, Larry Finger wrote:
> It has a rev 2 PHY, and a rev 4 0x2055 radio.
>
> I am willing to buy a higher PHY rev device for testing. Any idea what is in a
> 4324A-BRCM1036?
It says BCM94322 on the image, and if that's any indication, I have a
4322 with pci ID 14e4:432b (but it's an Apple build):
b43-phy0: Broadcom 4322 WLAN found (core revision 16)
b43-phy0 debug: Found PHY: Analog 8, Type 4, Revision 4
b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2056, Revision 3
johannes
next prev parent reply other threads:[~2010-12-09 15:25 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 20:55 [PATCH 0/4] Make N-PHY support experimental Rafał Miłecki
2010-12-07 20:55 ` [PATCH 1/4] b43: N-PHY: silence warnings Rafał Miłecki
2010-12-07 20:55 ` [PATCH 2/4] b43: set TMS to work with current band width for N-PHY Rafał Miłecki
2010-12-07 21:08 ` Michael Büsch
2010-12-09 14:12 ` Rafał Miłecki
2010-12-09 14:13 ` Rafał Miłecki
2010-12-09 14:19 ` Michael Büsch
2010-12-09 14:23 ` Rafał Miłecki
2010-12-09 14:28 ` Michael Büsch
2010-12-09 14:41 ` Michael Büsch
2010-12-07 20:55 ` [PATCH 3/4] b43: fix split of N-PHY devices into supported and not (based on PHY rev) Rafał Miłecki
2010-12-07 20:56 ` [PATCH 4/4] b43: rename config option for N-PHY, drop BROKEN Rafał Miłecki
2010-12-07 21:04 ` [PATCH 0/4] Make N-PHY support experimental Johannes Berg
2010-12-07 22:57 ` Gábor Stefanik
2010-12-07 23:11 ` Larry Finger
2010-12-08 3:37 ` Larry Finger
2010-12-09 14:11 ` Rafał Miłecki
2010-12-09 15:20 ` Larry Finger
2010-12-09 15:25 ` Johannes Berg [this message]
2010-12-09 15:28 ` Rafał Miłecki
2010-12-09 15:33 ` Johannes Berg
2010-12-09 15:37 ` Rafał Miłecki
2010-12-09 16:03 ` Larry Finger
2010-12-10 3:52 ` Jon Saul
2010-12-10 4:05 ` Larry Finger
2010-12-09 16:10 ` Rafał Miłecki
2010-12-08 15:15 ` b43 N PHY status report Larry Finger
2010-12-10 16:57 ` Peter Stuge
2010-12-10 17:15 ` Larry Finger
2010-12-10 18:34 ` Peter Stuge
2010-12-10 18:44 ` Peter Stuge
2010-12-13 17:00 ` Rafał Miłecki
2010-12-13 17:41 ` Larry Finger
2010-12-13 18:17 ` Rafał Miłecki
2010-12-13 18:37 ` Larry Finger
2010-12-13 18:34 ` Peter Stuge
2010-12-13 18:43 ` Larry Finger
2010-12-10 18:22 ` Francesco Gringoli
2010-12-10 18:30 ` Francesco Gringoli
2010-12-10 18:47 ` Johannes Berg
2010-12-10 19:02 ` Larry Finger
2010-12-10 19:04 ` Gábor Stefanik
2010-12-10 19:08 ` Johannes Berg
2010-12-21 9:25 ` David Woodhouse
2010-12-21 9:30 ` Rafał Miłecki
2010-12-21 14:30 ` Larry Finger
2010-12-10 18:53 ` Konstantinos Karantias
2010-12-10 19:00 ` Larry Finger
2010-12-09 14:09 ` [PATCH 0/4] Make N-PHY support experimental 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=1291908338.3540.16.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Larry.Finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--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 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).