From: "Stefan Brüns" <stefan.bruens@rwth-aachen.de>
To: linux-input@vger.kernel.org
Subject: RFC: making the aiptek.c tablet driver xf86-input-wacom compatible
Date: Wed, 26 Jun 2013 00:02:36 +0200 [thread overview]
Message-ID: <1448859.K0oxtlBRpL@pebbles> (raw)
Hi everyone,
I have started to modify the aiptek tablet driver to be compatible with the
xf86-input-wacom driver.
Motivation:
First, as wacom dominates the market, most configuration frontends are for
wacom, desktop integration only exists for wacom, and most application
developers only test with wacom tablets.
Second, the xf86-input-aiptek driver seems to be unmaintained, at least
opensuse has dropped it from distribution, and xf86-input-evdev is no
sufficient replacement.
So for me there are two possibilities, either replicating all the work done
for the wacom driver in the xorg stack and above, or just making the the
aiptek driver mimic the output of the wacom kernel driver - I have taken the
second option.
Currently, I am cleaning up my changes, and I am investigating some bugs in
the original driver parsing the reports from the device.
I have tested my Aiptek 6000U with the xf86-input-wacom driver, and it is
working fine in Krita, Inkscape and The Gimp, configuring the tablet via
kcm_wacomtablet (KDE configuration module).
If anyone is interested, I will send my patches to this list after the
cleanup.
Regards,
Stefan
--
Stefan Brüns / Bergstraße 21 / 52062 Aachen
phone: +49 241 53809034 mobile: +49 151 50412019
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2013-06-25 22:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 22:02 Stefan Brüns [this message]
2013-06-26 8:17 ` RFC: making the aiptek.c tablet driver xf86-input-wacom compatible Benjamin Tissoires
2013-06-27 21:01 ` Peter Hutterer
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=1448859.K0oxtlBRpL@pebbles \
--to=stefan.bruens@rwth-aachen.de \
--cc=linux-input@vger.kernel.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