Comment 212 for bug 268502
Revision history for this message
| Dominique Meeùs (dominiquem) wrote | #212 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
Kernel bug NOT fixed
I read three weeks ago in the list <email address hidden> somebody patching btusb.c with
+ /* Integrated System Solution devices */
+ { USB_DEVICE(0x1131, 0x1004), .driver_info = BTUSB_WRONG_SCO_MTU },
+
I wonder if this explains that some Integrated System Solution devices recently began to work. Maybe somebody should do the same for D-Link (maybe with some other driver_info). I am a plain user. I am curious, I do my best to understand my system, I do my best to help free and open source system but I am not a developer and I don't feel like patching my btusb myself. I know nothing about C and little about make.
Would a developer be so kind to examine this?
By the way, if I am right, the fact that the D-Link dongle still does a command tx timeout is indeed a kernel bug and the #268502 kernel bug is wrongly marked as fixed.