Ok. I've committed it on a new savage-2-0-0-branch. Hopefully this driver works for you. I didn't get display corruption with this one but there were a few lockups when switching back from another virtual terminal or when moving a 3D window around. Unfortunately it happens only occasionally. I'm going to look into these issues next.
Hmm ..., I just noticed that 3D isn't currently enabled on your chip ID (8A22). And I also saw a compile-time switch for SAVAGE4 in savage_bci.h. Feel free to play with these. Eventually we should make this distinction at runtime.
Ok, i'll work in that, in fact is the only one i can test :)
BTW, from which code drop is the 3D driver you're working with?
I was working on the 3D code at savage-1-0-0-branch, glxinfo reported the it was using direct rendering but glxgears hang the computer, i tried to debug and i discovered that a pointer was pointing to an unalloc'ed memory address witch caused the hang, nothing else.
bye.
Rafael M�ximo
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
