From: Jason Perlow <jperlow@gmail.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Marcel Holtmann <marcel@holtmann.org>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: btbcm: Add entries for BCM4364B3 UART Bluetooth
Date: Sun, 22 Nov 2026 12:14:00 -0500 [thread overview]
Message-ID: <179536764088.21183.18060597598784441550@gmail.com> (raw)
In-Reply-To: <6f0b4dfc-4bb3-45f9-81ae-347e345cbe33@molgen.mpg.de>
Hi Paul,
Thanks for looking at it. (Resending as plain text; the first copy of
this reply bounced from the lists because of an HTML part.)
As tested it is about naming and the firmware lookup. The controller
already came up without the entries, but it was logged without a name
and the driver only tried the generic brcm/BCM.hcd. With the entries it
is named BCM4364B3 and brcm/BCM4364B3.hcd is tried first. I only checked
the log output and that the controller still initialises on both units;
I have not compared pairing or throughput before and after, and I am
not aware of a unit where Bluetooth did not work without this. The
commit message now says that explicitly so it does not read as a bug
fix.
You are right about the order. The table is ascending by subversion
here, so v2 puts 0x3032 and 0x305b between 0x2128 and 0x4119.
v2 is already out as a separate mail
(<20261122165132.14015-1-jperlow@gmail.com>) with your Reviewed-by
added, as you offered.
Thanks,
Jason
prev parent reply other threads:[~2026-11-22 17:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 21:38 Jason Perlow
2026-11-22 8:27 ` Paul Menzel
2026-11-22 17:14 ` Jason Perlow [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=179536764088.21183.18060597598784441550@gmail.com \
--to=jperlow@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=pmenzel@molgen.mpg.de \
/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®