Description of problem: Bug 770233 introduced support for this device, but ASUS has given it a unique USB ID when they packaged it in my ASUS P8Z77-I Deluxe motherboard. The kernel does not detect this new ID. [ 1.446956] usb 1-1.5: New USB device found, idVendor=0b05, idProduct=17b5 [ 1.446958] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1.446959] usb 1-1.5: Product: BCM20702A0 [ 1.446961] usb 1-1.5: Manufacturer: Broadcom Corp [ 1.446962] usb 1-1.5: SerialNumber: foo $ hcitool dev Devices: Version-Release number of selected component (if applicable): kernel-3.6.5-1.fc17.x86_64
Created attachment 643971 [details] linux-3.6-bluetooth-asus.patch The attached patch adds the new ID to the btusb module. I created a scratch build with the patch and the bluetooth adapter is detected and is fully functional. http://koji.fedoraproject.org/koji/taskinfo?taskID=4682010
Can you send this upstream?
Done. Bug link added here.
(In reply to comment #3) > Done. Bug link added here. Heh, that's not quite what I meant but also good. Can you look over Documentation/SubmittingPatches (including the portion about the Signed-off-by tag) in the kernel tree and send it to the linux-bluetooth mailing list? I have no idea if the bluetooth maintainers use the upstream kernel.org bugzilla. It's very hit or miss among upstream maintainers.
(In reply to comment #4) > Heh, that's not quite what I meant but also good. Can you look over > Documentation/SubmittingPatches (including the portion about the > Signed-off-by tag) in the kernel tree and send it to the linux-bluetooth > mailing list? A quick scan of the linux-bluetooth archive shows someone has already started the process, but the patch has not been applied upstream, yet. http://www.spinics.net/lists/linux-bluetooth/msg31607.html
The patch has now been pushed to bluetooth-next. https://git.kernel.org/?p=linux/kernel/git/bluetooth/bluetooth-next.git;a=commit;h=1ee3ff6110c16acfc915a79b1e3feb5013c41e75
(In reply to comment #6) > The patch has now been pushed to bluetooth-next. > > https://git.kernel.org/?p=linux/kernel/git/bluetooth/bluetooth-next.git; > a=commit;h=1ee3ff6110c16acfc915a79b1e3feb5013c41e75 OK, great. Thanks for the pointer. I'll get this added shortly.
Applied to f16-rawhide. There was one additional device ID patch I found for f16-f18 and that was added as well. Thanks again for the report.
kernel-3.6.7-5.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/kernel-3.6.7-5.fc18
kernel-3.6.7-4.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/kernel-3.6.7-4.fc17
kernel-3.6.7-4.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/kernel-3.6.7-4.fc16
Package kernel-3.6.7-4.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kernel-3.6.7-4.fc17' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-18684/kernel-3.6.7-4.fc17 then log in and leave karma (feedback).
kernel-3.6.7-4.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
kernel-3.6.7-5.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
kernel-3.6.7-4.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.