Issue with uncommon pointing device.

[Drew Ogle]

Ah, missed that.

What it reports is :
Input device ID: bus 0x3 vendor 0x46d product 0xc626 version 0x110
Input device name: "3Dconnexion SpaceNavigator"
Supported events:
  Event type 0 (Sync)
  Event type 1 (Key)
    Event code 256 (Btn0)
    Event code 257 (Btn1)
  Event type 2 (Relative)
    Event code 0 (X)
    Event code 1 (Y)
    Event code 2 (Z)
    Event code 3 (?)
    Event code 4 (?)
    Event code 5 (?)
  Event type 4 (Misc)
    Event code 4 (ScanCode)
  Event type 17 (LED)


The 3 unknown codes are the twist sensor ( code 5 )
and the tilt for x and y.

On Tue, Oct 28, 2008 at 9:59 AM, Matthew Garrett <mjg59 at srcf.ucam.org>wrote:

> On Tue, Oct 28, 2008 at 09:50:56AM -0400, Drew Ogle wrote:
> > xinput list doesn't show the device, so I can't use evtest.
>
> evtest is run against the /dev/input device node, not against an xinput
> device.
>
> --
> Matthew Garrett | mjg59 at srcf.ucam.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.x.org/archives/xorg/attachments/20081028/1afa58d3/attachment.html>