Hi Bala, > This patch in crap directory enables btusb to load firmware > to device RAM when it is plugged in. > Signed-off-by: Bala Shanmugam <sbalashanmugam@xxxxxxxxxxx> > --- > crap/0003-btusb-Add-fw-load-support.patch | 424 +++++++++++++++++++++++++++++ > 1 files changed, 424 insertions(+), 0 deletions(-) > create mode 100644 crap/0003-btusb-Add-fw-load-support.patch > > diff --git a/crap/0003-btusb-Add-fw-load-support.patch b/crap/0003-btusb-Add-fw-load-support.patch > new file mode 100644 > index 0000000..6642d6b > --- /dev/null > +++ b/crap/0003-btusb-Add-fw-load-support.patch > @@ -0,0 +1,424 @@ > +Reason for not yet publishing: Marcel feels that Atheros sflash based BT device > +doesn't follow bluetooth H:2 specification and HCI commands should be supported > +in firmware if it is detected as bluetooth device. Using HCI command, firmware > +should be loaded. > + > +In sflash based device there is not enough memory to support HCI commands in firmware. > +So load firmware from btusb when the device comes up. and why are you just not fixing this properly. You can have a custom firmware loader with a different product ID. Load the firmware and then on reset it brings it up with proper Bluetooth USB class identifiers. Nothing demands that the firmware loading happens via HCI. You can invent your own protocol easily. See bcm203x firmware loader driver that has been around since the beginning of Bluetooth. Regards Marcel -- 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
