On Mon, Dec 08, 2014 at 05:38:52AM +0100, [email protected] wrote: > Hi, > I have written an xorg module for a proprietary ethernet based virtual > keyboard. > I can load that driver only witch a matching rule on the actual input path > (dev/input/event4) > I tried to match by tag (InputClass... MatchTag) with a udev assigned tag on > /dev/input/event4), however that fails.
you can match on the device name, the pid/vid, etc. surely one of those will be sufficient to match? if the tag matching doesn't work then that could be a bug, but I doubt it, we haven't touched that code in quite a while. > A more flexible approach for matching an xorg module to a device would be > something like "tentative module loading". > The user supplied device_control function (Bool (*device_control) > (DeviceIntPtr device, int what)) would return a new constant, indicating "not > my business". > In that case xorg server would load other devices (if present) for the given > module. no, what you have is likely a local misconfiguration, no need for the server to get more complicated here. Cheers, Peter _______________________________________________ [email protected]: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
