From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 66632] Very low FPS when video memory is full (GART & ram <-> vram swapping)
Date: Mon, 13 Jan 2014 21:23:56 +0000 [thread overview]
Message-ID: <bug-66632-502-vbPoQXNeVx@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-66632-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 478 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=66632
--- Comment #10 from MirceaKitsune <sonichedgehog_hyperblast00@yahoo.com> ---
(In reply to comment #9)
What I did was to simply checkout the stats6 branch and compile it. GIT clone
the repository, then create a local branch and pull stats6 into it. After that
compile, enable the debug flag, and run the application through the new version
of Mesa.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1369 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-01-13 21:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-05 23:31 [Bug 66632] New: Very low FPS when video memory is full (GART & ram <-> vram swapping) bugzilla-daemon
2014-01-12 11:31 ` [Bug 66632] " bugzilla-daemon
2014-01-12 12:00 ` bugzilla-daemon
2014-01-12 14:11 ` bugzilla-daemon
2014-01-12 14:17 ` bugzilla-daemon
2014-01-12 19:06 ` bugzilla-daemon
2014-01-12 21:07 ` bugzilla-daemon
2014-01-13 8:38 ` bugzilla-daemon
2014-01-13 12:52 ` bugzilla-daemon
2014-01-13 18:47 ` bugzilla-daemon
2014-01-13 21:23 ` bugzilla-daemon [this message]
2014-01-14 9:48 ` bugzilla-daemon
2014-01-26 12:24 ` bugzilla-daemon
2019-09-18 19:04 ` 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-66632-502-vbPoQXNeVx@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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 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.