On Wed, 4 Apr 2001, Stefan Seefeld wrote:
> hi there,
>
> I'v patched the linux evdev driver, following the sample code from the
> evtest applet. There are a couple of questions, though. Some of the numbers
> used (sizes, mostly), seem pretty arbitrary, and in the context of the
> evdev conventions (from what I could gather) even wrong.
> The stylus uses buttons and valuators, but these are not contigeously enumerated.
> What should the 'num_axes' member report ? the number of (absolute) valuators ?
> The highest id ? Further, valuator events seem to group a a set of valuator values
> together (seems to make sense, since they are often bundled into the same device).
> But why is 'values' 32 integers long ? The /dev/input/event0 driver supports more,
> so we have to be prepared for a clash.
>
> The fixes I applied are basically these:
>
> * I set the 'num_axes' to the highest id that corresponds to a valuator
>
> * I report valuator info for all valuators (range, number, long name)
>
> So, at the given state of GGI I must ask: is anybody interested in these changes
> at all ?
I can imagine, that merely people are interested in that, who have a
Wapcom intou, too.
Please give as much as details about what it needed in order to test
your work. I forward your description to a linux-user-group. I think
there might be some interested in that...
CU,
Christoph Egger
E-Mail: [EMAIL PROTECTED]
