On Mon, 2004-10-11 at 18:37 -0700, Ian Romanick wrote:
I was trying to test the latest version of my ReadPixels work to make sure I didn't break anything on big-endian. However, it seems someone beat me to it in the Rage128 driver. :) In a nutshell, I can get one frame of gears, and then the 3D engine is toast. After that frame is drawn, gears is at 100% and X is unresponsive. When I kill gears, everything goes back to semi-normal. If I run another 3D program, I get an empty (just a frame!) window.
Looking at the output from R128_DEBUG=all, it appears to be stuck in r128EmitHwStateLocked.
Please provide a little more context - machine type (G4 I guess? Which model exactly?), AGP/PCI, versions of kernel/DRM/X, ...
It's a stock AGP G4. The card is the original Rage128. The kernel is the debian 2.6.8-powerpc kernel (dittor for DRM), and X is yesterday's X.org. The last time I did anything with that machine was about a month ago with a 2.4.25 kernel (and whatever X.org was current then), and it worked fine. I suspect the problems are caused by recent changes to the 3D driver.
Regular X stuff works fine.
That single frame of gears is also wrong. The colors are pinks and purples. I suspect this may just be a byte-ordering problem. I notice that the driver wants to use BGRA for primary color, but I suspect the hardware really wants ARGB. Ditto for secondary color / fog.
Yeah, there are endianness issues to work out in t_vertex.
:( If I can get the driver to not wedge, I'll start working on those.
------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
