Hello all,
Here my lsusb :
Bus 001 Device 006: ID 1130:0001 Tenx Technology, Inc.
Bus 001 Device 006: ID 1130:0001 Tenx Technology, Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x1130 Tenx Technology, Inc.
idProduct 0x0001
bcdDevice 1.00
iManufacturer 0
iProduct 2
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 59
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
** UNRECOGNIZED: 09 21 10 01 00 01 22 29 00
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 10
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
** UNRECOGNIZED: 09 21 10 01 21 01 22 17 00
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 10
I'll send an email to admin@xxxxxxx <mailto:admin@xxxxxxx> to know
which one is a valid member.
Let me know if any trouble
Rémi
Le 01/12/2009 11:40, Jiri Kosina a écrit :
On Sat, 28 Nov 2009, Guido Dorssers wrote:
The problem apparently [1] is, that the vendor has been super-creative and
assigned the same combination of idVendor/idProduct to completely
different devices. Oh well.
Remi, could you please check your device against the lsusb data provided
in bugzilla to check whether there is any possibility to distinguish these
devices, so that we could put some ugly check in place probably?
Thanks.
[1]http://lkml.org/lkml/2009/2/10/434
Hi all,
A belated thanks for having pointed me into the right direction to get my
barcodescanner operational. However, as a thought since the bug is still
present, why not solve it with something as simple as making the blacklisting
user-configurable instead of blacklisting valid HID devices on purpose?
Hi,
actually, my current plan is to remove the blacklist entry for this
combination of VID/PID completely, and let the user decide and unbind the
driver via sysfs eventually, if needed (maybe together with warning in
dmesg).
As the vendor apparently messed up horribly, as far as I understand, I
don't really see another option.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
