-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alex Deucher wrote:

> On 6/29/03, Rune Petersen <[EMAIL PROTECTED]> wrote:
>
>> Hamish Marson wrote:
>>
>>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>>
>>> Hamish Marson wrote:
>>>
>>>
>>>> Just as a status report...
>>>>
>>>> On my thinkpad r50p which has an rv350 (FireGL-T2) when using
>>>> the current CVS xorg, CVS Mesa and the tagged r300 driver
>>>> 'the_perfect_frag') it all works, 1600fps on glxgears, but
>>>> the flickering is awful on OpenGL apps...
>>>>
>>>> (Current CVS is yesterday for xorg, today for Mesa).
>>>>
>>>> glxgears - works OK. But flickers. tuxracer - works OK.
>>>> Reasonable frame rates. But flickers at about 10Hz. gl-117 -
>>>> Same. Reasonable frame rates. But flickers.
>>>>
>>>> glxgears was in a window. tuxracer and gl-117 were
>>>> full-screen. I had to stop before I threw up...
>>>>
>>>> Suspend & Resume worked OK so far (Only suspended to RAM once
>>>> though).
>>>>
>>>> Hamish.
>>>
>>>
>>> FWIW the same things also happens on the current CVS copy.
>>>
>>> This is with a 1600x1200 resolution LCD as well, just in case
>>> it matters. gl-117 seems to geta round 60fps in the init
>>> screens... But I can't see the screen well enough to navigate
>>> through (Or access even) any setup screens to try & change
>>> anything in it.
>>>
>>> H
>>>
>> Flickering should be resolved by adding this to radeon_driver.c
>> in the Xorg: @@ -5631,6 +5627,11 @@ if (!info->IsSecondary)
>> RADEONChangeSurfaces(pScrn);
>>
>> + if (info->ChipFamily >= CHIP_FAMILY_R300) { + unsigned
>> char *RADEONMMIO = info->MMIO; + OUTREG(0x180, INREG(0x180)
>> | 0x1100); + } + if(info->MergedFB) { /* need this here to fix
>> up sarea values */ RADEONAdjustFrameMerged(scrnIndex,
>> pScrn->frameX0, pScrn->frameY0, 0);
>>
>>
>> Rune Petersen
>>
>
> According to the databooks, this is the correct behavior for high
> res modes. What it does is bump the display0/1 priorities in the
> memory controller. I'll be committing a slighly updated version of
> this patch to cvs in the next few days.
>

If anything, this patch made my display flicker even worse than
without it.  Frame rates seem slightly lower, but glxgears gets around
1450-1500fps at only about 50% CPU (vs 1500-1600fps and 100% CPU
utilisation without the patch).

This is at 24bpp. Because @ 32bpp in xorg.conf, X doesn't start
(Unsupported bit depth is the error).

I also tried 1024x768 resolution. Same thing. (In fact tuxracer runs
at a lower res I think. Hard to tell, I have the default screen
expansion turned on for the LCD. Must turn it off).

Alex. Are the databooks still a dire secret? Or can you share (If
softcopy). Or can ordinary mortals get hold of them?

regards
 Hamish.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCwrIC/3QXwQQkZYwRAqa4AKDVEjopQ1xhMcP/mBtBz4Ya7hAjmwCfbEeD
CrVJq23sNyMApn2J65JDx/c=
=ajyG
-----END PGP SIGNATURE-----



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to