ath11k.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Carl Huang <cjhuang@codeaurora.org>
To: Pavel Procopiuc <pavel.procopiuc@gmail.com>
Cc: ath11k@lists.infradead.org, Kalle Valo <kvalo@codeaurora.org>
Subject: Re: PROBLEM: unable to get QCA6390 to work
Date: Tue, 03 Nov 2020 16:42:01 +0800	[thread overview]
Message-ID: <51201ba28aeccb57dabc5e72868a899f@codeaurora.org> (raw)
In-Reply-To: <c9cc0ec6-4dda-2608-3575-0e6dfb6d0852@gmail.com>

On 2020-11-03 05:14, Pavel Procopiuc wrote:
> 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.
> 
> Op 02.11.2020 om 19:21 schreef Pavel Procopiuc:
>> Ah, my bad, I've now renamed the board-2.bin file, the md5's match 
>> yours. But it doesn't seem to have a positive effect.

Please set ath11k.ko module parameter debug_mask to 0xffffffff, and then 
reproduce and share the log.

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

  parent reply	other threads:[~2020-11-03 13:28 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
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       ` Carl Huang [this message]
2020-11-03 14:12         ` PROBLEM: unable to get QCA6390 to work 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=51201ba28aeccb57dabc5e72868a899f@codeaurora.org \
    --to=cjhuang@codeaurora.org \
    --cc=ath11k@lists.infradead.org \
    --cc=kvalo@codeaurora.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).