dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 81021] AMD CPUs w/ Integrated Graphics (APUs) And Turbo Core Only Boost If "fglrx" Module Is Loaded
Date: Thu, 07 Aug 2014 09:43:32 +0000	[thread overview]
Message-ID: <bug-81021-2300-gwRGWOmZCM@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-81021-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=81021

--- Comment #10 from LiNuxXer <andre.d@gmx.net> ---
(In reply to Alex Deucher from comment #8)
> I'm not sure why you don't think you need a GPU driver installed.  When the
> driver is installed it not only allows the GPU to dynamically adjust it
> clocks and voltages up for performance, but also enables low power states
> and turns off certain blocks when they are not in use, so overall, you'll
> probably save more power with the GPU driver loaded than just leaving the
> GPU in the state set up by the bios.

1) You're absolutely right. radeon outperforms fglrx significantly in console
mode (in my case 10W up to 12W when disabling the output) (and not to mention
the Turbo Core performance which is much smoother).

2) You inspired me to look at all this more systematically. I have posted my
detailed results at http://unix.stackexchange.com/a/148918/79761 -- in short,
the radeon driver is an excellent piece of software (and is in fact saving my
*** regarding processor choice, applying the bapm enabling patch you proposed).

3) One question remains -- can't bapm enabling become at least a parameter? Or
is it already?

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2014-08-07  9:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-81021-2300@https.bugzilla.kernel.org/>
2014-07-29 15:18 ` [Bug 81021] AMD CPUs w/ Integrated Graphics (APUs) And Turbo Core Only Boost If "fglrx" Module Is Loaded bugzilla-daemon
2014-07-29 15:18 ` bugzilla-daemon
2014-07-29 16:03 ` bugzilla-daemon
2014-07-29 23:35 ` bugzilla-daemon
2014-07-30 12:18 ` bugzilla-daemon
2014-07-30 12:32 ` bugzilla-daemon
2014-07-30 13:24 ` bugzilla-daemon
2014-08-03 17:34 ` bugzilla-daemon
2014-08-04 14:53 ` bugzilla-daemon
2014-08-07  9:34 ` bugzilla-daemon
2014-08-07  9:43 ` bugzilla-daemon [this message]
2014-08-07 13:21 ` bugzilla-daemon
2014-08-07 13:31 ` bugzilla-daemon
2014-08-07 15:17 ` bugzilla-daemon
2014-08-07 15:24 ` bugzilla-daemon

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=bug-81021-2300-gwRGWOmZCM@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).