The problem is that there seem to be two devices using the same vendor and model string. We have the info for the bluetooth dongle (0x050d:0x0121, Class=224 (wireless), SubClass=1 (radio) and Protocol=1 (bluetooth) from the lsusb output). The whole thing has to be fixed in the driver and the following patch could be a start. However, this has to be done upstream. Even more because the quick approach below (if it works) would be the wrong direction. Rather than checking special non-working cases, I guess it would make sense to extend the matching criteria more specifically to the supported classes. But that would be the decission of the maintainer anyways.
The problem is that there seem to be two devices using the same vendor and model string. We have the info for the bluetooth dongle (0x050d:0x0121, Class=224 (wireless), SubClass=1 (radio) and Protocol=1 (bluetooth) from the lsusb output). The whole thing has to be fixed in the driver and the following patch could be a start. However, this has to be done upstream. Even more because the quick approach below (if it works) would be the wrong direction. Rather than checking special non-working cases, I guess it would make sense to extend the matching criteria more specifically to the supported classes. But that would be the decission of the maintainer anyways.
USB PEGASUS DRIVER pegasus2. sourceforge. net/
P: Petko Manolov
M: <email address hidden>
L: <email address hidden>
L: <email address hidden>
W: http://
S: Maintained