From: Larry Finger <Larry.Finger@lwfinger.net>
To: Jonas Gorski <jonas.gorski@gmail.com>
Cc: "Gábor Stefanik" <netrolller.3d@gmail.com>,
"David Woodhouse" <dwmw2@infradead.org>,
"Michael Büsch" <mb@bu3sch.de>,
"John Linville" <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
b43-dev <b43-dev@lists.infradead.org>
Subject: [PATCH] ssb: Ignore dangling ethernet cores on wireless devices
Date: Wed, 09 Nov 2011 07:53:09 -0600 [thread overview]
Message-ID: <4EBA85C5.2000606@lwfinger.net> (raw)
In-Reply-To: <CAOiHx=kVL3dewGR=utxfKMVmJ4zEbzXmSXEnCH_8ypwkQ5WhmQ@mail.gmail.com>
On 11/09/2011 06:16 AM, Jonas Gorski wrote:
> On 9 November 2011 12:51, G?bor Stefanik<netrolller.3d@gmail.com> wrote:
>> On Wed, Nov 9, 2011 at 12:50 PM, G?bor Stefanik<netrolller.3d@gmail.com> wrote:
>>> On Wed, Nov 9, 2011 at 12:14 PM, David Woodhouse<dwmw2@infradead.org> wrote:
>>>> On Fri, 2011-01-07 at 19:48 +0100, Michael B?sch wrote:
>>>>>
>>>>> + case SSB_DEV_ETHERNET:
>>>>> + if (bus->bustype == SSB_BUSTYPE_PCI) {
>>>>> + if (bus->host_pci->vendor == PCI_VENDOR_ID_BROADCOM&&
>>>>> + (bus->host_pci->device& 0xFF00) == 0x4300) {
>>>>> + /* This is a dangling ethernet core on a
>>>>> + * wireless device. Ignore it. */
>>>>> + continue;
>>>>> + }
>>>>> + }
>>>>> + break;
>>>>
>>>> Do you also need to check for (bus->host_pci->device / 1000) == 43?
>>>> Or do the chips with 5-digit 'decimal' IDs not have the Ethernet cores?
>>>>
>>>> Would it be better to invert the test and check for != 0x4400?
>>>
>>> I do not know of any Broadcom wireless device with a decimal PCI ID
>>> (as opposed to a decimal Chip ID).
>>
>> Edit: However, 0x4700 should also be checked, as some BCM43xx chips
>> use 0x47xx PCI IDs.
>
> As far as I can tell from this snippet (I'm missing the original
> message), this code is SSB, and the only 0x47xx I know of is the
> BCM4313, and that's a BCMA card. So this doesn't apply here.
>
> Same for the five digit Chip IDs (which might leak into the PCI ID, if
> the card has no SPROM), AFAIK these are also BCMA exclusive.
The only known card with this problem is the BCM4303, with PCI IDs 14e4:4301. My
suspicion is that Broadcom created a chip that could be used for wireless or
wired depending on which core was connected. Thus, it is an artifact of the
early days. One can clean up the code as much as you want, but I do not believe
any other chips are involved.
Larry
next prev parent reply other threads:[~2011-11-09 13:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 18:48 [PATCH] ssb: Ignore dangling ethernet cores on wireless devices Michael Büsch
2011-11-09 11:14 ` David Woodhouse
2011-11-09 11:50 ` Gábor Stefanik
2011-11-09 11:51 ` Gábor Stefanik
2011-11-09 12:16 ` Jonas Gorski
2011-11-09 13:53 ` Larry Finger [this message]
2011-11-09 15:46 ` 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=4EBA85C5.2000606@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=dwmw2@infradead.org \
--cc=jonas.gorski@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=netrolller.3d@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).