[Dri-users] Status of Savage Driver

[Robert S. K. <rs...@ds...>]

Hello,

I'm writing to ask about the status of the savage driver and DRI in X.org.

I have a Linux machine that I use for MythTV (a homebrew PVR app) 
running FC3 with an onboard Prosavage DDR chip in it.

A while back (FEB '05), I spent the time to get DRI working on my X.org 
install.  It worked great, but at the time caused other performance 
issues when dragging windows that made the benefits of accelerated 
openGL not worth it.  The issue was that when dragging windows around on 
the screen, or under Myth when I play video, there is a spike in my 
Xserver's CPU utilization.  Without DRI, Xserver utilization never broke 
10% or so.  When DRI was enabled, it would jump to as high as 50% 
utilization.

At the time, Felix Kuhling mentioned that the driver was essentially 
very inefficient and didn't make use of IRQs or DMA to speed things up.

My question is if this has been resolved in recent work with DRI and 
x.org has resolved either of these two issues.  I've looked through the 
archives but haven't seen any direct reference, but I noticed that there 
has been a fair amount of savage work in the interim.

Can anyone provide some insight?

Also, when I compiled DRI in the past, I had to get the CVS version of 
X.org, CVS Mesa, and CVS DRM and build all the parts separately.  I've 
noticed that X.org now includes versions of Mesa and DRM in its tree.  
Can I use these to compile DRM for the Savage?

Rob