From: Ben Greear <greearb@candelatech.com>
To: Yeoh Chun-Yeow <yeohchunyeow@gmail.com>
Cc: ath10k <ath10k@lists.infradead.org>
Subject: Re: Any idea why we cannot disable /b rates?
Date: Wed, 25 Feb 2015 15:25:37 -0800 [thread overview]
Message-ID: <54EE59F1.20805@candelatech.com> (raw)
In-Reply-To: <CAEFj9871qXhsVn1XmhGs6qSpcVWVjk+B-CMp1zJzf5uqyzKCUQ@mail.gmail.com>
On 02/25/2015 02:30 AM, Yeoh Chun-Yeow wrote:
> On Wed, Feb 25, 2015 at 1:02 PM, Ben Greear <greearb@candelatech.com> wrote:
>>
>>
>> On 02/24/2015 06:45 PM, Yeoh Chun-Yeow wrote:
>>>
>>> On Wed, Feb 25, 2015 at 3:44 AM, Ben Greear <greearb@candelatech.com>
>>> wrote:
>>>>
>>>> Ok, so I found the problem. Appears that the firmware uses two different
>>>> fixed rate-ctrl settings, one for non-data (bcast, mgt-frames, etc) and
>>>> another
>>>> for data frames. The non-data one was not being set when user configured
>>>> fixed rates, so beacons went out at 1Mbps.
>>>>
>>>> I updated CT firmware (beta-14) to set both data and non-data to the same
>>>> value when the driver specifies the rates... Seems to work...any idea
>>>> if this is a bad idea in practice?
>>>
>>>
>>> Rate control is applicable to unicast frame whether it is
>>> management/data. Broadcast/Multicast rate is required for
>>> management/data (usually the lowest transmission rate 5GHz is 6Mbps).
>>>
>>> So it is more sensible if we can configure the broadcast/multicast
>>> rate and also disable the rate control for unicast frame by using
>>> fixed rate.
>>
>>
>> User-space API doesn't give the ability to set different fixed rates for
>> different packet types, as far as I know.
>>
>> So, the current firmware just ignores the fixed rate for management and
>> broadcast
>> frames.
>>
>> My firmware change makes the fixed rate apply equally to all types of
>> frames.
>>
>> Should I make my change optional for mgt/bcast , or should it always set
>> mgt/bcast rates to the
>> same fixed rates as data packets use?
>
> In iw, we have the following:
> dev <devname> set mcast_rate <rate in Mbps>
> dev <devname> set bitrates [legacy-<2.4|5> <legacy rate in Mbps>*]
> [mcs-<2.4|5> <MCS index>*]
>
> mcast-rate should be something set for broadcast/multicast frame
> including the management and data frame. This allows us to have in
> example beacon frame to be transmitted with higher rate from 1Mbps at
> 2.4GHz and 6Mbps at 5GHz.
Thanks...I'll try to figure out how to work this into my firmware. But, it will
require driver changes specific to my firmware as far as I can tell,
so it will never make it upstream...
Thanks,
Ben
--
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:[~2015-02-25 23:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 17:43 Any idea why we cannot disable /b rates? Ben Greear
2015-02-24 19:44 ` Ben Greear
2015-02-25 2:45 ` Yeoh Chun-Yeow
2015-02-25 5:02 ` Ben Greear
2015-02-25 10:30 ` Yeoh Chun-Yeow
2015-02-25 23:25 ` Ben Greear [this message]
2015-03-10 23:59 ` 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=54EE59F1.20805@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=yeohchunyeow@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