On Tue, Oct 23, 2001 at 09:17:48AM +0200, O. Beaudoux wrote: > > > 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 to the USB devices directly for that - just open > > /dev/input/mouse0 and /dev/input/mouse1 and read the data ... > > 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. For a more low level access, /dev/hiddevX was designed. You shouldn't need direct USB access. > Dealing with /dev/input/mouseX and so on seems to be not so > precise than an USB direct access. > > So I prefer to use the patch mentionned in Dan Streetman and David > Brownell... or wait for its integration in futur 2.4 kernels... 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. -- Vojtech Pavlik SuSE Labs _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
