From: Kalle Valo <kvalo@kernel.org>
To: "Lukas F. Hartmann" <lukas@mntre.com>
Cc: ath10k@lists.infradead.org, gary.bisson@boundarydevices.com
Subject: Re: Problems with QCA9377 SDIO on NXP i.MX8MPlus SOM
Date: Tue, 13 Jun 2023 11:05:14 +0300 [thread overview]
Message-ID: <87mt13eqit.fsf@kernel.org> (raw)
In-Reply-To: <875y7swixj.fsf@mntre.com> (Lukas F. Hartmann's message of "Mon, 12 Jun 2023 21:59:36 +0200")
"Lukas F. Hartmann" <lukas@mntre.com> writes:
> I'm trying to get the QCA9377 SDIO module on Boundary Devices'
> i.MX8MPlus SOM working with the ath10k mainline driver (from Linux git
> tip). Currently it can scan and see some APs and authenticate, but not
> associate (timeout). Several months ago I thought this was an SDIO
> signalling issue with the SoC, but I'm not sure anymore, because I fixed
> up the qcacld driver for the current Linux kernel and it works fine on
> the same system (i.e. I can rmmod ath10k_sdio and insmod wlan.ko and it
> works).
>
> I wonder if it is some kind of firmware/driver mismatch. I pasted the
> relevant dmesg output after my signature below.
>
> This is after I tried to build my own board-2.bin including bdwlan30.bin
> from qcacld-2.0-CNSS.LEA.NRT_3.0 (source:
> https://github.com/8devices/qcacld-2.0/tree/CNSS.LEA.NRT_3.0/firmware_bin/sdio).
> It gets picked up but doesn't seem to make a difference. I also tried
> assembling my own firmware-5-sdio.bin from qwlan30.bin and otp30.bin but
> this triggers a firmware crash (with register dump) when loading
> ath10k_sdio.ko.
>
> The qcacld driver works with that firmware, though.
>
> Any pointers on how to debug this are most appreciated.
Trying significantly older ath10k from an older kernel is something to
try in case there are recent regressions in ath10k.
I don't have an ath10k SDIO device myself so I don't know the state of
SDIO support in ath10k. Does anyone else from the list know?
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2023-06-13 8:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 19:59 Problems with QCA9377 SDIO on NXP i.MX8MPlus SOM Lukas F. Hartmann
2023-06-13 8:05 ` Kalle Valo [this message]
2023-06-13 8:26 ` Gary Bisson
2023-06-13 15:35 ` Lukas F. Hartmann
2023-09-04 14:28 ` Bastian Krause
2023-09-05 5:58 ` w.wadepohl
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=87mt13eqit.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath10k@lists.infradead.org \
--cc=gary.bisson@boundarydevices.com \
--cc=lukas@mntre.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.