On Wed, 12 Jan 2005, Rune Petersen wrote:
Vladimir Dergachev wrote:
Really ? Could you double check this ? It would be a big surprise if MM I2C bus access is interfering with anything.
I just did, and yes it still dies a horrible death.
Could you try to track down what in radeon_video.c causes this ? Just comment out (with #if 0 .. #endif) arbitrary chunks of code until you zero in on whatever causes the lockup.
The card is used as an RV350..
result:
bitblt & tex-bitblt is drawn perfectly, the rest apart from drawing the intended have a yellow band at the bottom half of the screen.
Great ! Btw, the yellow band is meant to be there and is the depthbuffer - it was positioned to overlap with framebuffer.
I wonder whether r300_dri.so will work for you now.
it does mostly, I just wanted to try running the card as RV350 instead of default R300, before "reporting" back =).
he strange thing is I get an error and the message: "disabling 3D acceleration", but I still get ~2400 fps with glxgears.
it means it is working ;) the message "disabling 3D acceleration" is from the times the driver only did color and depth clears. I should really hunt it down and change it to "installing fallback paths" or something.
best
Vladimir Dergachev
Rune Petersen
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt -- _______________________________________________ Dri-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dri-devel
