Hi Marcel, On Sat, Feb 14, 2015, Marcel Holtmann wrote: > The Broadcom firmware files are named with firmware version information > encoded into lmp_subver field. So BCM20702B0_002.001.014.0527.0607.hex > would be represented by 0x410e. To allow for an easier decoding of the > actual firmware names, provide an internal table that does the mapping > and request the firmware file by name. > > Bluetooth: hci0: BCM20702B0 (002.001.014) build 0607 > > Now the complicated encoding of lmp_subver will be decoded and turned > into the name and firmware version information from the firmware files. > > The previous attempt of using udev->product failed badly since it never > contains any matching entry to the actual hardware or firmware files > distributed by Broadcom in their Windows drivers. It is even worse since > it can change depending on if the internal bootstrapping happened before > the USB bus enumeration or after. This caused many race conditions. > > Signed-off-by: Marcel Holtmann <marcel@xxxxxxxxxxxx> > --- > drivers/bluetooth/btusb.c | 75 +++++++++++++++++++++++++++++++++-------------- > 1 file changed, 53 insertions(+), 22 deletions(-) Applied to bluetooth-next. Thanks. Johan -- 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
