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.

sorry i can't test this not because i do not have a measurement device i do have 1 and i'm willing to buy a better one but sorry i do not have a hd5870 so i can't test your card.
I also can not test your performance because i do only have a hd5670 and not a hd5870
and openCL in the radeon opensource r600g isn't ready yet for testing sorry.

6) wine (sometimes, 2d and 3d - say fallout2 and painkiller)
7) monitor support
2) 2D, compiz and 3D bugs
3) -"- features
8) detailed setup, its ok to have 160 page, but have it covered. Preferably in one place.

i can test this part but what kind of features do you like?

and setup?? what do you mean? i use 2 stock kubuntu setup and oibaf ppa or xorg-edgers setup

what do you think about monitor support? i test VGA and DVI and HDMI single monitor support i can not check multimonitor support.

2D usage the only known bug for me its the flash white control player panel bug... this makes flash control panels hard to use because the pannel goes white. this is maybe a transparency bug i save a similar bug in hon if the hero cronos makes a time stop shild it goes white to..... . but i think this is a oibaf ppa bug because the normal stable radeon do not have this bug.

3D bugs the stable radeon do not have many bugs if you use Git /unstable PPAs you do have bugs sometimes right now i do have some texture bugs in hon... i think its the new GLSL to galium3D translator/compiler.

Ty, very much!
I know. But purchasing 5870 monster is something not made overnight... given the electricity draw amount over time alone. Its vliw5 card, driver performance is very heavy affected by optimization as far as I understand. Michael did splendid review on nvidia vs amd powerdraw and catalyst vs radeon performance. But still
for both drivers on 5870 or very similar architecture

Comment

Mesa warning: glDraw[Range]Elements(start 7331, end 8087, count 2373, type 0x1403, indices=0xabc0)
end is out of bounds (max=8086) Element Buffer 21 (size 48714)
This should probably be fixed in the application.
Mesa warning: glDraw[Range]Elements(start 11022, end 11057, count 123, type 0x1403, indices=0x11232)
end is out of bounds (max=11056) Element Buffer 11 (size 70440)
This should probably be fixed in the application.
Mesa warning: glDraw[Range]Elements(start 794, end 1034, count 504, type 0x1403, indices=0xf00)
end is out of bounds (max=1033) Element Buffer 51 (size 4848)
This should probably be fixed in the application.
Mesa warning: glDraw[Range]Elements(start 794, end 1034, count 504, type 0x1403, indices=0xf00)
end is out of bounds (max=1033) Element Buffer 51 (size 4848)
This should probably be fixed in the application.
Mesa warning: glDraw[Range]Elements(start 297, end 1072, count 2253, type 0x1403, indices=0x9c0)
end is out of bounds (max=1071) Element Buffer 59 (size 7002)
This should probably be fixed in the application.
Mesa warning: glDraw[Range]Elements(start 297, end 1072, count 2253, type 0x1403, indices=0x9c0)
end is out of bounds (max=1071) Element Buffer 59 (size 7002)
This should probably be fixed in the application.
Mesa warning: glDraw[Range]Elements(start 297, end 1072, count 2253, type 0x1403, indices=0x9c0)
end is out of bounds (max=1071) Element Buffer 59 (size 7002)
This should probably be fixed in the application.
Mesa warning: glDraw[Range]Elements(start 297, end 1072, count 2253, type 0x1403, indices=0x9c0)
end is out of bounds (max=1071) Element Buffer 59 (size 7002)
This should probably be fixed in the application.
Mesa warning: glDraw[Range]Elements(start 297, end 1072, count 2253, type 0x1403, indices=0x9c0)
end is out of bounds (max=1071) Element Buffer 59 (size 7002)
This should probably be fixed in the application.

This bit is a known issue with the Unigine code. It doesn't seem to cause any problems, so it's safe to ignore.

Comment

Yes, Im aware. I use gentoo though, but I will be able to apply thanks to you keeping the revision logs. With "debug pool" I mean a pool, similar to current bug pool on freedesktop, that would list the tasks to perform(and instruction on how) some test on current drivers, directed to people that use open drivers but have no possiblilty to program the changes. Ie, bringing hackers and users together.

You can start experimenting on it if you care, but I am a bit busy to do it myself.

Comment

I'm still searching a way to keep 32bit mesa and libdrm in sync with the main 64bit driver. On debian I do use multiarch xserver/mesa from xorg-edgers ppa and dpkg from 'pu/multiarch/full' branch (but natty already ships it), fedora already has multiarch since 6 years, but what about gentoo? multilib overlay sucks, nobody keeps the mesa/libdrm/xf86-video-ati 9999 ebuilds in sync and they simply don't work. Also, if you use external overlays you can forgot about ia32 because multilib is not in portage and so nobody has to take care of it.

P.S.
oibaf, do you plan to support multiarch in your ppa?

I think that multiarch is supported on oneiric but not on natty (my packages are based on these). IIRC xorg-edgers is trying to backport multiarch to natty but it requires some other packages updates which I prefer not to do in my PPA to avoid breaking things for the others.