All of lore.kernel.org
 help / color / mirror / Atom feed
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: Tue, 24 Feb 2015 21:02:50 -0800	[thread overview]
Message-ID: <54ED577A.8030003@candelatech.com> (raw)
In-Reply-To: <CAEFj986Z80bBioVC4Ao77ZskGGdZQA5WgdBgEzVoY4f8OBAJRQ@mail.gmail.com>



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?

Thanks,
Ben

>
> ---
> Chun-Yeow
>

-- 
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

  reply	other threads:[~2015-02-25  5:03 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 [this message]
2015-02-25 10:30       ` Yeoh Chun-Yeow
2015-02-25 23:25         ` Ben Greear
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=54ED577A.8030003@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 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.