From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Bartosz Markowski <bartosz.markowski@tieto.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
ath10k <ath10k@lists.infradead.org>
Subject: Re: [PATCH] ath10k: AP: handle HT station which does not have HT RX MCS
Date: Thu, 13 Feb 2014 17:46:53 +0200 [thread overview]
Message-ID: <874n438176.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CACKGw+Es7YsNHtg+MJE_82Ffm5m9hHu+qo6nZbo-hoOfqCDmOQ@mail.gmail.com> (Bartosz Markowski's message of "Tue, 11 Feb 2014 09:10:56 +0100")
Bartosz Markowski <bartosz.markowski@tieto.com> writes:
> On 11 February 2014 09:06, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
>> Bartosz Markowski <bartosz.markowski@tieto.com> writes:
>>
>>> This is a workaround for HT-enabled STAs which break the spec
>>> and have no HT capabilities RX mask (no HT RX MCS map).
>>>
>>> As per spec, in section 20.3.5 Modulation and coding scheme (MCS),
>>> MCS 0 through 7 are mandatory in 20MHz with 800 ns GI at all STAs.
>>>
>>> Firmware asserts if such situation occurs.
>>>
>>> Signed-off-by: Bartosz Markowski <bartosz.markowski@tieto.com>
>>
>> This conflicted with Marek K's patch "ath10k: Set proper nss value for
>> the peer". Please check that my resolution in ath-next-test is correct:
>>
>> https://github.com/kvalo/ath/commit/d56aa0e779c17f8048a70a9dbd5228b54d9a712e
>
> Looks good.
Thanks, applied.
--
Kalle Valo
prev parent reply other threads:[~2014-02-13 15:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 12:12 [PATCH] ath10k: AP: handle HT station which does not have HT RX MCS Bartosz Markowski
2014-02-11 8:06 ` Kalle Valo
2014-02-11 8:10 ` Bartosz Markowski
2014-02-13 15:46 ` Kalle Valo [this message]
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=874n438176.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=bartosz.markowski@tieto.com \
--cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).