> How about an Input and USB DDK (Official or not)?  I seem to recall that Erick
>  Muis had an "Unofficial" Input DDK but I am not sure if it works with a USB 
> device.  This particular USB touchscreen controller is also HID-compliant but 
> it won't calibrate properly via the calib program.
> 
> Rob


Hi Rob,

The last update I did to the driver should support HID complaint screens.  What happens when you run:

devu-touch &
...wait a moment for the driver to start
Input generic fd -d/dev/usbtouch0 &

Does anything happen? if so, what?  Could you post the verbose output from Input

The DDK does not have any usb framework in place, however what you can do is if the devu-touch driver does not work, is 
grab the USB DDK and then write a quick driver that takes the data and converts it to the generic protocol format (as 
seen below).  The Input driver can then attach to it and there will be no need to change the Input driver itself.

Please let me know if this helps or not.

Best regards,

Erick

/*====================================================================
    
  Generic interface for non serial/ps2 touchscreens
    
  This is the generic protocol that is expected.  The external driver
  must use the following protocol in order for the generic driver to
  function correctly.  The number of bits is not critical.  This can
  be changed via the command line option -B to specify the number of
  bits for each coordinate.  The default is 14.  If you do not use
  all 14, make certain that the values not used are 0.
            
                  MSB             Bits               LSB
  Data Sequence    7    6    5    4    3    2    1    0
  ------------------------------------------------------
  S-Byte 1         1    S6   XXXXXXXXX Reserved XXXXXXXX
  X-Byte 2         0    X6   X5   X4   X3   X2   X1   X0
  x-Byte 3         0    X13  X12  X11  X10  X9   X8   X7
  Y-Byte 4         0    Y6   Y5   Y4   Y3   Y2   Y1   Y0
  y-Byte 5         0    Y13  Y12  Y11  Y10  Y9   Y8   Y7
  ------------------------------------------------------
            
  S0-S5     Reserved
  S6        Proximity        1 = Touchscreen is being touched (a
                             touchdown or a continued touch).
        
                             0 = Touchscreen is not being touched (a
                             touch liftoff or inactive).
    
  S7        Packet           Always 1. 
            synchronization

====================================================================*/