On Tue, Oct 23, 2001 at 09:47:31AM +0200, O. Beaudoux wrote: > > > 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 > > > think its the same problem. > > > > 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 :-)
What's your problem with it? I'll help if I can. > > For a more low level access, /dev/hiddevX was designed. You shouldn't need > > direct USB access. > > I know about it but it seems that (by default), every few devices are > accessible through it... Yes, by default only non-input HID devices are available through it. This can be changed, though. > > It's not nice if a simple lsusb disconnects all devices and reconnects > > them again after exiting. It'll cause a lot of mess, because the devices > > will be assigned different numbers and running applications will lose > > access to them. > > I understand your comments and fully agree on. The fact is I just want to > make some research stuff about HCI with our engineer students for this year. > For a futur and "nice" implementation of HID access, I find the best solution > is to wait for more "stable" things under new kernel versions... ? Yes, I hope this'll all be solved in an elegant way eventually. -- Vojtech Pavlik SuSE Labs _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
