Hi Bala, > Firmware loading to target RAM needs to be done once when the device is inserted. Firmware loading will not be required every time > the device goes from DOWN to UP. I think each HCI driver requires > a separate firmware loading code as firmware loading is > different for different interfaces. Please advice if my understanding is wrong. > > I initially thought of registration > mechanism with btusb transport driver to load firmware, but before > the device is inserted btusb will not be loaded and registering the > firmware load function with btusb was not possible. > > Please advice alternate solution to load firmware from transport driver. my advise would be to just build devices that change their USB VID/PID after the firmware got loaded. That way it is easy to have a firmware loading driver and just btusb for real operation. Why is it so hard to build just simple hardware that would just work. 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
