Hi David, > > Pulling the usb tree is always fun. > > > > drivers/bluetooth/bfusb.c: In function `bfusb_load_firmware': > > drivers/bluetooth/bfusb.c:589: structure has no member named `halted' > > drivers/bluetooth/bfusb.c:589: structure has no member named `halted' > > drivers/bluetooth/bfusb.c:631: structure has no member named `halted' > > drivers/bluetooth/bfusb.c:631: structure has no member named `halted' > > Right, "halted" is gone, and won't be back. It was state > that couldn't be accurate; the truth is kept in the device. > I'd do the obvious make-it-compile fix for the moment. > > That firmware loading code needs to be modified for other > reasons. It shouldn't touch "toggle"; directly setting the > configuration is dangerous; and it should probably just reset > the device (that should now work!) to force re-enumeration > after everything is updated ... since the old device state > won't be cleaned up properly otherwise.
you are fully right that I shouldn't have done this, but sometimes the time is against me and I must provide a quick fix before getting out the final solution. Fixing the bfusb driver to correctly use the USB config change for firmware loading is on the top of my todo list. Regards Marcel ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
