From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 219571] New: Previous handle short-transfer fix for fake CSR controllers does not account for other fake devices
Date: Sat, 07 Dec 2024 09:41:53 +0000 [thread overview]
Message-ID: <bug-219571-62941@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=219571
Bug ID: 219571
Summary: Previous handle short-transfer fix for fake CSR
controllers does not account for other fake devices
Product: Drivers
Version: 2.5
Hardware: AMD
OS: Linux
Status: NEW
Severity: high
Priority: P3
Component: Bluetooth
Assignee: linux-bluetooth@vger.kernel.org
Reporter: sohailsameja@gmail.com
Regression: Yes
Bisected 2c1dda2acc4192d826e84008d963b528e24d12bc
commit-id:
[ +9.730469] usb 1-1: new full-speed USB device number 10 using xhci_hcd
[ +3.071646] usb 1-2: new full-speed USB device number 11 using xhci_hcd
[ +0.374696] usb 1-2: New USB device found, idVendor=10d7, idProduct=b012,
bcdDevice=88.91
[ +0.000009] usb 1-2: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ +0.000003] usb 1-2: Product: CSR8510 A10
[ +0.017967] Bluetooth: hci0: HCI Read Default Erroneous Data Reporting
command is advertised, but not supported.
[ +0.000007] Bluetooth: hci0: HCI Read Transmit Power Level command is
advertised, but not supported.
[ +0.000002] Bluetooth: hci0: HCI LE Set Random Private Address Timeout
command is advertised, but not supported.
Some fake CSR controllers can also be identified as "Actions Semiconductor
ATS2851 based devices" i.e. 0x10d7, 0xb012 as seen above.
The previous fix should also account for such devices as well.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2024-12-07 9:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-07 9:41 bugzilla-daemon [this message]
2024-12-07 9:44 ` [Bug 219571] Previous handle short-transfer fix for fake CSR controllers does not account for other fake devices bugzilla-daemon
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=bug-219571-62941@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-bluetooth@vger.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;
as well as URLs for NNTP newsgroup(s).