public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Ahlswede <mightyquinn@charter.net>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Make kbtab play nice with wacom_drv in Xorg/XFree86
Date: Wed, 20 Oct 2004 11:55:02 -0400	[thread overview]
Message-ID: <1098287702.28045.9.camel@sayuki> (raw)
In-Reply-To: <20041020130447.GA8086@ucw.cz>

On Wed, 2004-10-20 at 15:04 +0200, Vojtech Pavlik wrote:
> 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.

I'll talk to the developer about that, thanks.

> 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.

Unfortunately, when the pen is out of bounds, the hardware simply stops
sending packets. I experimented with a change that would report no tool
in use when pressure was zero, but that made the tablet unusable. (It
would only track movement when the pen was being pressed to the tablet)




      reply	other threads:[~2004-10-20 15:58 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
2004-10-20 15:55   ` Dave Ahlswede [this message]

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=1098287702.28045.9.camel@sayuki \
    --to=mightyquinn@charter.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mightyquinn@letterboxes.org \
    --cc=vojtech@suse.cz \
    /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