From: Ben Greear <greearb@candelatech.com> To: Johannes Berg <johannes@sipsolutions.net>, Oleksij Rempel <linux@rempel-privat.de>, "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>, ath10k <ath10k@lists.infradead.org>, kirtika@google.com Subject: Re: Setting single rate in ath10k broken by "reject/clear user rate mask if not usable" Date: Mon, 13 Nov 2017 09:05:28 -0800 [thread overview] Message-ID: <d2caa97d-50b0-94bd-9ee1-349e44cee1c8@candelatech.com> (raw) In-Reply-To: <1510567783.30497.33.camel@sipsolutions.net> On 11/13/2017 02:09 AM, Johannes Berg wrote: > On Fri, 2017-10-27 at 13:41 -0700, Ben Greear wrote: > >> ath10k ignores the tx rateset pretty much entirely when sending management >> frames, so even if you set the tx rateset to have only VHT MCS 8, >> management frames are still sent with legacy ratesets. > > So that's a driver bug. The firmware gives the ability to set a single fixed rate for multicast, and another for management frames. It is possibly to set the tx-data frame rate to another fixed rate, or to a more normal rateset. But, you do not have full control over setting tx-data rates (no way to tell stock firmware to use 6Mbps /g rate and mcs 8 (only), for instance). The multicast and mgt frame API is not hooked up in the stock driver as far as I know. But even if they were, I don't see a good way to make this fit with the mac80211 txrate setting framework. What is the suggested approach to propagate a rateset set with 'iw' to a firmware with these limitations? For the Intel firmware NICs, how do they set management and bcast tx rates? >> My end goal about this part is to be able to configure a single tx rate >> and have that be allowed again, at least with ath10k. >> >> Maybe a new flag for drivers like ath10k that at least somewhat ignore >> the tx-rateset for management frames, and this flag would allow us to >> bypass the cannot-set-single-rate check? > > What? No, I'm not going to put a driver bug into the API like that! Thanks for the constructive feedback. --Ben > > johannes > -- Ben Greear <greearb@candelatech.com> Candela Technologies Inc http://www.candelatech.com
WARNING: multiple messages have this Message-ID (diff)
From: Ben Greear <greearb@candelatech.com> To: Johannes Berg <johannes@sipsolutions.net>, Oleksij Rempel <linux@rempel-privat.de>, "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>, ath10k <ath10k@lists.infradead.org>, kirtika@google.com Subject: Re: Setting single rate in ath10k broken by "reject/clear user rate mask if not usable" Date: Mon, 13 Nov 2017 09:05:28 -0800 [thread overview] Message-ID: <d2caa97d-50b0-94bd-9ee1-349e44cee1c8@candelatech.com> (raw) In-Reply-To: <1510567783.30497.33.camel@sipsolutions.net> On 11/13/2017 02:09 AM, Johannes Berg wrote: > On Fri, 2017-10-27 at 13:41 -0700, Ben Greear wrote: > >> ath10k ignores the tx rateset pretty much entirely when sending management >> frames, so even if you set the tx rateset to have only VHT MCS 8, >> management frames are still sent with legacy ratesets. > > So that's a driver bug. The firmware gives the ability to set a single fixed rate for multicast, and another for management frames. It is possibly to set the tx-data frame rate to another fixed rate, or to a more normal rateset. But, you do not have full control over setting tx-data rates (no way to tell stock firmware to use 6Mbps /g rate and mcs 8 (only), for instance). The multicast and mgt frame API is not hooked up in the stock driver as far as I know. But even if they were, I don't see a good way to make this fit with the mac80211 txrate setting framework. What is the suggested approach to propagate a rateset set with 'iw' to a firmware with these limitations? For the Intel firmware NICs, how do they set management and bcast tx rates? >> My end goal about this part is to be able to configure a single tx rate >> and have that be allowed again, at least with ath10k. >> >> Maybe a new flag for drivers like ath10k that at least somewhat ignore >> the tx-rateset for management frames, and this flag would allow us to >> bypass the cannot-set-single-rate check? > > What? No, I'm not going to put a driver bug into the API like that! Thanks for the constructive feedback. --Ben > > johannes > -- 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
next prev parent reply other threads:[~2017-11-13 17:05 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-10-10 20:54 Setting single rate in ath10k broken by "reject/clear user rate mask if not usable" Ben Greear 2017-10-10 20:54 ` Ben Greear 2017-10-11 4:37 ` Not able to set single rate in ath10k (backports-4.14-rc2-1) KAVITA MATHUR 2017-10-11 8:02 ` Setting single rate in ath10k broken by "reject/clear user rate mask if not usable" Johannes Berg 2017-10-11 8:02 ` Johannes Berg 2017-10-11 8:07 ` Johannes Berg 2017-10-11 8:07 ` Johannes Berg 2017-10-11 14:51 ` Ben Greear 2017-10-11 14:51 ` Ben Greear 2017-10-18 7:33 ` Johannes Berg 2017-10-18 7:33 ` Johannes Berg 2017-10-18 14:50 ` Ben Greear 2017-10-18 14:50 ` Ben Greear 2017-10-18 17:56 ` Oleksij Rempel 2017-10-18 17:56 ` Oleksij Rempel 2017-10-18 20:34 ` Johannes Berg 2017-10-18 20:34 ` Johannes Berg 2017-10-18 20:51 ` Ben Greear 2017-10-18 20:51 ` Ben Greear 2017-10-18 21:02 ` Johannes Berg 2017-10-18 21:02 ` Johannes Berg 2017-10-18 21:30 ` Ben Greear 2017-10-18 21:30 ` Ben Greear 2017-10-25 15:17 ` Johannes Berg 2017-10-25 15:17 ` Johannes Berg 2017-10-25 16:13 ` Ben Greear 2017-10-25 16:13 ` Ben Greear 2017-10-27 20:15 ` Johannes Berg 2017-10-27 20:15 ` Johannes Berg 2017-10-27 20:41 ` Ben Greear 2017-10-27 20:41 ` Ben Greear 2017-11-13 10:09 ` Johannes Berg 2017-11-13 10:09 ` Johannes Berg 2017-11-13 17:05 ` Ben Greear [this message] 2017-11-13 17:05 ` Ben Greear
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=d2caa97d-50b0-94bd-9ee1-349e44cee1c8@candelatech.com \ --to=greearb@candelatech.com \ --cc=ath10k@lists.infradead.org \ --cc=johannes@sipsolutions.net \ --cc=kirtika@google.com \ --cc=linux-wireless@vger.kernel.org \ --cc=linux@rempel-privat.de \ /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: linkBe 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.