Hi, after upgrading the DRM (it has been a while since the last cvs update) the Savage driver stopped working. I tracked it down to the DRM refusing to create multiple framebuffer-type mappings. If it finds an existing mapping it returns it instead of creating a new one. However, the Savage driver needs multiple framebuffer-type mappings. The real frame buffer is supplemented by a so-called aperture where front/back/depth buffers can be accessed at fixed addresses (independent of their actual locations in the frame buffer) linearly even if the framebuffer is physically tiled. This behaviour is controlled by a set of tiled surface registers (IIRC). The HwMC code makes yet another framebuffer-type mapping. :-/
Anyway, I suspect the behaviour of DRM(addmap) changed recently. The only addmap-related comment I could find on dri-patches is this: addmap-base-2 patch from Jon Smirl: sets up the DRM to have the ability to have permanent maps while the driver is loaded... Is it really necessary to limit drivers to a single framebuffer-type mapping? Regards, Felix | Felix Kühling <[EMAIL PROTECTED]> http://fxk.de.vu | | PGP Fingerprint: 6A3C 9566 5B30 DDED 73C3 B152 151C 5CC1 D888 E595 | ------------------------------------------------------- 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_idP47&alloc_id808&op=click -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
