On Mon, Nov 11, 2002 at 05:09:01AM -0500, Zephaniah E. Hull wrote: > On Mon, Nov 11, 2002 at 10:30:36AM +0100, Vojtech Pavlik wrote: > > On Mon, Nov 11, 2002 at 04:08:03AM -0500, Zephaniah E. Hull wrote: > > > > > The current state of affairs as far as being able to use > > > /dev/input/event<n> directly is, exceedingly suboptimal. > > > > > > To be blunt, under 2.4.x kernels the interface lacks ANY way to > > > determine which device you have if you have two identical devices. > > > > True, 2.4 kernels use a quite old input core codebase. I'm planning a > > backport from 2.5 as soon as I find the time to do it. > > > > > To make matters worse, while there /are/ ioctls to get the bus location > > > for 2.5.x kernels the #defines do not even exist for the 2.4.x headers. > > > > Obviously, they were added in 2.5. > > > > > This for a supposedly identical evdev protocol version. > > > > That only applies to the data layout read from /dev/input/evdev, not the > > actual interface, because you get an -EINVAL on an unsupported ioctl, > > while you don't get an error if you interpret the data layout > > incorrectly. > > Ok, this makes a bit more sense now. > > > > > Until this can be sorted out it is going to be /very/ problematic to > > > actually use the evdev interface for even mildly complex setups. > > > > You can do the backport yourself if you wish. Anyway, on 2.4, the input > > core is only used for USB and joysticks, which quite limits its > > capabilities. > > Ugh, I think I'll probably leave that to people who are more comfortable > kernel hacking then I am. > > > > > Zephaniah E. Hull. > > > (Back to trying to figure out how to get X to turn input drivers on and > > > off from outside signals.) > > > > In 2.5, /sbin/hotplug is called whenever a new device > > appears/disappears. It's a script. Add whatever you need to notify X > > about the device to that script. You can even connect to X via the X11 > > protocol and use some extension to tell it about the new mouse. > > In recent 2.4.x as well,
No. You get /sbin/hotplug called for USB devices, which is not exactly what you need. 2.5 will call it for Input devices as well. This is different, because you get all the info you get from the ioctls passed in shell variables. Also it works in an unified way for all input devices, be them USB or PS/2 or ADB or whatever ... (For USB devices you get both the USB connect and Input connect) > the real fun is the X side of it, which some > days I /really/ wish had some documentation. -- Vojtech Pavlik SuSE Labs _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
