ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "KAVITA MATHUR" <kavitam@cdot.in>
To: Ben Greear <greearb@candelatech.com>,
	ath10k@lists.infradead.org, backports@vger.kernel.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: fixed bit rate 9Mbps set as 24Mbps in g mode(legacy)
Date: Wed, 28 Feb 2018 09:33:16 +0530	[thread overview]
Message-ID: <20180228035700.M28643@cdot.in> (raw)
In-Reply-To: <3047f184-d600-7be7-52bc-2ed4cee37ffe@candelatech.com>




On Tue, 27 Feb 2018 08:41:50 -0800, Ben Greear wrote
> On 02/27/2018 12:49 AM, KAVITA MATHUR wrote:
> > Hi,
> >
> > I have configured AP in g mode and tested legacy rates.All basic rates and supported
> > rates(1,2,5.5,11,6,9,12,18,24,36,48,54) are set except 9Mbps.
> >
> > When fixed bit rate 9Mbps is set, it gets set as 24 Mbps. This issue has been observed
> > in backports-4.4.2-1 as well as latest git version of ath10k driver.
> >
> >
> > Is anybody aware of this issue? How can I fix this rate 9Mbps?
> 
> You should specify which firmware/chipset you are using, since this might
> easily be a firmware issue.


Chipset : QCA988x
ath10k version : git 16 oct 2017(v4.14-rc2-1-24-gc6db471)
firmware version : firmware-5.bin_10.2.4.70.66
Kernel version : 3.12 

> And, how are you determining that 'it gets set to 24Mbps'.  Is that the 
> encoding you see in a wifi sniff, or is the driver being set to 24Mbps 
> improperly when you use iw (or whatever) to try configuring the rate?

I have used command "iw wlan0 station dump" to see set data rate as well as I have
sniffer. Measured data throughput is also as per 24Mbps.



> Recent upstream mac80211 has broken the ability to set a single tx rate as 
> well, last I checked.

Other rates are set properly except 9Mbps.By default it sets as 6Mbps, when data
transfer starts, then it set to the mentioned fixed data rate.

Thanks & Regards,
Kavita
> Thanks,
> Ben
> 
> >
> >
> > Thanks & Regards,
> > Kavita
> >
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe backports" in
> >
> 
> -- 
> Ben Greear <greearb@candelatech.com>
> Candela Technologies Inc  http://www.candelatech.com


Thanks & Regards,
कविता माथुर Kavita Mathur 
वरिष्ठ अनुसंधान अभियंता  Senior Research Engineer 
सी-डॉट                      C-DOT
इलैक्ट्रॉनिक्स सिटी फेज़ I         Electronics City Phase I
होसूर रोड, बेंगलूरु               Hosur Road, Bengaluru – 560100
फोन  Ph 080-28529896
Disclaimer:
----------
This email and any files transmitted with it


_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2018-02-28  4:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-26  6:16 [PATCH] Revert "ath10k: send (re)assoc peer command when NSS changed" Karthikeyan Periyasamy
2018-02-26  8:45 ` Adrian Chadd
2018-02-26 10:41   ` periyasa
2018-02-26 15:56 ` Ben Greear
2018-02-26 17:06   ` periyasa
2018-02-26 19:21     ` Adrian Chadd
2018-02-27  4:00       ` periyasa
2018-02-26 19:17 ` Peter Oh
2018-02-27  8:49 ` fixed bit rate 9Mbps set as 24Mbps in g mode(legacy) KAVITA MATHUR
2018-02-27 16:41   ` Ben Greear
2018-02-28  4:03     ` KAVITA MATHUR [this message]
2018-02-28 19:43       ` 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=20180228035700.M28643@cdot.in \
    --to=kavitam@cdot.in \
    --cc=ath10k@lists.infradead.org \
    --cc=backports@vger.kernel.org \
    --cc=greearb@candelatech.com \
    --cc=linux-wireless@vger.kernel.org \
    /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