All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arend van Spriel <arend@broadcom.com>
To: Gucea Doru <gucea.doru@gmail.com>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: Fwd: bcmdhd: Concurrent use of wlan0 and virtual interface in managed mode
Date: Tue, 8 Sep 2015 11:24:40 +0200	[thread overview]
Message-ID: <55EEA958.4060300@broadcom.com> (raw)
In-Reply-To: <CANfLQrbX4GmTbEuvnm+25bwCknB6DR2aQZN=0ZrHqdjCKXYYcw@mail.gmail.com>

On 09/08/2015 09:50 AM, Gucea Doru wrote:
> On Tue, Sep 8, 2015 at 12:01 AM, Arend van Spriel <arend@broadcom.com> wrote:
>
>> The BCM4339 chip does not rely on mac80211. Instead, there is an
>> 802.11 stack running on the device, ie. in firmware. The driver creates the
>> primary interface, ie. wlan0. Additional P2P interfaces are created by
>> wpa_supplicant.
>>
>
> Hm, BCM4339 uses the bcmdhd driver.
> So the bcmdhd driver is not a softmac[1] driver and the the 802.11
> processing is not done in software, right?

Sure it is done in software. Just not on the host, ie. in linux kernel, 
but on the device.

Regards,
Arend

> [1] https://wireless.wiki.kernel.org/en/developers/documentation/glossary#softmac
>
> Regards,
> Doru
>


      reply	other threads:[~2015-09-08  9:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-23 15:15 bcmdhd: Concurrent use of wlan0 and virtual interface in managed mode Gucea Doru
2015-08-24  8:08 ` Arend van Spriel
2015-08-25 21:05   ` Gucea Doru
     [not found]     ` <CAG8K7gRdXqpfA3_HPoaM+ivgxH4eiPRWkD238QwMMbNigYHDBw@mail.gmail.com>
     [not found]       ` <CANfLQraZAkw0Eqt-Mog5t4ZfGFx3xm_8-6nJoJ68Mim18bW3Tg@mail.gmail.com>
2015-09-07 20:41         ` Fwd: " Gucea Doru
2015-09-07 21:01           ` Arend van Spriel
2015-09-08  7:50             ` Gucea Doru
2015-09-08  9:24               ` Arend van Spriel [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=55EEA958.4060300@broadcom.com \
    --to=arend@broadcom.com \
    --cc=gucea.doru@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.