If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
No announcement yet.
ATI R600/700 OSS 3D Driver Reaches Gears Milestone
Yeah, now it only flickers where the notification is. Sometimes a bit annoying if you're trying to concentrate and the notification jumps in and out in less than a second intervals before calming down.
Indeed. I think this is due to the design of the compositor on XP (e.g. it shouldn't happen if you disable menu fade-in and shadow effects). As far as I can tell, Vista and higher don't suffer from this issue anymore - at least not when Aero is enabled.
More like microseconds, actually. 1080p is ~7.9MB per frame, which translates needs something between 80μs (ultra high-end GPUs with GDDR5 memory) to 4ms (ultra low end Intel IGPs with single-channel DDR2 shared memory).
It's more than 80us, more like 200uS or 0.2mS on a board with 256-bit GDDR5 memory. Remember that the data has to be read and written back (so 2 accesses), and that the GPU is alternating read and write bursts. The bandwidth number you see in reviews is the theoretical maximum for infinitely long bursts.
I was thinking of "high end" as starting somewhere around 50-60GB/s peak bandwidth, say 3850/4850 and up, where the copy time would be 0.4-0.5 mS. I agree that if you go right up to 4870/4890 you can probably cut that in half again.
Decided to note it here so it gets documented: if you're having a fullscreen black screen with Fedora 11 when running glxgears with the r600 Mesa driver, try instead running progs/demos/gears from your Mesa build tree. (assuming you compiled the demos) It's the exact same program, just a newer version. It seems Fedora 11 got shipped with a glxgears that features a bit odd with at least this particular driver.
Since gears is in progs/demos and glxgears is in progs/xdemos, my thinking was that gears uses direct rendering and glxgears uses GL through X, ie indirect rendering.
Oh, very good notion. The major difference (in terms of what the end-user sees, not in terms of implementation) between the two (Fedora glxgears vs progs/demos/gears, will still have to test the one in xdemos, I guess) is the black screen on some cards, both render just as wrong on r6xx.
On my rv620 colours seem correct in most apps now except varray. Also getting the black screen in glxgears but not gears. Still getting some corruption in the gears (seems like size is jumping around), seems to happen only when EXA is drawing.
Anyways, now I can give back the rv770 I borrowed from QA
- glxgears looks like a simple graphictask. So I don't understand why it is a milestone? I mean, isn't there alot of work to be done yet? Or is it really a milestone, because we can say the main 3d-part of the driver is now working, and it now only need prober opengl support?
The driver was pretty much fully written in April. We were just starting to bring it up when it became obvious we needed to move it over to the radeon-rewrite code base, which in turn meant that we had to *understand* the radeon-rewrite changes
Getting glxgears working means that most of the major blocks of the driver are running, including the shader compiler / assembler (since mesa uses a vertex shader to emulate fixed-function TCL on GPUs that don't have fixed function). Gears doesn't exercise textures at all AFAIK, but it lights up most of the other areas.
The driver was pretty much fully written in April. Getting glxgears working means that most of the major blocks of the driver are running, including the shader compiler. Gears doesn't exercise textures at all AFAIK, but it lights up most of the other areas.
Aah I see.
But I shouldn't try this on a 2.6.30 kernel?