[Bug 60824] [PATCH][regression] Cambridge Silicon Radio, Ltd Bluetooth Dongle unusable

https://bugzilla.kernel.org/show_bug.cgi?id=60824

--- Comment #88 from Andrés Rodríguez (hello@andres.codes) ---

@Swyter
I'm happy to report some progress!

After patching the bitwise 0x04 comparison, the controller can finally be
detected, but is unable to find any devices (tested against a Wiimote and an
Android phone).

This is the hcidump -X:

https://gist.github.com/mixedCase/d6962b3d24e13cf4443e8193c1451c5d

These are the relevant dmesg lines:

[   50.227320] Bluetooth: hci0: CSR: New controller detected; bcdDevice=0x2520,
HCI manufacturer=10, HCI rev=0x3120, LMP subver=0x22bb
[   50.227330] Bluetooth: hci0: CSR: Modern CSR controller type detected
[   50.251489] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   50.251490] Bluetooth: BNEP filters: protocol multicast
[   50.251493] Bluetooth: BNEP socket layer initialized
[   50.340205] NET: Registered protocol family 38
[   50.362740] Bluetooth: RFCOMM TTY layer initialized
[   50.362745] Bluetooth: RFCOMM socket layer initialized
[   50.362756] Bluetooth: RFCOMM ver 1.11

After trying to find devices with Blueman:

[  107.543868] Bluetooth: hci0: command 0x2005 tx timeout
[  109.677220] Bluetooth: hci0: command 0x200b tx timeout
[  111.810719] Bluetooth: hci0: command 0x200c tx timeout

---

After patching out both comparisons, the hcidump -X changes a little bit:

https://gist.github.com/mixedCase/e286bbc5f43807bd04c59c2c75cfb88f

I notice in there my machine's hostname (Enterprise) which is the default bluez
identifier.

Thanks for all the help so far! Hope we can find a pattern here.

-- 
You are receiving this mail because:
You are the assignee for the bug.