All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Jackson <ajax@redhat.com>
To: "Elvis L." <xXSoulwarriorXx@web.de>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: DRI Support for Savage4
Date: Mon, 30 Jan 2012 13:05:32 -0500	[thread overview]
Message-ID: <4F26DBEC.3050609@redhat.com> (raw)
In-Reply-To: <4F26A81E.9010906@web.de>

On 1/30/12 9:24 AM, Elvis L. wrote:
> Hello
>
> first of all, please excuse my possibly bad english. Im German.
>
> I wanted to install DRI-supported drivers for my Savage4 graphic-chip
> (Acer Aspire 1310XC Laptop). I found some in
> http://dri.freedesktop.org/snapshots/ and read, that I have to
> "./install" the common package first, after that the savage package.
> I've took the newest ones.
> The common package was installed without any errors. But the
> savage-package says, that it only be can installed with 2.4 oder 2.6
> kernel. My System based on Fedora 16 (3.2.2.1). What do I have to do,
> that i can use DRI on this laptop? It's horribly damn slow on
> graphic-usage.

Not to break your heart, but I'm pretty sure that laptop's slow for 
reasons besides DRI.

I do apologize for other reasons though.  It looks like a configuration 
change that was meant to be in F17 [1] and later only got copied back to 
F16's update branch.  Mea culpa.  That will be fixed in a future update, 
at which point you'll probably have the renderer string in glxinfo 
magically change from llvmpipe to savage, since F16 is meant to include 
savage DRI support by default.

But I'd be a little surprised if enabling DRI on that chip had any 
appreciable effect on performance.

[1] - In particular, the change that drops all the non-KMS DRM drivers.

- ajax

      reply	other threads:[~2012-01-30 18:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-30 14:24 DRI Support for Savage4 Elvis L.
2012-01-30 18:05 ` Adam Jackson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F26DBEC.3050609@redhat.com \
    --to=ajax@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=xXSoulwarriorXx@web.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.