Hi Larry, On Thu, Apr 18, 2013, Larry Finger wrote: > On 04/18/2013 05:22 PM, Gustavo Padovan wrote: > >We recently added a setup callback to btusb to run device specific > >initialization, take a look in bluetooth-next to check how that can help you > >avoid duplicate a lot of code. > > Thanks for the tip. I knew something was in the planning stage. > > Is there any documentation on using the new facility? Not really, but you can take a look at the "Bluetooth: Add support for Intel Bluetooth device [[8087:07dc]" patch that's currently going through some feedback rounds on linux-bluetooth. It's one of the first users of this new API. Basically what you have is the new setup() callback for HCI drivers and then a new __hci_cmd_sync() function that can be used from within the setup() callback to synchronously send whatever HCI commands you need to send before proceeding with the normal HCI init sequence within the HCI core. To my understanding Marcel has planned to move the vendor specific btusb routines into their own files in the long run (I believe he's used a term "mini driver" for this) but for now the changes are expected to go to the main btusb.c file. Johan -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
