public inbox for b43-dev@lists.infradead.org
 help / color / mirror / Atom feed
From: Arend van Spriel <arend@broadcom.com>
To: b43-dev@lists.infradead.org
Subject: Broadcom 4330 and Intel Edison
Date: Thu, 5 Nov 2015 12:22:31 +0100	[thread overview]
Message-ID: <563B3BF7.9010408@broadcom.com> (raw)
In-Reply-To: <563A85BF.7050900@hauke-m.de>

On 11/04/2015 11:25 PM, Hauke Mehrtens wrote:
> On 11/04/2015 07:04 AM, Rafa? Mi?ecki wrote:
>> On 3 November 2015 at 23:00, Domeika, Max J <max.j.domeika@intel.com> wrote:
>>> We are trying to get the Intel Edison which uses the Broadcom 4330 to act as both an AP and client at the same time. Iw list seems to suggest it is possible, but we haven?t figured out the correct process to do so or even if the underlying kernel will allow it (using ubilinux 3.10.17 and the driver is bcm43340-mod-1.141-r47.
>>
>> It's some out-of-tree driver and BCM4330 is most likely a FullMAC
>> chip. It's not really related to b43 driver which support SoftMAC
>> devices.
>>
> bcm4330 is supported by the Linux upstream driver brcmfmac [0], you
> could take brcmfmac from backports [1] and try if that driver supports
> your requirements. BCM43340 seams to be a different chip, but it is also
> supported by brcmfmac.

Doing AP+STA requires MBSS support, which 4330 firmware does not. At 
least not the one in linux-firmware repo.

Regards,
Arend

  reply	other threads:[~2015-11-05 11:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-03 22:00 Broadcom 4330 and Intel Edison Domeika, Max J
2015-11-04  6:04 ` Rafał Miłecki
2015-11-04 22:25   ` Hauke Mehrtens
2015-11-05 11:22     ` Arend van Spriel [this message]
2015-11-12 20:17       ` Domeika, Max J
2015-11-12 20:24         ` Domeika, Max J
2015-11-13  8:31           ` Arend van Spriel

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=563B3BF7.9010408@broadcom.com \
    --to=arend@broadcom.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