On Tuesday 13 February 2007 16:15, Jeremy Roberson wrote: > Well, it seems the XInput Hotplug is still going to be a bit of a mess > for a while and some of the distributions that we are targeting have > updated kernels but, are still using XFree86 so we want to remain as > compatible as possible. > > > Our current X driver doesn't care what device node it's attached to, in > fact it's attached to /dev/null. When the X Driver is loaded, it > allocates shared memory that it uses to communicate with our Device > Manager. > > Our USB Devices are blacklisted so that we can use our own USB kernel > module to create and manage the device node. > The Device Mgr listens for a signal that a new device node has been > created in /dev/input/ and then we enumerate it and check to see whether > it's one of our boards etc. As low level input events are generated by > our boards, the Device Manager retrieves them and then passes them onto > our X Driver via the shared memory which, in tern formats the low level > input events into XInput events and then posts them on the XInput event > queue. > > Not sure if this answers your question or not. If not, please let me > know.
Yes it does. So in your case it would be Device Manager who issues EVIOCGRAB ioctl on the device node once you enumerated it. This will stop X mouse driver from also getting events while still allowing DM to process them and convert to XInput. -- Dmitry ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
