On Thu, Jun 17, 2010 at 05:59:38PM +0300, Timo Aaltonen wrote: > On Thu, 17 Jun 2010, Alexia Death wrote: > > Im looking for pointers on how to set up a sane testing environment > > for any driver testing. Having to stop whatever I do in my X and kill > > it to load the updated driver, that might be badly broken and kill X > > does not seem to be the sane way and Im too attached to my X to do the > > actual development in shell with emacs... > > You don't need to kill X if the driver is autoloaded via udev. Unplug the > device, see that the driver is unloaded and then hack-build-install-plug. > > unless the driver is not actually unloaded, can't remember if I've tried > the above in the past.
it's a libc bug, IIRC. was on this list a couple of months ago. the X server does the right thing with unloading, but the .so is kept around anyway. so yes, you have to drop your reference to it, and to do this you need to restart the server. Cheers, Peter ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
