From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Janusz Dziedzic <janusz.dziedzic@tieto.com>
Cc: while1eq1 <while1eq1@gmail.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
markaswift <markaswift@gmail.com>
Subject: Re: [RFC 1/2] ath10k: add implementation for configure max amsdu, ampdu
Date: Thu, 15 May 2014 15:24:54 +0300 [thread overview]
Message-ID: <871tvv9qll.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CALhHN=o_KUjGWN4sEWaGxc3xKmXt2TdmcYsBT9O8rnixcv2q=A@mail.gmail.com> (Janusz Dziedzic's message of "Thu, 15 May 2014 13:35:49 +0200")
Janusz Dziedzic <janusz.dziedzic@tieto.com> writes:
> On 15 May 2014 13:24, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
>
>> Did you somehow check that this command works as it should?
>
> Added WMI_DEBUG_EVENT in FW (_htt_tgt_tx_aggr_cfg):
>
> May 15 12:47:30 dell kernel: [ 6777.355444] ath10k: wmi event debug
> print 'xxx amsdu: 3, ampdu: 64' // This is default :)
> May 15 12:47:30 dell kernel: [ 6777.355477] ath10k: wmi event debug
> print 'xxx data: 0x00014005, 81925'
> May 15 12:47:30 dell kernel: [ 6777.355520] ath10k: wmi event debug
> print 'xxx amsdu: 1, ampdu: 64'
Ok, that's one way to test as well. I was more thinking about using
sniffer or another way to check what's really happening on the air.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2014-05-15 12:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 10:53 [RFC 1/2] ath10k: add implementation for configure max amsdu, ampdu Janusz Dziedzic
2014-05-15 10:53 ` [RFC 2/2] ath10k: setup AMSDU subframes to 1 Janusz Dziedzic
2014-05-15 11:26 ` Kalle Valo
2014-05-15 11:24 ` [RFC 1/2] ath10k: add implementation for configure max amsdu, ampdu Kalle Valo
2014-05-15 11:35 ` Janusz Dziedzic
2014-05-15 12:24 ` Kalle Valo [this message]
2014-07-08 10:46 ` Bartosz Markowski
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=871tvv9qll.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=janusz.dziedzic@tieto.com \
--cc=markaswift@gmail.com \
--cc=while1eq1@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox