All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Sujith Manoharan <sujith@msujith.org>
Cc: Adrian Chadd <adrian@freebsd.org>, ath10k <ath10k@lists.infradead.org>
Subject: Re: Question on beacon-miss handling.
Date: Sun, 06 Jul 2014 21:35:31 -0700	[thread overview]
Message-ID: <53BA2393.8020409@candelatech.com> (raw)
In-Reply-To: <21434.5649.615843.633424@gargle.gargle.HOWL>

On 07/06/2014 08:37 PM, Sujith Manoharan wrote:
> Ben Greear wrote:
>> Maybe the driver should make this 0 instead of 2 then?
>> hw.h:#define TARGET_10X_BMISS_OFFLOAD_MAX_VDEV	2
>> That would save resources in the firmware.
>
> Yes, it would. ath10k doesn't seem to be handling roam
> events too, so maybe that can be set to 0 - not sure if
> there are plans to properly enable and use roaming functionality
> that is already in the firmware.

I have set both to zero when using my firmware, and so far, everything
seems to be working fine.

I am tempted to just compile the roaming and beacon-miss code entirely
out of the firmware to save a bit of memory, but I guess that might
possibly break some driver, so if I do, I will have to add a new
firmware image variant...

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

  reply	other threads:[~2014-07-07  4:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-05 14:16 Question on beacon-miss handling Ben Greear
2014-07-06  2:14 ` Adrian Chadd
2014-07-06  3:39   ` Ben Greear
2014-07-06  4:39     ` Adrian Chadd
2014-07-06  6:01       ` Sujith Manoharan
2014-07-06  7:18         ` Adrian Chadd
2014-07-06  8:54         ` Ben Greear
2014-07-07  3:37           ` Sujith Manoharan
2014-07-07  4:35             ` Ben Greear [this message]
2014-07-07  6:57             ` Bartosz Markowski

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=53BA2393.8020409@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=adrian@freebsd.org \
    --cc=ath10k@lists.infradead.org \
    --cc=sujith@msujith.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 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.