On Sun, 2 Jun 2002 05:02, Danny Rathjens wrote: > Thank you. I had come to a similar conclusion, but was planning > on using EVIOCGID or EVIOCGNAME which I found in input/evdev.c > I see EVIOCGBUS defined in input.h but I do not see where it is actually > used. I have some patches that are queued with Marcelo for 2.4.20-pre, that make some changes to how all this works.
> I also noticed this commented line in evdev_connect() in evdev.c: > // printk(KERN_INFO "event%d: Event device for input%d\n", minor, > dev->number); > > I was thinking of just uncommenting it and adding dev->name and > dev->idvendor > to the output since I am lazy. But I guess the ioctl method would be > the most > proper, ;) Parsing logs is very error prone. Even more racy than an ioctl. > > If that doesn't help, perhaps you need to tell us what you are trying to > > do. > > I'm using a usb microtouch touchscreen for a linux-based kiosk > (http://www.wirespring.com is our company). For the X module to use it we > have to tell it which event stream to use. Up until now we had just > hard coded the value in XF86Config but now I need to programatically set > it so that it will work for different variations of keyboard/mouse/monitor. Interesting. Brad -- http://conf.linux.org.au. 22-25Jan2003. Perth, Australia. Birds in Black. _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
