Hi Bastien, > Here are the patches to get sixpair support built into BlueZ. It uses > libusb-1.0 as well as a yet to be merged libusb-1.0 patch to allow > re-attaching a driver to a device. so I applied all patches except the changes for the build system. I am not sure that this is the right way to go. If we require libusb-1.0, then we should just change our current code that depends on libusb-0.1 and require libusb-1.0 for all of it. > Problems left to solve: > - sixaxis enabler code (as seen in enable_sixaxis() in compat/hidd.c) > seems to have disappeared from the input plugin. Is that done in the > kernel now, or was it just removed? The kernel is not doing it. Seems to be an oversight. > - After "cable pairing" the device, I need to unplug/replug the adapter, > or restart bluetoothd. Can anyone think of a better way of getting the > list of devices updated? We could use inotify or SIGUSR2 or something to re-read the database. > - Some minor niggles in the code itself (use D-Bus instead of parsing > command-line tools) Of course. > - udev rule(s) and parsing only the selected device would be necessary > if not required If we can do this via the HID bus, then we can do it every time and it would not affect the controller itself. Regards Marcel -- 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
