From: Wren Turkal <wt@penguintechs.org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: ath11k@lists.infradead.org, linux-bluetooth@vger.kernel.org,
Kalle Valo <kvalo@kernel.org>,
Marcel Holtmann <marcel@holtmann.org>
Subject: Re: QCA6390 bluetooth doesn't work after warm boot or disable/reenable
Date: Tue, 9 Apr 2024 13:11:26 -0700 [thread overview]
Message-ID: <fca46585-c1ed-4a60-91b5-6da39a5bbdec@penguintechs.org> (raw)
In-Reply-To: <CABBYNZJQUy37fxWuCXV1OgM+DNnOr7V0h_rkgcSdw-5hF7iauQ@mail.gmail.com>
On 4/9/24 1:03 PM, Luiz Augusto von Dentz wrote:
> 5.19 seems a little too old, imo, or has it been broken for that long,
> did you at least tried with bluetooth-next? Try contacting the people
> who actually wrote the driver.
Sorry, I didn't answer your question. Yes, I do think it's been broken
for longer than that, but I wanted to confirm.
wt
--
You're more amazing than you think!
next prev parent reply other threads:[~2024-04-09 20:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 19:14 QCA6390 bluetooth doesn't work after warm boot or disable/reenable Wren Turkal
2024-04-06 20:16 ` Wren Turkal
2024-04-06 20:27 ` Wren Turkal
2024-04-06 20:29 ` Wren Turkal
2024-04-06 20:50 ` Wren Turkal
2024-04-08 5:22 ` Kalle Valo
2024-04-08 18:35 ` Wren Turkal
2024-04-10 7:21 ` Kalle Valo
2024-04-08 19:49 ` Wren Turkal
2024-04-09 19:53 ` Wren Turkal
2024-04-09 20:02 ` Wren Turkal
2024-04-09 20:03 ` Luiz Augusto von Dentz
2024-04-09 20:09 ` Wren Turkal
2024-04-09 20:11 ` Wren Turkal [this message]
2024-04-10 22:00 ` Wren Turkal
2024-04-10 22:40 ` Wren Turkal
2024-04-11 20:30 ` Wren Turkal
2024-04-12 19:46 ` Wren Turkal
2024-04-14 12:04 ` quic_zijuhu
2024-04-15 7:52 ` Wren Turkal
2024-04-15 8:07 ` quic_zijuhu
2024-04-15 8:51 ` Wren Turkal
2024-04-15 9:29 ` quic_zijuhu
2024-04-15 11:34 ` quic_zijuhu
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=fca46585-c1ed-4a60-91b5-6da39a5bbdec@penguintechs.org \
--to=wt@penguintechs.org \
--cc=ath11k@lists.infradead.org \
--cc=kvalo@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).