khaqq wrote:

On Tue, 06 Dec 2005 13:13:35 +0100
Roland Scheidegger <[EMAIL PROTECTED]> wrote:

vehemens wrote:
Posting my latest DRM and Mesa patches in case they should prove useful to anyone else. They are to head as of early Saturday.

I moved the CP idle outside the while loop in radeon_state.c. I think it may apply to the R300 as well as there is an "if R300 idle command" in the Xserver RADEONEnterServer function.

I have not tried removing the DRM changes since adding the Mesa change. Just sticking with something that doesn't lockup.
I'm still thinking it just doesn't really make sense the rv250 would need the pairwise tex emit. Apparently, it's not needed for a lot of people (my own rv250 If never locks up like that) so I guess there's more to it. One reason which comes to mind why some cards lock up and others don't (apart from timing differences due to cpu/chipset) would be different bioses on the cards - there have been issues like that wrt to cache programming in the past.

Probably not. My FireGL8800 used to crash a lot about one year ago while ajax' never crashed. And as far as I can tell, there is only one BIOS for
that card. ( http://www.techpowerup.com/bios/?search=8800&Submit=Search )
BTW, a friend of mine reports 6.8.2 stable with his 8800, while it did not
work on my machine.


That site is probably far from exhaustive. I know at least two bioses for the 7000 that are not listed there. And I've seen radeon caching issues solved by bios updates in the past.

Also, you don't happen to have fast writes enabled ?

Stephane




-------------------------------------------------------
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://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to