Question on beacon-miss handling.

[Adrian Chadd]

Where is it in the firmware again?

The beacon miss stuff is a little .. odd. Mostly because there's only
one (and maybe two) timers for it and they're a pain in the ass to
configure correctly. Having it scale (correctly) to more than two
vdevs may be a little challenging.



-a


On 5 July 2014 07:16, Ben Greear <greearb at candelatech.com> wrote:
> While poking around in the firmware, I notice that ath10k
> driver only requests a few vdevs to be supported by
> the beacon-miss firmware logic, though the driver
> supposedly supports more vdevs than that...
>
> Any idea how this is supposed to work with more vdevs
> than bmiss_offload_max_vdev?
>
> Maybe it is best to just disable beacon-miss logic in
> firmware entirely and let the driver/host handle it?
>
> Thanks,
> Ben
>
> --
> Ben Greear <greearb at candelatech.com>
> Candela Technologies Inc  http://www.candelatech.com
>
>
> _______________________________________________
> ath10k mailing list
> ath10k at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k