Hi Jui-Hao, > After working on this subject for one month. (no matter on old > hci_usb.c or on > btusb.c), eventually I found that if we want to change the > alternative setting > of a usb interface, the only way is to use "Set Interface" in > "Standard Device > Request" defined by usb specification. In usb core message.c, the > corresponding > is usb_set_interface() function. Besides, there is no additional > behavior > definition after the "Set Interface" request. > From my current experiment, it seems that once the interface is > set, the > reserved bandwidth will be reset, which means the adapter may find > out "oh! my > bandwidth is reset, what should I do to my current voice link ?" > Anyway, maybe I am too pessimistic, maybe it just needs to change > the usb core > driver to support some asynchronous action instead of brutal force > to reset the > bandwidth of all current connections. I will look into it later. > The following is a update to Alok's patch, which tries to resubmit a > new urb > request after usb_set_interface() actually Oliver posted the first attempt for the btusb changes and that is what you should be working on. The hci_usb driver is really unfixable and not even worth to bother since once btusb gets full SCO support, we are going to remove it. Also create unified diffs. I am never gonna twist my brain to read context diffs. Regards Marcel ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Bluez-devel mailing list Bluez-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/bluez-devel
