Mailinglist Archive: radeonhd (427 mails)
| < Previous | Next > |
Re: [radeonhd] 0x95C5:0x1043:0x01F4: Asus EAH3450
- From: Alex Deucher <alexdeucher@xxxxxxxxx>
- Date: Mon, 11 May 2009 13:01:52 -0400
- Message-id: <a728f9f90905111001s3cbbb3b9k2be43558ed60f6c6@xxxxxxxxxxxxxx>
On Mon, May 11, 2009 at 12:20 PM, Matthias Hopf <mhopf@xxxxxxx> wrote:
Yeah, I figured something like that would need to be done which is why
it's not currently done even for older asics.
Alex
--
To unsubscribe, e-mail: radeonhd+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: radeonhd+help@xxxxxxxxxxxx
On May 11, 09 18:10:04 +0200, Matthias Hopf wrote:
On May 08, 09 11:15:05 -0400, Alex Deucher wrote:
Releases before 1.2.5 did not have acceleration support for r6xx/r7xx
cards so they always used shadowfb. When EXA initialization fails the
driver falls back to no accel rather than shadowfb.
Alex, do you think this can be reworked to use shadowfb if it fails? I
know that the logic order is different, so this *might* be troublesome.
Reading the code again, it turns out that we would need a PreInit
function to determine whether acceleration is available or not. So this
needs some coding. The Init function is called after memory layout
setup, which is influenced by ShadowFB.
Yeah, I figured something like that would need to be done which is why
it's not currently done even for older asics.
Alex
--
To unsubscribe, e-mail: radeonhd+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: radeonhd+help@xxxxxxxxxxxx
| < Previous | Next > |