Johan Hedberg schrieb:
Hi Marcel,
On Fri, Jul 19, 2013, Marcel Holtmann wrote:
HCI Event: Command Complete (0x0e) plen 12 [hci0] 0.043811
Read Local Version Information (0x04|0x0001) ncmd 1
Status: Success (0x00)
HCI version: 2 - 0x2006
LMP version: 2 - 0x1806
Manufacturer: AVM Berlin (31)
it declares itself here as Bluetooth 1.2 device. Which means it is the
second generation of BlueFritz! USB device.
<snip>
< HCI Command: Read Local Supported Comm.. (0x04|0x0002) plen 0 [hci0] 0.210014
HCI Event: Command Status (0x0f) plen 4 [hci0] 0.217361
Read Local Supported Commands (0x04|0x0002) ncmd 1
Status: Unknown HCI Command (0x01)
And here is your failing command. Newer kernels have been strict with
failing commands and will just abort the setup if anything goes wrong.
Johan, we need to figure out on how to work around this one. Might
just match for the manufacturer before sending the command.
Either that or a quirk based on the USB id. Wouldn't matching just the
manufacturer be a bit problematic for any newer chips from this company,
or they stopped doing Bluetooth dongles after this one?
They stopped doing Bluetooth dongles after this one. I found no more
Product with bluetooth on their website.
The support from AVM endet on 01.12.2009.
As I read here http://www.wehavemorefun.de/fritzbox/BlueFRITZ!_USB
Should I open my trashbin?
--
Gruss, Joerg
--
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
