> DRI, from Mesa CVS, still builds, but falls back to indirect rendering since > it needs DRM 1.22.x to run. > > Isn't it possible to only make newer functionality in the DRI drivers depend > on newer DRM? This way, users stuck with a particular version of the DRM > still have functional DRI drivers, even if they are missing out on newer > features of the driver?
For any other driver than r300 this is done, I don't want to do this for r300 as it is an experimental driver, and having a lot of backwarrds compat in the Mesa driver during development is only going to make it look uglier for no real gain.. I guess it was my kcmdbuf changes that broke radeon on FreeBSD, they shouldn't be that hard to fixup.. Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie Linux kernel - DRI, VAX / pam_smb / ILUG ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
