Mailinglist Archive: radeonhd (265 mails)
| < Previous | Next > |
Re: [radeonhd] X1400 chipset questions
- From: "Alex Deucher" <alexdeucher@xxxxxxxxx>
- Date: Fri, 9 Jan 2009 11:43:59 -0500
- Message-id: <a728f9f90901090843v2465a508p1ac510fbce070425@xxxxxxxxxxxxxx>
On Fri, Jan 9, 2009 at 11:16 AM, Pierpaolo Follia <pfollia@xxxxxxxxx> wrote:
radeonhd supports r5xx-r7xx radeons, radeon supports r1xx-r7xx
radeons. Either driver should work for your hardware. The accel code
is mostly the same as well.
XAA provides no mechanism to migrate pixmaps from system ram to vram,
so if the pixmap containing the video is in system ram we can't use it
as a texture source. You could create a scratch buffer and manually
copy the frame to vram, but no one has implemented that yet. With EXA
you can request the migration directly. Generally this is only an
issue with composite managers, but it can happen anytime.
Alex
--
To unsubscribe, e-mail: radeonhd+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: radeonhd+help@xxxxxxxxxxxx
Hi to all. I have a Mobility Radeon X1400 on my laptop running Ubuntu
8.10 and I have a couple of questions about the new radeonhd driver (I
get it from the XorgOnTheEdge repos).
First of all my chipset is listed both man pages of radeon and
radeonhd driver, so which one should I use? I tried both, and the only
difference is that with radeon driver, the external monitor is
recognized as a Nec 17" and with the radeonhd both my screens (laptop
and external) are not recognized (randr interface display "Unknown
Monitor").
radeonhd supports r5xx-r7xx radeons, radeon supports r1xx-r7xx
radeons. Either driver should work for your hardware. The accel code
is mostly the same as well.
The second question is: I'm using the Xaa acceleration (since with Exa
and composite environment the X server sometimes hangs, and the only
thing I can do is a hard reset) and the Xv acceleration is not working
(applications like totem or VLC simply crash using Xv). Instead, Xv is
working well with Exa acceleration method. Is this correct? Man pages
say nothing about Xv and Xaa.
XAA provides no mechanism to migrate pixmaps from system ram to vram,
so if the pixmap containing the video is in system ram we can't use it
as a texture source. You could create a scratch buffer and manually
copy the frame to vram, but no one has implemented that yet. With EXA
you can request the migration directly. Generally this is only an
issue with composite managers, but it can happen anytime.
Alex
--
To unsubscribe, e-mail: radeonhd+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: radeonhd+help@xxxxxxxxxxxx
| < Previous | Next > |