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.
Didn't R600 IRQ support land in some of earlier RCs?
No, the two "new" firmware files that are required (R600_rlc.bin and R700_rlc.bin) are not included in the kernel so far. They are required to start the system though, so ATM the kernel will likely appear "broken" to several users until that firmware is officially shipped, too (or until users start using google or other search engines and find the solution: download the files from the net and activate the correct setup switches before building the kernel).
The kernel is not accepting any new firmware and existing firmware is slowly being moved out of the kernel. There is a Linux firmware tree where things will eventually end up, but for now you need to get it from: http://people.freedesktop.org/~agd5f/radeon_ucode/
KDE's Kwin window manager has some glitches, but I don't know if it's Mesa or DRM.
Sometimes a window gets a thick Yellow or Black border around it. If you focus or unfocus the window it goes away, but it'll eventually come back on another window.
Jepp, the same over here. On my rv670 I do especially get "black rectangles" where eg the currently running program is shown or the whole area for switching the current workspace or the clock just shown that black rectangle. Things somehow seem to be related to stuff like transparancy. Clicking once on the desktop tends to fix those things. And when borders around progs are shown clicking on a different prog also fixes this issue.
Sorry, but it is rather hard to provide you with some way to definitely be able to reproduce it. But at least here using kwin (kde 4.3.x atm) I do see those issues. Nothing that stops you from normal working, just some glitches. Those only happen with KMS active and it makes no difference if acceleration method for desktop effects is xrender or opengl. So I think the "fault" is somewhere in the KMS part, not in mesa or libdrm itself, though I am not sure at all.
Currently I am running 2.6.33-rc5, but I had the same observation with KMS in 2.6.32*. Using mesa, libdrm and xf86-video-radon from git-master.
I personally think KMS has quite a way to go on catching up with UMS in performance. As I have hacked away on both sets of code to improve performance by any means I just don't see where KMS is going to get it from or where the core bottle neck is. Minor improvements are possible however.