Alan Grimes wrote:
Software rendering: WORKS (about 1.2 fps, if that..)
ATI Mach 64 (PCI): WORKS -- minor image degradation as would be
expected of a card of that vintage... (around 5 fps...)
ATI Rage 128: Works, slows down dramaticly in some areas, has a number
of visual artifacts.
MSI 9250: Some demos work, ones that don't contain portals to other
"fields". Ones that do have portals, segfault IN THE DRIVER CODE.
A gdb backtrace might be useful.
> I really don't understand the information flows within the Mesa
> driver.. How do I tell which parts of the code are in use on my
> platform and which are only for software rendering?
Typically, stuff in src/mesa/main is shared by all drivers, opengl state
handling and such. src/mesa/swrast is used only for software rendering,
BUT you can hit that code too with hw acceleration, if you hit a
fallback somewhere (the most common case is probably if you read/write
directly to the framebuffer, most if not all drivers implement this as a
fallback). All hw driver specific code is in src/mesa/drivers/dri, in
your case obviously in the r200 directory.
Roland
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
