On Tue, May 01, 2012 at 06:57:59PM +0300, Nikolai Kondrashov wrote:
> On 05/01/2012 03:56 PM, Nikolai Kondrashov wrote:
> >On 05/01/2012 03:44 PM, Nikolai Kondrashov wrote:
> >>I would very much like to have a single class for generic tablets instead.
> >>They're all very similar and the evdev interface is capable of providing all
> >>the required information about them. It does that for all the tablets
> >>handled by hid-waltop, hid-uclogic and hid-kye drivers, at least.
> >>I've been attempting to implement this maybe twice in the past, but didn't
> >>have time or dedication to finish it.
> >Sorry, I confused libwacom classes with wcmUSB.c "protocols". I was talking
> >about the latter here. However, it probably applies to the former as well.
> I should really think and read the source before posting. I meant "models",
> actually, sorry. I.e. usbBamboo, usbIntuos4 and others, and how they are
> shoehorned on non-Wacom tablets. These should really be just a set of
> Further, I don't see the necessity to list all the models and their
> descriptions in xf86-input-wacom, and then in libwacom, while the kernel
> could provide all this and be the ultimate source of the information.
the kernel gives you some information but it's by far not enough for
GUI configuration tools. For example, which button controls the ring modes
on the Intuos4? What's the physical layout of the buttons on the pad? Which
styli are compatible with a Cintiq 21UX2? These are questions that
The kernel is good at enumerating, but bad at telling you more specific
information. Plus, it requires privileged access to the device files.
fwiw, I've had a short go at switching the X driver to use libwacom at some
time but didn't get far. libwacom wasn't ready then and the driver is too
entangled with model numbers etc. Anyone sufficiently optimistic can have a
go, but it won't be a small undertaking :)