From: Hector Martin <marcan@marcan.st>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Janne Grunau <j@jannau.net>
Cc: linux-bluetooth@vger.kernel.org, regressions@lists.linux.dev,
asahi@lists.linux.dev
Subject: Re: [PATCH v1] Bluetooth: hci_sync: Use advertised PHYs on hci_le_ext_create_conn_sync
Date: Fri, 10 May 2024 12:13:30 +0900 [thread overview]
Message-ID: <70078624-d766-4db6-8ddb-511251baf0f2@marcan.st> (raw)
In-Reply-To: <CABBYNZJ-6oyLnBov9H_jym9m-9qiUt1ELxYGuBOdZT29aj9MCA@mail.gmail.com>
Hi,
On 2024/05/10 7:41, Luiz Augusto von Dentz wrote:
<snip>
> If I print the actual value then we got:
>
> Primary PHY: Reserved (0x81)
>
> I guess one needs to disregard the reserved range, well until they are
> no longer reserved then it will no longer work. Perhaps we should talk
> to broadcom to know what is up with using reserved values and if that
> is an apple thing then perhaps we could ask them to provide firmware
> that acts according to the spec.
Apple and Broadcom do not support Linux on this platform. The kernel has
to work with the existing firmware (which is the firmware macOS uses),
we don't get to request changes. If the firmware has quirks the kernel
has to deal with it, that's how it goes. It would be great if we had
vendor support, but that is not something we can control. This is common
(Linux is full of quirks to support noncompliant hardware/firmware).
- Hector
next prev parent reply other threads:[~2024-05-10 3:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240405204037.3451091-1-luiz.dentz@gmail.com>
2024-05-09 16:06 ` [PATCH v1] Bluetooth: hci_sync: Use advertised PHYs on hci_le_ext_create_conn_sync Janne Grunau
2024-05-09 16:30 ` Luiz Augusto von Dentz
2024-05-09 20:09 ` Janne Grunau
2024-05-09 22:23 ` Luiz Augusto von Dentz
2024-05-09 22:41 ` Luiz Augusto von Dentz
2024-05-10 3:13 ` Hector Martin [this message]
2024-05-10 9:54 ` Sven Peter
2024-05-10 14:33 ` Luiz Augusto von Dentz
2024-05-10 14:43 ` Sven Peter
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=70078624-d766-4db6-8ddb-511251baf0f2@marcan.st \
--to=marcan@marcan.st \
--cc=asahi@lists.linux.dev \
--cc=j@jannau.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=regressions@lists.linux.dev \
/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).