"SV" == Sergey Vlasov writes:

 >> Report Descriptors: ** UNAVAILABLE **

 SV> To get full "lsusb -v" output for a HID device, you need to
 SV> unload the usbhid module.  Be careful if you also have an USB
 SV> keyboard - you will need to enter all commands on one line:

 SV>    rmmod usbhid; lsusb -v >lsusb.log; modprobe usbhid

here is the output for this device:

============================================================================
Bus 006 Device 029: ID 0665:5161  
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0         8
  idVendor           0x0665 
  idProduct          0x5161 
  bcdDevice            0.02
  iManufacturer           1 Cypress Semiconductor
  iProduct                2 USB to Serial
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           34
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          3 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         3 Human Interface Devices
      bInterfaceSubClass      0 No Subclass
      bInterfaceProtocol      0 None
      iInterface              4 Sample HID
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.00
          bCountryCode            0 Not supported
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength      27
          Report Descriptor: (length is 27)
            Item(Global): Usage Page, data= [ 0x00 0xff ] 65280
                            (null)
            Item(Local ): Usage, data= [ 0x01 ] 1
                            (null)
            Item(Main  ): Collection, data= [ 0x01 ] 1
                            Application
            Item(Local ): Usage, data= [ 0x02 ] 2
                            (null)
            Item(Global): Logical Minimum, data= [ 0x00 ] 0
            Item(Global): Logical Maximum, data= [ 0xff 0x00 ] 255
            Item(Global): Report Size, data= [ 0x08 ] 8
            Item(Global): Report Count, data= [ 0x08 ] 8
            Item(Main  ): Input, data= [ 0x82 ] 130
                            Data Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Volatile Bitfield
            Item(Local ): Usage, data= [ 0x02 ] 2
                            (null)
            Item(Global): Report Count, data= [ 0x08 ] 8
            Item(Main  ): Output, data= [ 0x82 ] 130
                            Data Variable Absolute No_Wrap Linear
                            Preferred_State No_Null_Position Volatile Bitfield
            Item(Main  ): End Collection, data=none
      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              32
Device Status:     0x0000
  (Bus Powered)
============================================================================

 >> i.e. the usbhid module gets loaded and it gets control over the
 >> USB port (instead of thecypress_m8 driver), and creates the device
 >> node /dev/usb/hiddev0

 SV> This would be normal for an UPS with USB interface, if the device
 SV> name would not contain "USB to Serial"...

yup - but it does contain "USB to Serial" so it should appear as a
plain serial port device node?

 >> my question is - could the cypress_m8 driver (or other driver) be
 >> used with this controller (device id is 0665:5161) to make it look
 >> as a plain serial device?

 SV> I have tried to do this with an Ippon SmartWinner 1000 (don't
 SV> remember the exact device ID) by adding the device ID to the
 SV> table in cypress_m8, but it did not work - apparently this device
 SV> is different.  Actually, it was even worse than "does not work" -
 SV> I have got a kernel oops in cypress_m8; I had no time to debug
 SV> this, and just attached the UPS to a serial port.

maybe i'll have to do that too, but i hope that this problem could be
solved and it would be possible to use USB... :)

Best,
v.


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to