From: "Valo, Kalle" <kvalo@qca.qualcomm.com>
To: Sebastian Gottschall <s.gottschall@dd-wrt.com>
Cc: Ben Greear <greearb@candelatech.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: 9984 VHT
Date: Fri, 10 Feb 2017 06:50:56 +0000 [thread overview]
Message-ID: <87y3xeilor.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <2c29c0e6-a207-9d40-fa8d-dc5e54f9c468@dd-wrt.com> (Sebastian Gottschall's message of "Tue, 7 Feb 2017 13:39:28 +0100")
Sebastian Gottschall <s.gottschall@dd-wrt.com> writes:
> Am 07.02.2017 um 13:14 schrieb Valo, Kalle:
>> Ben Greear <greearb@candelatech.com> writes:
>>
>>> On 02/02/2017 10:42 AM, Sebastian Gottschall wrote:
>>>> Am 02.02.2017 um 19:24 schrieb Ben Greear:
>>>>
>>>>> I hacked ath10k to enable radar detection on 160Mhz bandwidths. Now hostapd
>>>>> starts.
>>>>>
>>>>> I can reproduce the FW failure. It is because FW 3.3-25 release
>>>>> started asserting
>>>>> if the freq2 was zero in VHT160 mode. It seems to use both freq1
>>>>> and freq2, and not
>>>>> how the driver or linux seems to normally use them.
>>>> its even worse. starting from 3.3 it uses freq2 instead of freq1.
>>>> but i made a patch for it. but it still wont work. vdev_start still
>>>> fails
>>> Well it would have been helpful from the start to have known about this patch.
>>>
>>> Could you post it?
>>>
>>> Kalle: Since the firmware API changed, how do you want to handle
>>> the differences here?
>>
>> The firmware API shouldn't change like that, but if it has I guess a
>> firmware feature flag to enable a workaround in ath10k sounds like the
>> easiest solution.
>
> the more recent firmware have some new wmi services enabled which can
> be used as indicator as well.
I don't know what flag exactly you are referring to, but using a WMI
service flag to detect this is not really reliable. They can be enabled
or disabled between branches, or even between builds.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-02-10 6:51 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-29 23:11 QCA988X firmware pull-push support Sergey Ryazanov
[not found] ` <CAJ-Vmo=yD7Ct5LFXBO3qNhKsNco91VXMmZOYeBaAuw+DFGq=RQ@mail.gmail.com>
2017-01-30 1:20 ` Sergey Ryazanov
2017-01-30 2:50 ` Adrian Chadd
2017-01-30 8:13 ` Valo, Kalle
2017-01-30 10:28 ` 9984 VHT Sebastian Gottschall
2017-02-01 16:48 ` Ben Greear
2017-02-01 18:45 ` Sebastian Gottschall
2017-02-02 16:18 ` Ben Greear
2017-02-02 18:24 ` Ben Greear
2017-02-02 18:42 ` Sebastian Gottschall
2017-02-02 19:05 ` Ben Greear
2017-02-02 19:08 ` Sebastian Gottschall
2017-02-02 19:18 ` Ben Greear
2017-02-02 19:29 ` Sebastian Gottschall
2017-02-02 19:32 ` Ben Greear
2017-02-02 20:28 ` Sebastian Gottschall
2017-02-02 20:37 ` Ben Greear
2017-02-02 20:45 ` Sebastian Gottschall
2017-02-02 20:50 ` Ben Greear
2017-02-02 21:01 ` Sebastian Gottschall
2017-02-02 21:04 ` Sebastian Gottschall
2017-02-07 12:14 ` Valo, Kalle
2017-02-07 12:39 ` Sebastian Gottschall
2017-02-10 6:50 ` Valo, Kalle [this message]
[not found] ` <c894f9ae-068a-eac3-16e6-c1ada4da22b9@dd-wrt.com>
2017-02-14 10:30 ` Valo, Kalle
2017-02-14 15:21 ` Sebastian Gottschall
2017-02-16 16:20 ` Adrian Chadd
2017-02-16 16:34 ` Sebastian Gottschall
2017-02-17 5:42 ` Adrian Chadd
2017-02-20 15:40 ` Valo, Kalle
2017-02-01 8:21 ` QCA988X firmware pull-push support Sergey Ryazanov
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=87y3xeilor.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.com \
--cc=s.gottschall@dd-wrt.com \
/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).