From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Johannes Bauer <dfnsonfsduifb@gmx.de>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Fan running with Intel Graphics
Date: Tue, 13 Dec 2011 13:46:49 -0800 [thread overview]
Message-ID: <20111213134649.2e1e97e1@jbarnes-desktop> (raw)
In-Reply-To: <4EE7C402.2070003@gmx.de>
[-- Attachment #1.1: Type: text/plain, Size: 807 bytes --]
On Tue, 13 Dec 2011 22:30:42 +0100
Johannes Bauer <dfnsonfsduifb@gmx.de> wrote:
> > then echo that value into the max freq file, e.g.:
> >
> > $ echo 400 > /sys/kernel/debug/dri/0/i915_max_freq
>
> This doesn't work for
>
> joelaptop [/sys/kernel/debug/dri]: uname -a
> Linux joelaptop 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC
> 2011 x86_64 x86_64 x86_64 GNU/Linux
>
> Since i915_max_freq does not exist -- do I need to switch to a more
> recent kernel version?
Yes. Try running drm-intel-next from Keith's git tree:
git://people.freedesktop.org/~keithp/linux
> I also noted that dri/ has two subdirectories, 0 and 64. Does this mean
> anything?
You can ignore the "64" directory, it's currently unused.
--
Jesse Barnes, Intel Open Source Technology Center
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2011-12-13 21:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 21:12 Fan running with Intel Graphics Johannes Bauer
2011-12-13 21:23 ` Jesse Barnes
2011-12-13 21:30 ` Johannes Bauer
2011-12-13 21:46 ` Jesse Barnes [this message]
2011-12-15 22:04 ` Johannes Bauer
2011-12-20 20:19 ` Johannes Bauer
2012-01-04 17:40 ` Jesse Barnes
2011-12-14 2:49 ` Eugeni Dodonov
2011-12-15 22:13 ` Johannes Bauer
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=20111213134649.2e1e97e1@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=dfnsonfsduifb@gmx.de \
--cc=intel-gfx@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