ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lukas F. Hartmann <lukas@mntre.com>
To: Gary Bisson <bisson.gary@gmail.com>, Kalle Valo <kvalo@kernel.org>
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 17:35:58 +0200	[thread overview]
Message-ID: <878rcn4boh.fsf@mntre.com> (raw)
In-Reply-To: <ZIgoHqP8gk5wdP8A@p1g2>

Hi Gary & Kalle,

Gary Bisson <bisson.gary@gmail.com> writes:

>> 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?
>
> FYI we have a branch in our repo with the firmware that worked on ath10k
> at some point [2].

Thanks, I looked at this FW now and it is exactly the same as the
"untested" in the ath10k-firmware repo
https://github.com/kvalo/ath10k-firmware/tree/master/QCA9377/hw1.0/untested

So if that worked with ath10k several years ago (when?) I could try to
reconstruct an older version and try to bisect for a regression, though
I imagine it will be complicated to make these old versions work with
APIs that have changed in the meantime in Linux.

Best
Lukas
-- 
Lukas F. Hartmann, CEO
MNT Research GmbH
https://mntre.com

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2023-06-13 15:36 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
2023-06-13  8:26   ` Gary Bisson
2023-06-13 15:35     ` Lukas F. Hartmann [this message]
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=878rcn4boh.fsf@mntre.com \
    --to=lukas@mntre.com \
    --cc=ath10k@lists.infradead.org \
    --cc=bisson.gary@gmail.com \
    --cc=gary.bisson@boundarydevices.com \
    --cc=kvalo@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