Bug 13040

Summary:

Make the "cursor" option in xorg.conf useful

Product:

xorg

Reporter:

Manuel Reimer <Manuel.Spam>

Component:

Input/hyperpen

Assignee:

Manuel Reimer <Manuel.Spam>

Status:

RESOLVED INVALID

QA Contact:

Xorg Project Team <xorg-team>

Severity:

normal

Priority:

medium

CC:

jeremyhu

Version:

unspecified

Keywords:

patch

Hardware:

All

OS:

All

Whiteboard:

2011BRB_Reviewed

i915 platform:

i915 features:

Attachments:

Description	Flags
Patch with my changes	none

Description Manuel Reimer 2007-11-01 08:19:01 UTC

The "cursor" option for xorg.conf is available, but gets resettet immediately by the "auto cursor detection" in "xf86HypReadInput".

My patch will disable this "auto detection" as soon as the "cursor" option is set in xorg.conf. This way, the setting in xorg.conf gets respected by the driver.

I also did minor cleanup (removed the "stylus" variable from global scope).

In future I may publish more patches, but this one has to be accepted first, as I forcefully need this. My tablet seems to have a minor hardware defect, which makes the auto detection fail (driver detects my stylus as mouse and as soon as I touch the panel, the stylus gets detected and driver switches to absolute, which makes the cursor jump).

Comment 1 Manuel Reimer 2007-11-01 08:19:53 UTC

Created attachment 12296 [details] [review]
Patch with my changes

Comment 2 Jeremy Huddleston Sequoia 2011-10-17 01:08:40 UTC

Can you please send your patch to xorg-devel for review.  Please base it on 
current git rather than a release tarball.  Use 'git commit -s' to commit your 
patch with your signoff, and use 'git format-patch HEAD' to create the patch.

Comment 3 Adam Jackson 2018-06-12 19:07:31 UTC

Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.

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.