public inbox for b43-dev@lists.infradead.org
 help / color / mirror / Atom feed
From: Arend Van Spriel <arend.vanspriel@broadcom.com>
To: "Rafał Miłecki" <zajec5@gmail.com>,
	"Jan Sobotka" <xSobotkaJ@seznam.cz>,
	"brcm80211 development" <brcm80211-dev-list@broadcom.com>
Cc: b43-dev <b43-dev@lists.infradead.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Planned Support for BCM 43162 [14e4:43ae] rev 02 ?
Date: Mon, 9 May 2016 11:40:51 +0200	[thread overview]
Message-ID: <57305B23.4030101@broadcom.com> (raw)
In-Reply-To: <CACna6rwe9mbcHW+AvtcXvpdvnwZMxkLKzvOLeNp0-XTLB5k6_A@mail.gmail.com>

On 6-5-2016 2:03, Rafa? Mi?ecki wrote:
> On 5 May 2016 at 18:22, Jan Sobotka <xSobotkaJ@seznam.cz> wrote:
>> Great, now it works. Output:
>>
>> root at chobot-lenovo-laptop:/home/chobot# echo "14e4 43ae" > /sys/bus/pci/drivers/bcma-pci-bridge/new_id
>> root at chobot-lenovo-laptop:/home/chobot# dmesg | egrep "bcma|b43"
>> [ 5295.114902] bcma: bus0: Found chip with id 0x4335, rev 0x02 and package 0x01
>> [ 5295.114950] bcma: bus0: Core 0 found: ChipCommon (manuf 0x4BF, id 0x800, rev 0x2E, class 0x0)
>> [ 5295.114974] bcma: bus0: Core 1 found: IEEE 802.11 (manuf 0x4BF, id 0x812, rev 0x2E, class 0x0)
>> [ 5295.115026] bcma: bus0: Core 2 found: ARM CR4 (manuf 0x4BF, id 0x83E, rev 0x04, class 0x0)
>> [ 5295.115073] bcma: bus0: Core 3 found: PCIe Gen2 (manuf 0x4BF, id 0x83C, rev 0x04, class 0x0)
>> [ 5295.115096] bcma: bus0: Core 4 found: USB 2.0 Device (manuf 0x4BF, id 0x81A, rev 0x14, class 0x0)
>> [ 5295.115119] bcma: bus0: Core 5 found: SDIO Device (manuf 0x4BF, id 0x829, rev 0x15, class 0x0)
>> [ 5295.115170] bcma: bus0: Bridge found
>> [ 5295.115221] bcma-pci-bridge: probe of 0000:02:00.0 failed with error -84
> 
> So this is device with BCM4335 chipset which is a FullMAC one AFAIK.
> It may be supported by brcmfmac. There is already support for BCM4335
> in brcmfmac but it was developed for SDIO devices only. I don't think
> we ever met BCM4335 on PCIe device.

It does have an ARM core, but for fullmac we need RAM as well and I
don't see that listed. So I guess it is a 43162 and needs softmac
driver. Also could not find any fullmac firmware for it. The only thing
I found was a hybrid wl driver release for it.

Regards,
Arend

> You may try:
> sudo su
> rmmod bcma
> echo "14e4 43ae" > /sys/bus/pci/drivers/brcmfmac/new_id
> dmesg | grep brcmfmac
> 
> However I think brcmfmac may need some extra changes to support
> BCM4335 on PCIe. Lets also see if Broadcom team can help us with this.
> 

  parent reply	other threads:[~2016-05-09  9:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-30  8:38 Planned Support for BCM 43162 [14e4:43ae] rev 02 ? Jan Sobotka
2016-05-04 18:42 ` Rafał Miłecki
     [not found]   ` <3Fn.2TId.FHuvjLBV4z.1NAsIY@seznam.cz>
2016-05-05 15:37     ` Rafał Miłecki
2016-05-05 16:22       ` Jan Sobotka
2016-05-06  0:03         ` Rafał Miłecki
2016-05-06 11:19           ` Jan Sobotka
2016-05-09  9:40           ` Arend Van Spriel [this message]
2016-05-05 18:11       ` Stuart Longland

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=57305B23.4030101@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --cc=b43-dev@lists.infradead.org \
    --cc=brcm80211-dev-list@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=xSobotkaJ@seznam.cz \
    --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