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.
Well, how well does 2D performance and video work in the radeonhd driver for the 780G chipset (HD 3200)? With fglrx, 2D seems to lag a bit at times, and I dunno if it's related to fglrx, but sometimes when you switch tabs in a multi tabbed session of gvim, the text isn't drawn. However, video seems to work fine with fglrx.
Both 2D (EXA) and video (Xv) accel work fine as long as you have updated drm modules for your kernel.
I just want to make sure I've got this straight before I start investing too much thought/time into it: If I were to grab a copy of Ubuntu Jaunty in 2 weeks when it comes out, in theory I'd just have to update xorg-driver-ati/radeonhd and the mesa libs to 7.5, but not have to touch the kernel if I wanted to get the Mesa 3D code for my RV770 working (replace Mesa 7.5 with radeon-rewrite or whatever Mesa branch the code ends up in for now, since it sounds like Mesa 7.5 will be released before all the r600/r700 3D code gets merged in).
Because the item being discussed is Mesa 3D drivers for r600/r700, and there's not yet a Gallium driver written for these chips, no X.Org or kernel updates are needed, just Mesa and xorg-driver-ati or xorg-driver-radeonhd, right?
I've been wanting to try out a lot of the work that's been going on lately for the Radeon 4850 I have in my home machine, but replacing half of the X stack in Ubuntu is a bit more than I really feel like dealing with right now. If it turns out I'll still have to replace X.org and/or the kernel, I'll give it a shot in my Lunar Linux install instead [ yay for source-based distros that aren't Gentoo =) ].
I expect you will need to update the drm as well. The X server and Mesa driver use different APIs into the drm; right now the API used by the X server is implemented in the Jaunty kernel (that's what EXA and Xv use) but the API used by Mesa is not.
The r600_demo program uses the X server's API, not the Mesa API.
You'll need an updated drm and ddx to use the new mesa driver. You need the updated ddx to specify the correct 3D driver name, and you'll need an updated drm to supply the ioctl used for 3D. As John said, the 2D and 3D drivers do not use the same ioctls at the moment. Since the 3D driver isn't done yet, the 3D ioctl is still in flux.
Alright, sounds good. New Mesa, new copy of drm, new xorg-driver-*, ???, profit.
I guess I'll give this a shot on the Lunar install then, since the repository has a drm-git package, and I've previously written my own packages to install xorg-driver-ati and/or xorg-driver-radeonhd. I haven't gotten the Mesa git install to work on lunar yet, but I wrote the basic framework for it while I was screwing around with this stuff last month. Shouldn't be too hard to extend that to pull whatever branches I need from the repository.