Bug 20871 (paulhelf)

Summary: (1) timeout error on startup, (2) driver outputs erroneous Axis 1 digitizing tablet board limit
Product: xorg Reporter: Paul Helfenstein <paulhelf>
Component: Input/calcompAssignee: Peter Hutterer <peter.hutterer>
Status: RESOLVED WONTFIX QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium CC: paulhelf
Version: 7.4 (2008.09)Keywords: janitor
Hardware: x86 (IA32)   
OS: Linux (All)   
URL: http://kubuntuforums.net/forums/index.php?topic=3102076.msg171676#msg171676
Whiteboard: 2011BRB_Reviewed
i915 platform: i915 features:

Description Paul Helfenstein 2009-03-26 00:01:00 UTC
Detailed documentation at URL given above.

(1) Calcomp DrawingBoard III digitizing tablet fails to initialize as xinput device at startup due to timeout error. From /var/log/Xorg.0.log:

(WW) Timeout while reading Calcomp tablet. No tablet connected ???
(EE) Unable to query/initialize CALCOMP hardware.

User fix in xf86Calcomp.c:  At line 787, change "int retries = 5;" to "int retries = 100;"

(2) After fixing (1), "xinput list TABLET" retrieves "7616" from the driver as the tablet axis 1 limit instead of the correct number, "24000".

User found error (missing line of code) in xf86Calcomp.c.  At line 608 change
         priv->max_y = (int)buffer[5] + ((int)buffer[4] << 7);

         priv->max_y = (int)buffer[5] + ((int)buffer[4] << 7)
                                        + (((int)buffer[3]&0x03)<<14);

(3) "xinput set-pointer TABLET" fails on calcomp tablet. 

X Error of failed request:  BadDevice, invalid or uninitialized input device
  Major opcode of failed request:  146 (XInputExtension)
  Minor opcode of failed request:  12 (X_ChangePointerDevice)
  Serial number of failed request:  12
  Current serial number in output stream:  12
Comment 1 Peter Hutterer 2011-10-17 02:02:10 UTC
Sorry, closing as WONTFIX. This driver is unmaintained and will not see further fixes.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.