UFO Ai 2.4 works quite well on kernel 3.7-rc3 + mesa git + ati git driver if anyone asks meQuite a development from the time I first tried it on the E-350 - r600 driver in mid 2011
"Bring it on" aliens. Flamethrowers are wating![]()
UFO Ai 2.4 works quite well on kernel 3.7-rc3 + mesa git + ati git driver if anyone asks meQuite a development from the time I first tried it on the E-350 - r600 driver in mid 2011
"Bring it on" aliens. Flamethrowers are wating![]()
That's funny because I use the ivy bridge drivers too and kwin opengl compositing has been totally broken for weeks now. First, it was awfully slow and kept occassionally stalling everything.
(Now it immediately crashes when I change to opengl compositing but I think a X restart / reboot will fix it).
kwin gles works better, but is graphically very glitchy, doesn't redraw the screen well enough.
Last edited by ChrisXY; 10-31-2012 at 07:32 AM.
Since when is it funny that stuff that works for some doesn't work for others? It's just life as we know it on Linux.
In my case, 2.19 was totally unusable (had to stick with 2.11 or 2.12 for a while), 2.20 is ok, but I can't turn on desktop effects. I'm stuck with F16, so that may be part of the problem though.
I've never had a problem with KWin and Ivy Bridge. Smooth as silk. Filed a bug?
Actually, I haven't had a problem with KWin and r600g for years either. The problem of r600g is not stability, it's features and performance.
r600g won't have many new features for HD2000-HD4000 anyway. Only these are missing there:
- geometry shaders
- multisample textures (DONE in the driver, but core Mesa can't do it yet)
- uniform buffer objects
- texture buffers objects (this is being worked on)
Once this list is done, there won't be any OpenGL feature that the hardware can do that the driver doesn't implement. Then it'll be mostly just about performance.
You are right, and I should have written "FLOSS radeon drivers".
What is missing is not really a part of OpenGL, but they are still missing: dynamic power management, UVD, OpenCL. Some belong in the kernel, some in Mesa, etc.
Since the GPU drivers are spread between different projects now, it's harder nowadays to be specific![]()
I think that this has possibly been fixed due to a KWin bug.
https://bugs.freedesktop.org/show_bug.cgi?id=55998