From: Kalle Valo <kvalo@kernel.org>
To: Matthew Schwartz <njtransit215@gmail.com>
Cc: ath11k@lists.infradead.org, cristian.ciocaltea@collabora.com
Subject: Re: question regarding qca2066 and qca206x (Steam Deck OLED/Galileo) on upstream kernels
Date: Tue, 21 May 2024 14:49:03 +0300 [thread overview]
Message-ID: <87zfsjbd1s.fsf@kernel.org> (raw)
In-Reply-To: <CAFKu21aQjbf_vsyikhQqDa0s99WQpzepLa0dWmmhVo5yeWr=Gg@mail.gmail.com> (Matthew Schwartz's message of "Mon, 20 May 2024 13:52:02 -0700")
Matthew Schwartz <njtransit215@gmail.com> writes:
>> Is the mismatch between file/directory structure for QCA2066 and the
>> upstream QCA206X I had to add to the upstream ath11k firmware going to
>> be an issue? Also, QCA206X seems to be missing Notice.txt. Will this
>> cause any issues?
>>
>
> Sorry there is a slight typo here. To clarify: Is the mismatch between
> file/directory structure for upstream QCA2066 and the Valve QCA206X an
> issue. I described the wrong folder as the upstream folder in my
> original reply.
So from what I have seen so far the situation seems to be this:
Steam has some ath11k hack patches to add QCA2066 support to an older
Linux kernel and they also have a separate firmware release. I do not
know where they got them from.
In Linux upstream ("kernel.org") we added initial QCA2066 support for
ath11k in Linux v6.9. We also provided the firmware[1] which will be
also submitted to linux-firmware.git in the near future.
The ath11k upstream version uses different directory structure as the
hack patches, which is not uncommon. Basically using hack patches is at
your own risk and no compatibility is guarenteed, of course. But once
the support is in official Linux kernel we take backwards compatibility
very seriously.
I want to also mention that even if Steam's ath11k firmware version
might work, I still recommend to use the firmware from our repo[1]. I do
not know what changes Steam's firmware version has and it possible might
be incompatible with kernel.org driver. In this mailing list we only
support firmware releases from [1].
[1] https://git.codelinaro.org/clo/ath-firmware/ath11k-firmware/-/tree/main/QCA2066/hw2.1?ref_type=heads
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-05-21 11:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-19 22:14 question regarding qca2066 and qca206x (Steam Deck OLED/Galileo) on upstream kernels Matthew Schwartz
2024-05-20 10:21 ` Kalle Valo
2024-05-20 20:41 ` Matthew Schwartz
2024-05-20 20:52 ` Matthew Schwartz
2024-05-21 11:49 ` Kalle Valo [this message]
2024-05-21 15:51 ` Matthew Schwartz
2024-05-21 11:33 ` Kalle Valo
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=87zfsjbd1s.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=cristian.ciocaltea@collabora.com \
--cc=njtransit215@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