linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arend van Spriel <arend@broadcom.com>
To: Gucea Doru <gucea.doru@gmail.com>, <linux-wireless@vger.kernel.org>
Subject: Re: Fwd: bcmdhd: Concurrent use of wlan0 and virtual interface in managed mode
Date: Mon, 7 Sep 2015 23:01:26 +0200	[thread overview]
Message-ID: <55EDFB26.8000708@broadcom.com> (raw)
In-Reply-To: <CANfLQrYVq_eMa-CLJhqVthbm_h7yLBhZN5nm0_f70eEob+rUdw@mail.gmail.com>

On 09/07/2015 10:41 PM, Gucea Doru wrote:
> Hello,
>
> Thanks for helping me. I have some more questions related to parallel
> usage of p2p and STA (station) interface.
>
> I use a Nexus 5 device which has a BCM4339 [1] chip and it seems that
> it's possible to transfer data in parallel using two connections: one
> based on Wi-Fi direct(p2p, 2.4Ghz) and the other one based on a
> connection to AP (wlan0, 5Ghz).
>
> This is done by _time-sharing_ the wireless interface radio? From my
> understanding the mac80211 layer have support for multiple virtual
> interfaces and the switching between this interfaces is done inside
> mac80211. Does the driver creates multiple virtual interfaces (one for
> p2p and one for the connection to the AP) and the mac80211 manages the
> time-sharing between them?

Nope. 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.

> I am interested in understanding the code that decides how much the
> radio should stay on a specific channel. I would be really grateful if
> you could give me some details about the architecture.

That code runs in firmware on the device and is proprietary. So I can 
not disclose any details.

Regards,
Arend

> [1] http://www.broadcom.com/press/release.php?id=s766879
>
> Thanks,
> Doru
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


  reply	other threads:[~2015-09-07 21:01 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 [this message]
2015-09-08  7:50             ` Gucea Doru
2015-09-08  9:24               ` 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=55EDFB26.8000708@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 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).