Mailinglist Archive: radeonhd (427 mails)

[Alex Deucher <alexdeucher@xxxxxxxxx>]

On Fri, May 8, 2009 at 11:07 AM, Juergen Buchmueller
<pullmoll@xxxxxxxxxxx> wrote:
> On Fri, 8 May 2009 10:32:46 -0400
> Alex Deucher <alexdeucher@xxxxxxxxx> wrote:
>
> > There is no XAA support for r6xx/r7xx.  When you select XAA, it falls
> > back to shadowfb or none I think.
>
> Ok, so what I see then is shadowfb, which always has been reasonably
> fast.
>
> > Most likely you don't have the drm installed correctly.  If the drm is
> > not available, the driver will fallback to direct framebuffer access
> > rather than shadowfb for software rendering.
>
> Well, actually there is no such thing as drm in a NetBSD 5.0 kernel.
> So if you say I need a kernel direct rendering manager, then the
> following lines from Xorg.0.log are a little misleading:
>
> (**) RADEONHD(0): Depth 16, (--) framebuffer bpp 16
> (**) RADEONHD(0): Option "AccelMethod" "EXA"
> (**) RADEONHD(0): Selected EXA 2D acceleration.
> (II) RADEONHD(0): Unknown card detected: 0x95C5:0x1043:0x01F4.
>        If - and only if - your card does not work or does not work
> optimally please contact radeonhd@xxxxxxxxxxxx to help rectify this.
>        Use the subject: 0x95C5:0x1043:0x01F4: <name of board>
>        and *please* describe the problems you are seeing
>        in your message.
> (--) RADEONHD(0): Detected an RV620 on an unidentified card
>
> There is no warning or even error telling me that EXA would not be
> working or that I'm missing something else.

Those messages are telling you that you've selected EXA, look further
down the log to see if EXA initialized properly or not.  if it did
you'll see:

(II) EXA(0): Offscreen pixmap area of 51871744 bytes
(II) EXA(0): Driver registered support for the following operations:
(II)         Solid
(II)         Copy
(II)         Composite (RENDER acceleration)
(II)         UploadToScreen
(II)         DownloadFromScreen

> > Shadowfb is faster than rendering directly to the framebuffer because
> > the framebuffer is shadowed in system ram.
>
> Ok, I got that. So I think the radeonhd drivers before 1.2.5 were
> falling back to shadowfb (?), while 1.2.5 directly accesses the
> framebuffer in case it doesn't find (how?) DRM.

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.

> Perhaps a warning or error message in the logfile would help stupid
> people like me to understand what goes wrong ;-)
>
> > Alex
>
> Thanks for the explanations,

No problem.

Alex

> Juergen
--
To unsubscribe, e-mail: radeonhd+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: radeonhd+help@xxxxxxxxxxxx