From: "Franky Lin" <frankyl@broadcom.com>
To: "Kiran Karra" <kiran.karra@gmail.com>
Cc: "linux wireless" <linux-wireless@vger.kernel.org>
Subject: Re: BCM4329 chipset -- open80211s
Date: Mon, 2 Apr 2012 14:40:24 -0700 [thread overview]
Message-ID: <4F7A1CC8.4020006@broadcom.com> (raw)
In-Reply-To: <CAAaUcVyTk7zRs4XACXa_Sw_n6qgcF_7b2Mf_dNhEMsiwgGa_QA@mail.gmail.com>
Hi Kiran,
On 03/31/2012 12:18 PM, Kiran Karra wrote:
> Hi All,
> I would like to know if I can use open80211s with the BCM4329 chipset?
> From the research I've done, the BCM4329 is a FullMAC device, not a
> SoftMAC device. The open-source linux driver that can work with the
> BCM4329 chipset is the brcmfmac. Therefore, it does not use the
> mac80211 framework. The brcmfmac driver is integrated with cfg80211.
> Since open80211s is based off the mac80211 stack, does this mean
> open80211s can never be used with brcmfmac? Is it possible to
> interface the open80211s code directly with cfg80211? Would the
> cfg80211 api provide all the necessary callbacks in order to acheive
> mesh functionality? If this is possible, does anyone have an idea of
> how much time this effort would require?
The current implementation of support for 4329 is using the chipset to
handle all 80211 stuff. The packet passed between host and the dongle
chipset is Ethernet packet (802.3). Currently we don't have any plan to
add mesh mode support in firmware.
Thanks,
-Franky
prev parent reply other threads:[~2012-04-02 21:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-31 19:18 BCM4329 chipset -- open80211s Kiran Karra
2012-04-02 21:40 ` Franky Lin [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=4F7A1CC8.4020006@broadcom.com \
--to=frankyl@broadcom.com \
--cc=kiran.karra@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).