All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rémi Cattiau" <remi@cattiau.com>
To: linux-input@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 13411] New: Barscanner (USB HID Keyboard) stopped functioning in kernels >= 2.6.28
Date: Tue, 01 Dec 2009 21:07:14 +0100	[thread overview]
Message-ID: <4B157772.1050207@cattiau.com> (raw)

  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@usb.org <mailto:admin@usb.org>  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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2009-12-01 20:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-01 20:07 Rémi Cattiau [this message]
     [not found] <bug-13411-10286@http.bugzilla.kernel.org/>
2009-06-02  3:25 ` [Bugme-new] [Bug 13411] New: Barscanner (USB HID Keyboard) stopped functioning in kernels >= 2.6.28 Andrew Morton
2009-06-02  3:44   ` Maximi89
2009-06-02  9:29     ` Paulius Zaleckas
     [not found]   ` <20090601202509.87f57ef9.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2009-06-02  9:55     ` Jiri Kosina
     [not found]       ` <alpine.LRH.2.00.0906021148140.29471-1ReQVI26iDCaZKY3DrU6dA@public.gmane.org>
2009-11-28 21:51         ` Guido Dorssers
     [not found]           ` <200911282251.28780.bugzilla.kernel.org-Dy4KJ/v5nlEVgfBnK23ub6xOck334EZe@public.gmane.org>
2009-12-01 10:40             ` Jiri Kosina
2009-12-01 11:08               ` Rémi Cattiau

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B157772.1050207@cattiau.com \
    --to=remi@cattiau.com \
    --cc=linux-input@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.