The intricacies of inter module registration were not at first apparant.. the latest fix only does an inter module get/put for the first device in each driver...
let me know how this one gets on .. Dave. > > Still can't unload it. It seems the problem is that the kernel thought the driver is > in > use, and did not even call the clean-up code. The debug msg follows: > > [drm] Debug messages ON > [drm:drm_probe] > [drm:i830_stub_register] > [drm:i830_stub_register] calling inter_module_register > [drm:i830_stub_getminor] info count increased 1 > [drm:i830_ctxbitmap_next] drm_ctxbitmap_next bit : 0 > [drm:i830_ctxbitmap_init] drm_ctxbitmap_init : 0 > [drm] Initialized i830 1.3.2 20021108 on minor 0: Intel Corp. 82852/855GM Integrated > Graphics Device > [drm:drm_probe] > [drm:i830_stub_register] > [drm:i830_stub_register] already registered 1 > [drm:i830_stub_getminor] info count increased 2 > [drm:i830_ctxbitmap_next] drm_ctxbitmap_next bit : 0 > [drm:i830_ctxbitmap_init] drm_ctxbitmap_init : 0 > [drm] Initialized i830 1.3.2 20021108 on minor 1: Intel Corp. 82852/855GM Integrated > Graphics Device (#2) > -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
