From: patchwork-bot+bluetooth@kernel.org
To: Ton Sharp <66ton99@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
linux-bluetooth@vger.kernel.org, josemiguelo.ochoa@gmail.com,
gargaditya08@live.com
Subject: Re: [PATCH bluetooth-next] Bluetooth: hci_event: strip Broadcom vendor bits from legacy adv report type
Date: Thu, 15 Oct 2026 19:40:05 +0000 [thread overview]
Message-ID: <179209320528.4073732.6498666167619250326.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261015114903.784731-1-66ton99@gmail.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 15 Oct 2026 14:49:01 +0300 you wrote:
> Broadcom controllers running ROM firmware on Apple T2 Macs (where no
> RAM patchram exists, e.g. BCM4364B3 on MacBookPro16,1) set vendor bits
> 0x10/0x20/0x80 in the legacy LE Advertising Report Event_Type.
>
> As a result, directed advertisements (ADV_DIRECT_IND) arrive as
> 0x81/0x91/0xa1 instead of 0x01. Because process_adv_report() drops any
> legacy report with type > LE_ADV_SCAN_RSP (0x04) as an unknown advertising
> packet type, bonded LE peripherals (such as Apple Magic Mouse/Keyboard)
> and Chrome passkey proximity scans fail to discover or reliably reconnect
> to the host.
>
> [...]
Here is the summary with links:
- [bluetooth-next] Bluetooth: hci_event: strip Broadcom vendor bits from legacy adv report type
https://git.kernel.org/bluetooth/bluetooth-next/c/e3bb245b2daf
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-10-15 19:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 11:49 [PATCH bluetooth-next] Bluetooth: hci_event: strip Broadcom vendor bits from legacy adv report type Ton Sharp
2026-10-15 12:44 ` [bluetooth-next] " bluez.test.bot
2026-10-15 19:40 ` patchwork-bot+bluetooth [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=179209320528.4073732.6498666167619250326.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=66ton99@gmail.com \
--cc=gargaditya08@live.com \
--cc=josemiguelo.ochoa@gmail.com \
--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