From: Kalle Valo <kvalo@codeaurora.org>
To: John Crispin <john@phrozen.org>
Cc: Vasanthakumar Thiagarajan <vthiagar@codeaurora.org>,
ath11k@lists.infradead.org,
Shashidhar Lakkavalli <slakkavalli@datto.com>
Subject: Re: [PATCH V2] ath11k: add HE support
Date: Tue, 23 Apr 2019 17:43:13 +0300 [thread overview]
Message-ID: <87wojkye7y.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <2fdd2aa7-758c-55d1-4afb-9afdc8842c98@phrozen.org> (John Crispin's message of "Tue, 16 Apr 2019 19:12:54 +0200")
John Crispin <john@phrozen.org> writes:
> On 16/04/2019 19:07, Vasanthakumar Thiagarajan wrote:
>> On 2019-04-16 19:57, John Crispin wrote:
>>> Add basic HE support to the driver. Things still missing are
>>> * fixed HE mcs/nss rates
>>> * reading the caps from the FW
>>> * 80P80 support
>>> * verify if the mac_caps are correct
>>> * he_operations is not yet propagated to the FW yet
>>>
>>> For HE to work the following hostapd patches need to be used
>>> --> http://lists.infradead.org/pipermail/hostap/2019-April/039962.html
>>>
>>> Signed-off-by: Shashidhar Lakkavalli <slakkavalli@datto.com>
>>> Signed-off-by: John Crispin <john@phrozen.org>
[...]
>> This seems to revert the below commit which fixes target assert.
>>
>> commit e95894e0e5a7b575b681ed7ca550656b7fc72649
>> Author: Sriram R <srirrama@codeaurora.org>
>> Date: Fri Mar 29 14:53:05 2019 +0530
>>
>> ath11k: Fix fw assert in VHT20/VHT40 modes during peer assoc
>>
[...]
> IT does indeed, let me fold a fix into my patch.
I assume you will send a new version and I can drop this?
--
Kalle Valo
_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2019-04-23 14:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 14:27 [PATCH V2] ath11k: add HE support John Crispin
2019-04-16 17:07 ` Vasanthakumar Thiagarajan
2019-04-16 17:09 ` Vasanthakumar Thiagarajan
2019-04-16 17:12 ` John Crispin
2019-04-23 14:43 ` Kalle Valo [this message]
2019-04-23 14:45 ` John Crispin
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=87wojkye7y.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=john@phrozen.org \
--cc=slakkavalli@datto.com \
--cc=vthiagar@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox