From: Yeoh Chun-Yeow <yeohchunyeow@gmail.com>
To: Kamran Nishat <kamran.nishat@gmail.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: Dynamic channel Access
Date: Fri, 3 Oct 2014 18:02:02 +0800 [thread overview]
Message-ID: <CAEFj985wmiPwnF7rM1qCcO2K3X2yC_onO0AAMfm=9ytwpChzgg@mail.gmail.com> (raw)
In-Reply-To: <CADxDmp50X2XnBjfk5qJKRH-n=1Cwagmjb_XyD+RJ4AgpPh-kjQ@mail.gmail.com>
As far as I know, dynamic bandwidth operation is based on RTS/CTS
exchange on each 20MHz channel before deciding whether to use 20MHz,
40MHz or 80MHz channel access.
Did you able to capture the RTS or CTS when testing with ath10k?
-----
Chun-Yeow
On Fri, Oct 3, 2014 at 3:58 AM, Kamran Nishat <kamran.nishat@gmail.com> wrote:
> Hi,
> To deal with co-channel interference 802.11ac standard propose Dynamic
> channel access. It means if my AP is configured on 40MHz, but it sense
> only its primary 20Mhz channel is free then it will dynamically
> changes its channel width to 20MHz and starts sending.
>
> Is dynamic channel access implemented in Atheros based 802.11ac chips?
>
>
> Regards
> Kamran
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2014-10-03 10:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 19:58 Dynamic channel Access Kamran Nishat
2014-10-03 10:02 ` Yeoh Chun-Yeow [this message]
2014-10-03 11:52 ` Okhwan Lee
2015-03-25 10:29 ` Jose Antonio Delgado Alfonso
2015-03-25 10:29 ` Jose Antonio Delgado Alfonso
2015-03-25 15:34 ` Jose Antonio Delgado Alfonso
2015-03-25 15:34 ` Jose Antonio Delgado Alfonso
2015-03-25 15:46 ` Ben Greear
2015-03-25 15:46 ` Ben Greear
2015-03-26 6:30 ` Michal Kazior
2015-03-26 6:30 ` Michal Kazior
2015-03-26 9:34 ` Jose Antonio Delgado Alfonso
2015-03-26 9:34 ` Jose Antonio Delgado Alfonso
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='CAEFj985wmiPwnF7rM1qCcO2K3X2yC_onO0AAMfm=9ytwpChzgg@mail.gmail.com' \
--to=yeohchunyeow@gmail.com \
--cc=ath10k@lists.infradead.org \
--cc=kamran.nishat@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.