Re: r300 on Thinkpad r50p (RV350)

[Alex D. <ale...@gm...>]

On 6/29/05, Hamish Marson <ha...@tr...> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> Alex Deucher wrote:
>=20
> > On 6/29/03, Rune Petersen <ru...@me...> 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 >=3D CHIP_FAMILY_R300) { + unsigned
> >> char *RADEONMMIO =3D 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.
> >
>=20
> 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).

the flickering may be GL related.  if you are using one head, try this
line instead:
OUTREG(0x180, INREG(0x180) | 0x0100);
that will only up the priority on display0.

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

depth 24 is 32bpp internally to the driver.  there is no depth 32.

>=20
> 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).
>=20
> Alex. Are the databooks still a dire secret? Or can you share (If
> softcopy). Or can ordinary mortals get hold of them?
>=20

Sorry NDAs.

Alex

> regards
>  Hamish.
>=20
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.0 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>=20
> iD8DBQFCwrIC/3QXwQQkZYwRAqa4AKDVEjopQ1xhMcP/mBtBz4Ya7hAjmwCfbEeD
> CrVJq23sNyMApn2J65JDx/c=3D
> =3DajyG
> -----END PGP SIGNATURE-----
>=20
>