From: James Prestwood <prestwoj@gmail.com>
To: Jeremy Whiting <jeremy.whiting@collabora.com>, iwd@lists.linux.dev
Cc: Edmund Smith <ed.smith@collabora.com>,
Alvaro Soliverez <alvaro.soliverez@collabora.com>
Subject: Re: ios hotspot fix
Date: Tue, 26 Mar 2024 04:33:50 -0700 [thread overview]
Message-ID: <fc1a740b-41cf-48d4-a95c-3c733801b672@gmail.com> (raw)
In-Reply-To: <bfb5d799-65bb-412c-be32-3ceea0211968@collabora.com>
Hi Jeremy,
>
> The bug we were experiencing was only on the OLED version of the steam
> deck. According to lscpi it uses this wifi chip:
>
> 3:00.0 Network controller: Qualcomm Technologies, Inc QCNFA765
> Wireless Network Adapter (rev 01)
> DeviceName: Broadcom 5762
> Subsystem: Qualcomm Technologies, Inc QCNFA765 Wireless
> Network Adapter
> Flags: bus master, fast devsel, latency 0, IRQ 77
> Memory at 80000000 (64-bit, non-prefetchable) [size=2M]
> Capabilities: <access denied>
> Kernel driver in use: ath11k_pci
> Kernel modules: ath11k_pci
Interesting, this is the same chip we have several devices running and I
have never seen this behavior, granted I've never connected to an iOS
hotspot. So maybe iOS does have some hand in it. This might be something
I can reproduce when I have some time to set everything back up again
because I do have this same chipset here locally.
fwiw the firmware we've been running is:
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36
Thanks,
James
prev parent reply other threads:[~2024-03-26 11:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 17:26 ios hotspot fix Jeremy Whiting
2024-03-25 18:23 ` James Prestwood
2024-03-25 19:11 ` Jeremy Whiting
2024-03-26 11:33 ` James Prestwood [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=fc1a740b-41cf-48d4-a95c-3c733801b672@gmail.com \
--to=prestwoj@gmail.com \
--cc=alvaro.soliverez@collabora.com \
--cc=ed.smith@collabora.com \
--cc=iwd@lists.linux.dev \
--cc=jeremy.whiting@collabora.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 read-only IMAP folder(s) and NNTP newsgroup(s).