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. On Tue, 2007-02-13 at 09:49 -0500, Dmitry Torokhov wrote: > On 2/12/07, Jeremy Roberson <[EMAIL PROTECTED]> wrote: > > Maybe. Attached is a high level diagram of the architecture that we > > used in order to prevent the end user from having to modify the x config > > file manually whenever they add a new digitizer. With this architecture, > > the end user doesn't need to know what device node the digitizer is > > attached to and the X config file doesn't need to be constantly > > modified. So, as far as the end user is concerned the Digitizers are > > hot plug-able. > > > > So, to my question. In order to use EVIOCGRAB ioctl in my X driver, > > don't I have to already know the device node that the digitizer is > > attached to? > > > > Yes, you would need a device node. If X would support hotplug then > different input drivers could query new device ID (struct inpuit_id) > and capabilities and make decision whether they want to attach to it > and whether they want exclusive access (EVIOCSGRAB). > > In absense of hotplug in X (is it still absent btw?) your device > manager will need to perform the same functions. > > How does current version of your device manager know what device nodes > to attach to? > -- Jeremy Roberson Software Engineer GTCO CalComp "Do not go gentle into that good night, Old age should burn and rave at the close of the day; Rage, rage against the dying of the light." - Dylan Thomas Note: The information contained within this electronic transmission is intended by Interwrite Learning for the use of the named individual or entity to which it is directed and contains confidential and/or privileged information. It is not intended for transmission or receipt by anyone other than the named addressee or entity. It should not be forwarded or copied to any unauthorized persons. If you have received this is error, please remove it from your system, without copying or forwarding it and notify the sender by return email. Thank you. ------------------------------------------------------------------------- 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
