public inbox for b43-dev@lists.infradead.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: b43-dev@lists.infradead.org
Subject: Table of PCIs, chipsets, etc. on b43 wiki page
Date: Sat, 05 Feb 2011 09:56:44 -0600	[thread overview]
Message-ID: <4D4D733C.30906@lwfinger.net> (raw)
In-Reply-To: <AANLkTinSVSx_AZ=sc+f5UF_8WRRtnotXZxOdXU4YOEB8@mail.gmail.com>

On 02/04/2011 11:56 PM, G?bor Stefanik wrote:
> 2011/2/5 Larry Finger <Larry.Finger@lwfinger.net>:
>> On 02/04/2011 02:27 PM, Rafa? Mi?ecki wrote:
>>> W dniu 4 lutego 2011 20:37 u?ytkownik Larry Finger
>>> <Larry.Finger@lwfinger.net> napisa?:
>>>> On 02/04/2011 12:56 PM, Rafa? Mi?ecki wrote:
>>>>> I'd like to propose little (nothing big) reogranisation of b43 hardware table:
>>>>> http://wireless.kernel.org/Zajec?action=recall&rev=4
>>>>>
>>>>> Changed columns support/supported and driver/alternatives.
>>>>>
>>>>> Are you fine with that? Can we use colored one?
>>>>
>>>> I like the colored one.
>>>>
>>>> Some small changes:
>>>>
>>>> I would eliminate the second 14e4:4312 line and move the wl entry to the first
>>>> one. I don't know if wl supports 5 GHz on that chip. I don't have mine any longer.
>>>
>>> Do you know anything about that duplicated ID? Is that true at all?
>>> Why we don't support device with that duplicated ID? Why do you want
>>> to remove it?
>>
>> I'm not sure that there really is an 802.11b/g device with ID 14e4:4312. There
>> are two flavors of BCM4312, one that is 802.11a/b/g (14e4:4312), and an
>> 802.11b/g device with ID 14e4:4315, which is the LP PHY. I suspect that the
>> confusion over the two BCM4312 items led to the duplicate entry in this table.
> 
> The device with PCI ID 0x4312 is called BCM4311 (dual-band) - check
> Broadcom's official brochure on BCM4311 (has a single-band and a
> dual-band version). Same for 0x4319 - it's actually BCM4318 dual-band
> (for example, the BCM94318MPAGH has this ID). The only BCM4312 is
> 0x4315 (also, there exists no "BCM4315", and while BCM4310 might
> indeed be real, it has nothing to do with PCI ID 0x4315). Apparently
> the correlation between PCI ID and chip ID only exists for pure G-PHY
> cards.
>
Check Comment #6 in the thread at
http://forums.opensuse.org/forums/english/get-technical-help-here/wireless/453614-wireless-card-dormant-until-wired-connection-detected.html.
A BCM4312 with ID 14e4:4312.

Larry

  parent reply	other threads:[~2011-02-05 15:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-04 18:56 Table of PCIs, chipsets, etc. on b43 wiki page Rafał Miłecki
2011-02-04 19:37 ` Larry Finger
2011-02-04 20:27   ` Rafał Miłecki
2011-02-05  3:22     ` Larry Finger
2011-02-05  5:56       ` Gábor Stefanik
2011-02-05 10:06         ` Michael Büsch
2011-02-05 11:39         ` Jonas Gorski
2011-02-05 13:38           ` Rafał Miłecki
2011-02-05 16:13             ` Jonas Gorski
2011-02-05 16:24               ` Larry Finger
2011-02-05 16:38                 ` Jonas Gorski
2011-02-05 17:24               ` Rafał Miłecki
2011-02-05 15:56         ` Larry Finger [this message]
2011-02-05 17:35           ` Rafał Miłecki
2011-02-05 17:49             ` Rafał Miłecki
2011-02-05 18:31               ` Rafał Miłecki
2011-02-05 22:32                 ` Rafał Miłecki
2011-02-05 13:35       ` Rafał Miłecki
2011-02-04 20:42 ` 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=4D4D733C.30906@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --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