Re: [PATCH 59/70] USB Input: Added kernel module to support all GTCO CalComp USB InterWrite School products
"Dmitry Torokhov" <[email protected]>
| Newsgroups | gmane.linux.usb.devel |
|---|---|
| Message-ID | <[email protected]> |
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? -- 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 _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel