On Tue, Mar 20, 2012 at 9:55 AM, Eric Miao <eric.miao@xxxxxxxxxxxxx> wrote: > On Tue, Mar 20, 2012 at 1:37 AM, Marcel Holtmann <marcel@xxxxxxxxxxxx> wrote: >> Hi Eric, >> >>> Some Ralink WiFi + CSR BT module needs bluetooth radio to be >>> turned on explicitly with bccmd by the following command: >>> >>> bccmd psset -r 0x028c 0x0001 >>> >>> The HCI will be probed successfully, but due to the default >>> OFF state of the radio, no scan or connection can be made. >>> This patch adds the udev rule so that once the HCI is up, >>> udev will invoke bccmd with warm reset to turn on the radio. >>> >>> [1] https://bugs.launchpad.net/bugs/781556 >>> [2] https://bugs.meego.com/show_bug.cgi?id=3498 >>> [3] http://ubuntuforums.org/showthread.php?t=1776108 >>> [4] http://ubuntuforums.org/showthread.php?t=1703941 >> >> why are we doing this in userspace? The btusb.c driver has the option >> for pre-execution HCI commands queue. Why not use that one. > > That sounds like a better one, I'll take a look and see if it's possible > to give a revised version. Thanks Marcel. Hmm... have thought about this twice, and I still prefer the bccmd command in user space. Converting this very straight-forward setting w/ bccmd into HCI commands would make it rather awkward. And so the further question would be the bluetooth-hid2hcd.rules, will this file gradually disappear and the necessary operations be made into the kernel code eventually? -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
