From: Vojtech Pavlik <vojtech@suse.cz>
To: mightyquinn@letterboxes.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Make kbtab play nice with wacom_drv in Xorg/XFree86
Date: Wed, 20 Oct 2004 15:04:47 +0200 [thread overview]
Message-ID: <20041020130447.GA8086@ucw.cz> (raw)
In-Reply-To: <1098271641.26932.12.camel@sayuki>
On Wed, Oct 20, 2004 at 07:27:21AM -0400, Dave Ahlswede wrote:
> In its current state, the kbtab driver can be made to work with the
> XF86/Xorg Wacom driver, but only once per modprobe. If X is restarted,
> the driver won't report any input events. This is because the driver
> always reports the pen tool as being in use, and the information doesn't
> seem to be passed after the first time the device is opened.
>
> This patch fixes the issue by causing the driver to briefly report the
> pen not in use each time the device is opened.
It's a bug in the X Wacom driver that it doesn't check the initial state
of the tool. It should use EVIOCGKEY() to do that.
A good way to get this working in the driver would be report the PEN
tool as not in use when the position is invalid (the pen is not within
reach), if that is possible with the hardware. It's what the bit should
signify.
> Also, while the specs say the tablet is supposed to have 256 levels of
> pressure sensitivity, it only seems to report 0-127 on both tablets that
> I have access to. This patch changes the reported bounds to cooperate
> better with Gimp 2.1.
No problem with that.
> To actually use this in X, it may require the latest stable driver from
> http://linuxwacom.sourceforge.net
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2004-10-20 13:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 11:27 [PATCH] Make kbtab play nice with wacom_drv in Xorg/XFree86 Dave Ahlswede
2004-10-20 13:04 ` Vojtech Pavlik [this message]
2004-10-20 15:55 ` Dave Ahlswede
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041020130447.GA8086@ucw.cz \
--to=vojtech@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mightyquinn@letterboxes.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox