From: "André Eikmeyer" <dev@deq.rocks>
To: Sasha Finkelstein <k@chaosmail.tech>
Cc: Myria Sarvay <myrialsarvay@gmail.com>,
marcel@holtmann.org, luiz.dentz@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
sven@kernel.org, j@jannau.net, asahi@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
Yossef Osman <Yossef.Osman@proton.me>,
Aditya Garg <aditya.garg@linux.dev>
Subject: Re: [PATCH v2 1/2] Bluetooth: btbcm: raise ACL priority on Apple Broadcom controllers
Date: Fri, 6 Nov 2026 12:12:50 +0100 [thread overview]
Message-ID: <20261106121250.0caf3299@kait2en-mbp15-1> (raw)
In-Reply-To: <5F81A6CC-46B6-4C45-BB05-8483057EEE7C@chaosmail.tech>
On Fri, 6 Nov 2026 11:53:13 +0100
Sasha Finkelstein <k@chaosmail.tech> wrote:
> Sleep. I intened to say sleep and I have no idea how I managed to typo
> it as stream, but that is what I meant. Sorry.
Bwah! Well... np. But you know we are using s3 on T2? So the
controller will be off to Nirvana anyways. My last info is that Asahi
is stuck on s2? So even when testing with s2 on T2, we have UART
transport on the 4634 chips... So if at all the 4377 on 9,1 and 15,4
T2s is in question, right?
Andre
next prev parent reply other threads:[~2026-11-06 11:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 8:57 [PATCH v2 0/2] Bluetooth: Broadcom controllers of the Apple T2 Macs Andre Eikmeyer
2026-11-05 8:57 ` [PATCH v2 1/2] Bluetooth: btbcm: raise ACL priority on Apple Broadcom controllers Andre Eikmeyer
2026-11-06 6:05 ` Myria Sarvay
2026-11-06 7:33 ` André Eikmeyer
2026-11-06 9:40 ` Sasha Finkelstein
2026-11-06 10:39 ` André Eikmeyer
2026-11-06 10:53 ` Sasha Finkelstein
2026-11-06 11:12 ` André Eikmeyer [this message]
2026-11-06 15:06 ` André Eikmeyer
2026-11-05 8:57 ` [PATCH v2 2/2] Bluetooth: set the strict duplicate filter quirk " Andre Eikmeyer
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=20261106121250.0caf3299@kait2en-mbp15-1 \
--to=dev@deq.rocks \
--cc=Yossef.Osman@proton.me \
--cc=aditya.garg@linux.dev \
--cc=asahi@lists.linux.dev \
--cc=j@jannau.net \
--cc=k@chaosmail.tech \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=myrialsarvay@gmail.com \
--cc=sven@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
all inboxes | Powered by JetHome®