From: Brian P. <br...@vm...> - 2010-01-08 14:42:48
|
rnddim wrote: > That bug sounds about right. But of course, it's unresolved. :( > > I suppose what makes me the maddest is that I can't find out where the > bug occurs. I'm hoping there's a line of code or two I can change in my > personal copy of Mesa to help counteract the problem, if it's a problem > with something beyond Mesa (which it seems like it is). > > Comparing my gears picture and the one on the Mesa3d homepage (which I'm > assuming is a snapshot of the correct gears output), this is what > happens (good output on mesa3d.org, bad output in my original attachment): > > Good Output -> Bad Output > Red Gear -> Green Gear (the one that may look cyan or light blue to some > in the picture) > Green Gear -> Red Gear (may look pink) > Blue Gear -> Alpha (transparent) Gear (it looks like a light gray-blue > gear, but that's transparency at work) > Alpha (No) Background (appears black) -> Blue Background > > Based on this, it's mostly likely that any RGBA color value is read as > GRAB. I wonder if there's anywhere in the Mesa source code, probably > where colors are first read, where I could insert an 'easy fix'. Possibly. Look through src/mesa/drivers/dri/r128/* for instances of MESA_FORMAT_*. Perhaps MESA_FORMAT_ARGB8888 should be PIPE_FORMAT_ARGB8888_REV, or something like that. See src/mesa/main/formats.h for the available pixel formats. I doubt that any of the active DRI developers have R128 hardware on hand so hopefully you can figure it out. BTW, you should use Mesa 7.7 if you aren't already. -Brian |