Hi,
I use a same code than evdev.c to scan more than one device states. This
code is embedded in threads, one thread by detected device. The trouble
comes from the "read" function call: it freeze the thread execution
until the associated device state has changed (and doing so, others
thread
Hi all,
I just tried my new Wacom Graphire2 USB tablet and it works fine under
Linux. Yep.
I want to get all available informations about this device so a use
EVDEV with the sample application EVTEST.
Here is what I get:
***
Input driver version is 1.0.0
Input device ID: bus
Hi Vojtech,
> > > For this type of access, /dev/input/eventX was designed. It'll give you
> > > all you describe.
> >
> > I have tried it but I cannot make it work. I run it under kernel 2.2.18
> > and 2.4.0 (SuSE 7.1 installation). If it can work, I effectively think
> > its the better choice :-
> > I think its effectively a good choice for a standard mouse usage. But
> > when I want to use a grapic tablet (a wacom intuos for instance), I'll
> > need to get stylus pressure information as well as stylus unique ID. And
> > if I want to manage a complementary keyboard (a key pad for instance
> > I'm really desapointed by the fact that there is no simple way to dialog
> > with USB devices from the application level, assuming that all is build
> > for "standard" things (for instance, we want to show 2 cursors onto the
> > screen when 2 mouses are plugged...).
>
> You don't need to talk
Hi,
I try to get a HID report descriptor using lsusb from usbutils-0.8 package
for 3 devices:
1/ Microsoft Optical IntelliMouse
2/ a Sun mouse
3/ a Sun keyboard
and all is ok except on the HID report descriptor.
Here is what lsusb said to me for device 1/:
===
Bus 001 Device 00
Hi,
I want to build an application that can use multiple input devices at the
same time (typically two HIDs) for special kind of interaction (research
perspective), with the ability to detect new incoming devices.
All is ok to check for the last point (hot'plug) but I desesperatly try to
find
