From: Kalle Valo <kvalo@kernel.org>
To: "Luca Weiss" <luca.weiss@fairphone.com>
Cc: <ath10k@lists.infradead.org>
Subject: Re: chan info: invalid frequency 0 (idx 41 out of bounds)
Date: Thu, 12 Oct 2023 13:34:13 +0300 [thread overview]
Message-ID: <87wmvs2kpm.fsf@kernel.org> (raw)
In-Reply-To: <CW5HOU3XBPS7.1KO9C3VGQCX12@fairphone.com> (Luca Weiss's message of "Wed, 11 Oct 2023 11:07:01 +0200")
"Luca Weiss" <luca.weiss@fairphone.com> writes:
> Anybody have an idea about the issue I sent a few months ago?
I don't recall anyone reporting anything similar before. As the ath10k
firmware can be different on devices it is a possibility that's
something specific with your firmware version. Unfortunately I don't
have any tips how to try solve this.
--
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
prev parent reply other threads:[~2023-10-12 10:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 11:41 chan info: invalid frequency 0 (idx 41 out of bounds) Luca Weiss
2023-10-11 9:07 ` Luca Weiss
2023-10-12 10:34 ` Kalle Valo [this message]
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=87wmvs2kpm.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath10k@lists.infradead.org \
--cc=luca.weiss@fairphone.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