From: "Rafał Miłecki" <zajec5@gmail.com>
To: b43-dev@lists.infradead.org
Subject: Interesting 14e4:4321
Date: Fri, 6 May 2011 23:48:54 +0200 [thread overview]
Message-ID: <BANLkTimqRJnhE4n-4UAxWOEObRmuSuBUSQ@mail.gmail.com> (raw)
In-Reply-To: <4DC467F8.9050503@lwfinger.net>
W dniu 6 maja 2011 23:28 u?ytkownik Larry Finger
<Larry.Finger@lwfinger.net> napisa?:
> On 05/06/2011 03:40 PM, Rafa? Mi?ecki wrote:
>>
>> Swen has found 14e4:4321 in his WRT160N version 1.1. This is quite
>> rare and interesting so I wanted to post all info about it :)
>>
>> I'm attaching lspci and dmesg.
>>
>> I find it interesting because it seems to be SSB SOC with standard
>> cores: CC, FastEthernet, USB, MIPS, etc. Plus there is PCI bridge with
>> 14e4:4321 card connected, which is SSB-based one with (the most
>> interesting) 80211.
>>
>> Unfortunately this is one another BCM4321 with DMA not working. I
>> really need to focus on this after fixing LP-PHY and adding BCMA.
>
> From the attachments:
>
> 01:01.0 Network controller [0280]: Broadcom Corporation BCM4306 802.11a
> Wireless LAN Controller [14e4:4321] (rev 03)
> ? ? ? Subsystem: Broadcom Corporation BCM4306 802.11a Wireless LAN
> Controller [14e4:4321]
> ? ? ? Flags: bus master, fast devsel, latency 64, IRQ 2
> ? ? ? Memory at 40004000 (32-bit, non-prefetchable) [size=16K]
>
> Is this really a 5G-only card? Everything I could see about the WRT160N
> seemed to say that the routers are 802.11b/g/n.
>
> In addition, we really needed more BCM43XX confusion. Is a BCM4306 an
> 802.11b/g with a 14e4:4320 chip, or this one?
>
> Broadcom is really easy to hate!
It's some ooooold description from 2006 or so, so I'm sure it's
incorrect. I've no idea about 14e4:4320.
--
Rafa?
next prev parent reply other threads:[~2011-05-06 21:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 20:40 Interesting 14e4:4321 Rafał Miłecki
2011-05-06 21:28 ` Larry Finger
2011-05-06 21:48 ` Rafał Miłecki [this message]
2011-05-06 22:25 ` Larry Finger
2011-05-06 21:36 ` Hauke Mehrtens
2011-05-06 21:51 ` Rafał Miłecki
[not found] ` <479014597.20110507002540@googlemail.com>
[not found] ` <BANLkTi=n6gjDxGX0buUamNQAydPCMqEpjg@mail.gmail.com>
[not found] ` <274308290.20110507111432@googlemail.com>
2011-05-07 9:41 ` Rafał Miłecki
2011-05-06 21:56 ` Jonas Gorski
2011-05-06 22:14 ` Rafał Miłecki
2011-05-06 22:32 ` Jonas Gorski
2011-05-07 15:17 ` Michael Büsch
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=BANLkTimqRJnhE4n-4UAxWOEObRmuSuBUSQ@mail.gmail.com \
--to=zajec5@gmail.com \
--cc=b43-dev@lists.infradead.org \
/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