From: Samuel Sieb <samuel@sieb.net>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: BCM43142 doesn't work
Date: Fri, 5 Feb 2016 16:54:37 -0800 [thread overview]
Message-ID: <56B5444D.5070103@sieb.net> (raw)
In-Reply-To: <CACna6rxJFo-rtUP6g3LGn-e3fwF==OkVtBo41iLxKoWY=ETYRA@mail.gmail.com>
On 02/05/2016 04:41 PM, Rafał Miłecki wrote:
> On 6 February 2016 at 00:53, Samuel Sieb <samuel@sieb.net> wrote:
>> However, what happens is:
>> Feb 04 11:55:50 localhost kernel: bcma: bus0: Found chip with id 43142, rev
>> 0x01 and package 0x08
>> Feb 04 11:55:50 localhost kernel: bcma: bus0: Core 0 found: ChipCommon
>> (manuf 0x4BF, id 0x800, rev 0x28, class 0x0)
>> Feb 04 11:55:50 localhost kernel: bcma: bus0: Core 1 found: IEEE 802.11
>> (manuf 0x4BF, id 0x812, rev 0x21, class 0x0)
>> Feb 04 11:55:50 localhost kernel: bcma: bus0: Core 2 found: PCIe (manuf
>> 0x4BF, id 0x820, rev 0x16, class 0x0)
>> Feb 04 11:55:50 localhost kernel: bcma: bus0: Core 3 found: UNKNOWN (manuf
>> 0x43B, id 0x368, rev 0x00, class 0x0)
>> Feb 04 11:55:50 localhost kernel: bcma: bus0: Bus registered
>
> Which means bcma (bus!) supports BCM43132. It detects bus (!) devices
> correctly and registers them. There is no driver supporting wireless
> device found on this chipset.
>
Thank you, that makes sense. So I will need a 3rd party driver after
all. Unfortunately, the wireless chipset is not one of the specs listed
in most stores.
prev parent reply other threads:[~2016-02-06 1:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 23:53 BCM43142 doesn't work Samuel Sieb
2016-02-06 0:41 ` Rafał Miłecki
2016-02-06 0:54 ` Samuel Sieb [this message]
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=56B5444D.5070103@sieb.net \
--to=samuel@sieb.net \
--cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).