[Bug 2094969] Re: bluetooth/detect-output failed due to the lack of USB device id in btusb.c

This bug is awaiting verification that the linux-oem-6.11/6.11.0-1013.13
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-oem-6.11' to 'verification-done-
noble-linux-oem-6.11'. If the problem still exists, change the tag
'verification-needed-noble-linux-oem-6.11' to 'verification-failed-
noble-linux-oem-6.11'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-noble-linux-oem-6.11-v2 verification-needed-noble-linux-oem-6.11

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2094969

Title:
bluetooth/detect-output failed due to the lack of USB device id in
btusb.c

Status in HWE Next:
New
Status in linux package in Ubuntu:
New
Status in linux-oem-6.11 package in Ubuntu:
New
Status in linux source package in Noble:
Invalid
Status in linux-oem-6.11 source package in Noble:
Fix Committed

Bug description:
[Impact]
BT hardware is not available on certain machines:

1. Machine with MT7925 BT (USB VID/PID 13d3/3628)
2. Machine with MT7925 BT (USB VID/PID 0489/e14e)

[Fix]
Add USB device IDs into device table in btusb.c fixes the issue.

1. For VID/PID 13d3/3628, the patch has already been merged into
linux-next:

f597b8982d51 Bluetooth: btusb: Add new VID/PID 13d3/3628 for MT7925

2. For VID/PID 0489/e14e, the patch is still under review. Out of the
urgency, we're going to make a SAUCE patch first.


[Test Plan]
1. Install Ubuntu image and boot into the OS
2. Run $ sudo checkbox-cli run com.canonical.certification::bluetooth/detect-output and see if the test is passed

[Where problems could occur]
The two BT hardware may have not yet been matured, so there might be issues in the future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2094969/+subscriptions