From: Ben Greear <greearb@candelatech.com>
To: Yeoh Chun-Yeow <yeohchunyeow@gmail.com>
Cc: ath10k <ath10k@lists.infradead.org>
Subject: Re: ath10k and 802.11s support?
Date: Wed, 11 Mar 2015 16:35:59 -0700 [thread overview]
Message-ID: <5500D15F.7070009@candelatech.com> (raw)
In-Reply-To: <CAEFj9848iE7Sy5+g6Bvqe+EiExx=xgyxJ12ZeyyXWCAB8btFKA@mail.gmail.com>
On 03/11/2015 04:26 PM, Yeoh Chun-Yeow wrote:
> Hi, Ben
>
> I have forwarded my email two years ago related to fw supporting 802.11s.
Thanks for the info.
I'll look into this a bit more when I finish some other pending work.
Thanks,
Ben
>
> -----
> Chun-Yeow
>
> ---------- Forwarded message ----------
> From: Yeoh Chun-Yeow <yeohchunyeow@gmail.com>
> Date: Mon, Mar 3, 2014 at 10:21 AM
> Subject: Mesh Support in ath10k
> To: Kalle Valo <kvalo@qca.qualcomm.com>
>
>
> Hi, Kalle Valo
>
> Currently, I am investigating the possibility of putting mesh or o11s
> support in ath10k by utilizing the adhoc mode available in ath10k.
>
> I have compiled the following issues that need to address to enable
> the mesh support:
>
> 1. Beacon Filtering
> Currenly, adhoc mode only allowed the beacon with the BSSID set by the
> ath10k_wmi_vdev_up to pass to mac80211. Continuous background scanning
> may not be good since we need to receive the beacon for
> synchronization purpose. FYI, mesh uses the BSSID similar to its own
> vif mac addr.
>
> 2. QoS Data Frame for broadcast data frame
> Currently, only non-QoS data allowed for broadcast frame as I observed.
>
> 3. QoS Control Field, no stripped off
> We need to set the bit-8 of QoS control field to indicate the presence
> of mesh control field.
>
> I believe that we need to have some changes on the Firmware to make this work.
>
> Please kindly let me know is that possible to make arrangement of FW changes.
>
> Thanks
>
> Regards,
> Chun-Yeow
>
>
> On Tue, Mar 10, 2015 at 5:25 PM, Ben Greear <greearb@candelatech.com> wrote:
>> Anyone know what it would take to get ath10k to support
>> 802.11s?
>>
>> As you know, I'm not above modifying ath10k firmware, but
>> I also do not have a huge amount of time to put into this,
>> so if changes needed are extensive, then probably I cannot
>> do it now...
>>
>> Thanks,
>> Ben
>>
>> --
>> Ben Greear <greearb@candelatech.com>
>> Candela Technologies Inc http://www.candelatech.com
>>
>>
>> _______________________________________________
>> ath10k mailing list
>> ath10k@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/ath10k
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2015-03-11 23:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 17:25 ath10k and 802.11s support? Ben Greear
2015-03-11 23:26 ` Yeoh Chun-Yeow
2015-03-11 23:35 ` Ben Greear [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=5500D15F.7070009@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=yeohchunyeow@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 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.