From: "Valo, Kalle" <kvalo@qca.qualcomm.com>
To: Zach Sherin <zach@netblazr.com>
Cc: Yeoh Chun-Yeow <yeohchunyeow@gmail.com>,
Bob Copeland <me@bobcopeland.com>,
Raj Joshi <rajjoshi@comp.nus.edu.sg>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: 802.11s channel width settings?
Date: Fri, 6 May 2016 16:32:45 +0000 [thread overview]
Message-ID: <87mvo3no44.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAOiRWuXhVWGRvt1_4p0KVg=DmAey=trjK2Fx7GtXtFUrnS23GA@mail.gmail.com> (Zach Sherin's message of "Fri, 6 May 2016 12:09:56 -0400")
Zach Sherin <zach@netblazr.com> writes:
> Thanks! I mostly am interested in knowing the modulation just to keep
> track of my theoretical maximum throughput for monitoring. The Rx rate
> was changing correctly now, which is great. I know the Tx rate is
> totally unreported, but the Rx is all I need. Thanks again for all the
> assistance, I think I have everything I need.
IIRC you should actually see the TX rate from fw_stats debugfs file.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2016-05-06 16:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 18:51 802.11s channel width settings? Zach Sherin
2016-05-05 20:53 ` Zach Sherin
2016-05-06 1:32 ` Bob Copeland
2016-05-06 14:28 ` Zach Sherin
2016-05-06 15:28 ` Yeoh Chun-Yeow
[not found] ` <CA+uUJGvb6gtFK9xHitL36VHK25BW1jcBVkv__GUid_K7sVraHw@mail.gmail.com>
2016-05-06 15:56 ` Yeoh Chun-Yeow
2016-05-06 16:09 ` Zach Sherin
2016-05-06 16:32 ` Valo, Kalle [this message]
2016-05-06 16:44 ` Yeoh Chun-Yeow
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=87mvo3no44.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=me@bobcopeland.com \
--cc=rajjoshi@comp.nus.edu.sg \
--cc=yeohchunyeow@gmail.com \
--cc=zach@netblazr.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.