On Wed, Oct 7, 2009 at 5:02 PM, Peter Hutterer <span dir="ltr"><<a href="mailto:peter.hutterer@who-t.net">peter.hutterer@who-t.net</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div><div></div><div class="h5"><br> </div></div><a href="http://cvs.fedoraproject.org/viewvc/rpms/linuxwacom/devel/linuxwacom-0.8.2.2-HAL.patch?revision=1.1&view=markup" target="_blank">http://cvs.fedoraproject.org/viewvc/rpms/linuxwacom/devel/linuxwacom-0.8.2.2-HAL.patch?revision=1.1&view=markup</a><br> not for the faint of heart.<br> <br> when cleaning up you have to make sure you're only cleaning up those devices<br> that you've initialized yourself, otherwise you're going to top the server.<br> i'm not sure if I can recommend the above at all, mjg59's HAL trickery was a<br> lot nicer but then again, udev.</blockquote><div><br>Then, my question is: can we assume, with xserver 1.8 and later, xf86WcmInit (the device initialization routine) will only be called by your libudev input-hotplug mechanism? Or in another phase: do you still allow users to define input devices through xorg.conf? <br> <br>If xf86-input-wacom will only be Init'ed by libudev input-hotplug, I can "fix" my driver by creating all devices inside the Init. Then the driver will cleanup itself in UnInit. I think I like this approach if you guys are willing to take the risk of Wacom blowing up the server :).<br> <br>Ping<br><br><br></div></div><br>