This is very interesting and useful. Seems it's already showing some areas where
improvement is required in the R300 driver.
I'd suggest getting an account on freedesktop.org and a Git repository there. :)
Sourceforge is... less than reliable.
-
http://bugs.freedesktop.org/show_bug.cgi?id=10303
--- Comment #5 from [EMAIL PROTECTED] 2007-03-16 20:09 PST ---
I agree with that. If there are no objections I can change the vendor string
for R300. I think that R300 does still use some Tungsten Graphics code, but it
should be accep
Hello,
back when I was actively working on DRI drivers almost three years
ago, I always felt uneasy about the fact that I didn't have an
extensive array of tests that I could rely on to test for regressions.
Now I've decided to do something about it. I've taken Glean and some
code from Mesa and w
http://bugs.freedesktop.org/show_bug.cgi?id=10303
--- Comment #4 from [EMAIL PROTECTED] 2007-03-16 19:41 PST ---
> I think it was Vladimir Dergachev who did a lot of the initial work, at least
> from looking at the R300 Sourceforge site, but I expect that a lot of people
> made signif
hi, guys,
I am trying to understand the DRI/DRM code. I know about
Linux, but have no knowledge of FreeBSD. Could you please
kindly help me on the following question about DRM on FreeBSD?
For FreeBSD, in drm_close(), there is the following code
to release drmlock in case that current process is d
