From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [PATCH] ath10k: implement more versatile set_bitrate_mask
Date: Tue, 21 Apr 2015 18:04:15 +0300 [thread overview]
Message-ID: <87vbgpzfo0.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CA+BoTQnNNKF7riAgcVj1LupABAGodm751jxOUuZgam8u=wthUA@mail.gmail.com> (Michal Kazior's message of "Fri, 17 Apr 2015 09:30:51 +0200")
Michal Kazior <michal.kazior@tieto.com> writes:
>> To reduce support questions from the users it would be nice to give few
>> good examples how to use this with iw. And also it makes it easier to
>> test the patch. If you could send something I can add it to the commit
>> log.
>
> Should work:
>
> iw wlan0 set bitrates legacy 1 6 12 ht-mcs 1 2 3
> iw wlan0 set bitrates legacy-5 mcs-5 7 8 9
> iw wlan0 set bitrates legacy-5 24 ht-mcs-5 vht-mcs-5 1:0-9
>
> Won't work:
>
> iw wlan0 set bitrates legacy-5 ht-mcs-5 vht-mcs-5 1:0-5
> iw wlan0 set bitrates vht-mcs-5 2:7-9
>
> (note the invalid VHT MCS ranges)
Thanks, I added these to the commit log.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ath10k: implement more versatile set_bitrate_mask
Date: Tue, 21 Apr 2015 18:04:15 +0300 [thread overview]
Message-ID: <87vbgpzfo0.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CA+BoTQnNNKF7riAgcVj1LupABAGodm751jxOUuZgam8u=wthUA@mail.gmail.com> (Michal Kazior's message of "Fri, 17 Apr 2015 09:30:51 +0200")
Michal Kazior <michal.kazior@tieto.com> writes:
>> To reduce support questions from the users it would be nice to give few
>> good examples how to use this with iw. And also it makes it easier to
>> test the patch. If you could send something I can add it to the commit
>> log.
>
> Should work:
>
> iw wlan0 set bitrates legacy 1 6 12 ht-mcs 1 2 3
> iw wlan0 set bitrates legacy-5 mcs-5 7 8 9
> iw wlan0 set bitrates legacy-5 24 ht-mcs-5 vht-mcs-5 1:0-9
>
> Won't work:
>
> iw wlan0 set bitrates legacy-5 ht-mcs-5 vht-mcs-5 1:0-5
> iw wlan0 set bitrates vht-mcs-5 2:7-9
>
> (note the invalid VHT MCS ranges)
Thanks, I added these to the commit log.
--
Kalle Valo
next prev parent reply other threads:[~2015-04-21 15:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 13:32 [PATCH] ath10k: implement more versatile set_bitrate_mask Michal Kazior
2015-04-10 13:32 ` Michal Kazior
2015-04-17 7:06 ` Kalle Valo
2015-04-17 7:06 ` Kalle Valo
2015-04-17 7:30 ` Michal Kazior
2015-04-17 7:30 ` Michal Kazior
2015-04-21 15:04 ` Kalle Valo [this message]
2015-04-21 15:04 ` Kalle Valo
2015-04-22 6:27 ` Kalle Valo
2015-04-22 6:27 ` Kalle Valo
2015-04-22 7:33 ` Michal Kazior
2015-04-22 7:33 ` Michal Kazior
2015-04-24 14:31 ` Kalle Valo
2015-04-24 14:31 ` Kalle Valo
2015-04-27 8:50 ` Kalle Valo
2015-04-27 8:50 ` Kalle Valo
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=87vbgpzfo0.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.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.