For the future if you do not have the input ddk (not really an official package just something I put together that 
allows you to build the stuff) you can create your own driver using a resource manager and then convert the data packets
 into the 'generic' protocol that the Input driver supports:

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

  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

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


Then start the Input driver using the generic module and point it to your resmgr mount point and then it will handle the
 rest.

Best regards,

Erick