Dnia 2009-11-30, pon o godzinie 11:52 +1000, Peter Hutterer pisze: [..] > I think there's stuff missing in the server to support this. I'd like to see > it working at runtime but haven't yet found the time to actually find and > fix it. > > no driver supports real module unloading because we've never had the need > for it. Until rather recently, the drivers didn't even support device > removal because the devices were static anyway. [..] Last couple days I was digging really deep in server and glibc guts and ... the server was/is ready to unload modules. It's not exactly clean (duplicating modules instead of using just one, UnloadModule called from IMHO wrong place and so on), but it works. The problem is that looks like glibc (dlopen, dlclose functions) are "too" smart. Unloading wacom module and removing it from disk doesn't remove it from memory, so after installing new version of wacom and loading it again I'm getting the old one. I'm going to ask on glibc-help for ideas how to force real unloading. I tried to play with ldconfig - no luck. The problem is no longer related to wacom development, but I wanted to close the thread. -- Przemo
------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ Linuxwacom-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
