On 5/20/19 12:25 PM, Adrian Chadd wrote:
On Mon, 20 May 2019 at 09:59, Sebastian Gottschall
wrote:
the curious thing is still that the fallback code applies only for 2.4
ghz so it would never have affected 802.11ac
Hm, does RC fall back to 11na or 11a rates when doing 11ac? (in 5G
mode.) It
On Mon, 20 May 2019 at 09:59, Sebastian Gottschall
wrote:
> the curious thing is still that the fallback code applies only for 2.4
> ghz so it would never have affected 802.11ac
Hm, does RC fall back to 11na or 11a rates when doing 11ac? (in 5G
mode.) It's good to know fixing that would fix it
Am 17.05.2019 um 18:00 schrieb Ben Greear:
On 5/17/19 8:47 AM, Adrian Chadd wrote:
On Fri, 17 May 2019 at 08:06, Sebastian Gottschall
wrote:
personally i think going back to basic rates like 2 mbit makes no sense
anyway. its that dead slow that a connection must break and has to be
broken i
Am 17.05.2019 um 17:47 schrieb Adrian Chadd:
On Fri, 17 May 2019 at 08:06, Sebastian Gottschall
wrote:
personally i think going back to basic rates like 2 mbit makes no sense
anyway. its that dead slow that a connection must break and has to be
broken if this doesnt work.
still a shame that
On 2019-05-15 02:57, Johannes Berg wrote:
On Tue, 2019-05-14 at 11:54 -0700, Ben Greear wrote:
Here is the info I have in my commit that changed this to
WARN_ON_ONCE.
I never posted it because I had to hack ath10k to get to this state,
so maybe
this is not a valid case to debug.
Maybe Yibo
