From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 42175] RV730: Display errors in glxgears & WebGL
Date: Mon, 24 Oct 2011 21:55:59 +0000 [thread overview]
Message-ID: <bug-42175-502-GKNv61IX73@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-42175-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=42175
--- Comment #4 from Stefan <kdevel@vogtner.de> 2011-10-24 14:55:59 PDT ---
(In reply to comment #3)
> Can you bisect?
The change took place between 7.11-rc1 and -rc2:
a8907c6005d7935b4520255e12184c139471b5b9 is the first bad commit
commit a8907c6005d7935b4520255e12184c139471b5b9
Author: Benjamin Franzke <benjaminfranzke@googlemail.com>
Date: Sat Jul 2 13:41:35 2011 +0200
But: This is where the switch from the old driver to the Gallium takes place.
The old driver got used in my configuration up to 7.11-rc1 because the
udev-devel packet was not installed. Eventually after installing it 7.11-rc1
uses the new driver.
So currently I don't have a "good" reference for a bisection.
BTW: https://bugzilla.mozilla.org/show_bug.cgi?id=693056 (origin of the current
problems).
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-10-24 21:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 21:06 [Bug 42175] New: RV730: Display errors in glxgears & WebGL bugzilla-daemon
2011-10-24 21:06 ` [Bug 42175] " bugzilla-daemon
2011-10-24 21:07 ` bugzilla-daemon
2011-10-24 21:44 ` bugzilla-daemon
2011-10-24 21:55 ` bugzilla-daemon [this message]
2011-10-25 0:32 ` bugzilla-daemon
2011-10-25 15:00 ` bugzilla-daemon
2011-10-25 15:16 ` bugzilla-daemon
2011-10-26 8:47 ` bugzilla-daemon
2011-10-26 12:29 ` bugzilla-daemon
2011-10-26 12:38 ` bugzilla-daemon
2011-10-26 13:07 ` 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-42175-502-GKNv61IX73@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox