From: Kalle Valo <kvalo@codeaurora.org>
To: Pavel Procopiuc <pavel.procopiuc@gmail.com>
Cc: ath11k@lists.infradead.org
Subject: Re: PROBLEM: unable to get QCA6390 to work
Date: Tue, 03 Nov 2020 16:23:58 +0200 [thread overview]
Message-ID: <87ft5qsem9.fsf@codeaurora.org> (raw)
In-Reply-To: 87ft5rszcs.fsf@codeaurora.org
Kalle Valo <kvalo@codeaurora.org> writes:
> Pavel Procopiuc <pavel.procopiuc@gmail.com> writes:
>
>> After doing some testing I was able to get it running under some
>> specific conditions. I took the v5.9 tag of the main kernel tree and
>> merged in the ath11k-qca6390-bringup-202009250825 tag from the ath
>> tree. I had to fix some trivial conflicts, but the resulting kernel
>> together with the firmware (amss.bin, m3.bin and board-2.bin) gave me
>> a working driver that I was able to use to connect to my AP in both
>> 2,4 and 5GHz.
>>
>> I then tried to copy over the ath11k driver source resulting from that
>> merge on top of the 5.10-rc2 tag. After fixing some API breakage
>> (IEEE80211_TX_CTRL_HW_80211_ENCAP and ieee80211_set_hw_80211_encap) to
>> make it compile I booted into the resulting kernel, but ath11k driver
>> was giving me the same firmware errors I had initially on 5.10-rc2. So
>> it looks like there might be some change in 5.10 that broke the logic.
>
> Interesting, and worrisome. I have not yet tested v5.10-rc releases,
> I'll do that ASAP and try to reproduce your issue. If I see the same
> problem then it should be possible to bisect the issue pretty easily.
For me v5.10-rc2 (no extra patches) was working fine. A bisection would
be a good next step. What I suggest that is that you first test these
three commits from Linus' tree in this order:
fd5ad4d1e980 wcn36xx: Advertise beacon filtering support in bmps
3650b228f83a Linux 5.10-rc1
3cea11cd5e3b Linux 5.10-rc2
Commit fd5ad4d1e980 is based on v5.9-rc6 so try that first. In these
three commits ath11k is practically identical, the only change is a
small bugfix in commit 8431350eee2e ("ath11k: Fix memory leak on error
path").
If commit fd5ad4d1e980 works for you then use that as "good" commit for
git-bisect. And use 3650b228f83a or 3cea11cd5e3b as the "bad" commit,
depending on which one was broken first. Hopefully the bisect would give
us more clues what's happening.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2020-11-03 14:24 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 10:32 PROBLEM: unable to get QCA6390 to work Pavel Procopiuc
2020-11-02 17:42 ` Kalle Valo
2020-11-02 18:21 ` Pavel Procopiuc
2020-11-02 21:14 ` Pavel Procopiuc
2020-11-03 6:56 ` Kalle Valo
2020-11-03 13:12 ` Pavel Procopiuc
2020-11-04 9:32 ` Pavel Procopiuc
2020-11-03 14:23 ` Kalle Valo [this message]
2020-11-03 21:01 ` Pavel Procopiuc
2020-11-04 9:12 ` Kalle Valo
2020-11-04 22:15 ` Pavel Procopiuc
2020-11-05 9:04 ` Regression: QCA6390 fails with "mm/page_alloc: place pages to tail in __free_pages_core()" Kalle Valo
2020-11-05 9:47 ` Pavel Procopiuc
2020-11-05 10:42 ` Vlastimil Babka
2020-11-05 10:45 ` Pavel Procopiuc
2020-11-05 11:13 ` David Hildenbrand
2020-11-05 12:55 ` Pavel Procopiuc
2020-11-05 20:23 ` David Hildenbrand
2020-11-06 17:32 ` Pavel Procopiuc
2020-11-06 20:41 ` David Hildenbrand
2020-11-11 19:23 ` Kalle Valo
2020-11-11 20:41 ` Pavel Procopiuc
2020-11-12 10:48 ` David Hildenbrand
2020-11-13 8:17 ` Pavel Procopiuc
2020-11-13 11:08 ` Carl Huang
2020-11-13 11:44 ` Carl Huang
2020-11-13 12:52 ` Pavel Procopiuc
2020-11-13 13:36 ` wi nk
2020-11-13 13:56 ` David Hildenbrand
2020-11-13 15:49 ` wi nk
2020-11-03 8:42 ` PROBLEM: unable to get QCA6390 to work Carl Huang
2020-11-03 14:12 ` Pavel Procopiuc
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=87ft5qsem9.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=pavel.procopiuc@gmail.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).