On Thu, Aug 04, 2011 at 11:05:39AM -0700, Keith Packard wrote:
> Linus' tree does not have the relevant fixes; I was posting that patch
> to let you know it was coming. The fixes are in my drm-intel-next
> branch, which I've asked Dave Airlie to pull in.
I have tested your branch drm-intel-next an
> -Original Message-
> From: intel-gfx-bounces+gordon.jin=intel@lists.freedesktop.org
> [mailto:intel-gfx-bounces+gordon.jin=intel@lists.freedesktop.org] On
> Behalf Of Dexter Filmore
> Sent: Friday, August 05, 2011 5:16 AM
> To: intel-gfx@lists.freedesktop.org
> Subject: [Intel-gfx
Daniel Vetter writes:
> On Thu, Aug 4, 2011 at 16:05, Ted Phelps wrote:
> > I saw a bunch of stack traces like the one below, alternating between
> > ring_put and ring_get, before the GPU was declared wedged.
>
> How much time happens between the first wait_for_fifo backtrace and
> the final gpu
System: Core i5 2500T on a H67 Gigabyte board
OS: debian testing,
intel driver 2.15
Mesa 7.10.3
kernel 2.6.39
Tested with SMplayer and XBMC (file 1080p x264 mkv): when zooming, panning etc
the image tears and seems to lag in updating regions of the image.
First time intel gfx user, anything I
On Wed, Aug 03, 2011 at 04:43:33PM +0200, Lukas Hejtmanek wrote:
> On Wed, Aug 03, 2011 at 08:44:30AM +0100, Chris Wilson wrote:
> > > I gave a try to 3.0 kernel but problems were even worse. Playing video
> > > using
> > > XV gave me random framents of video accross whole desktop :(
> >
> > This
On Thu, 4 Aug 2011 16:29:50 +0800, Grissiom wrote:
> 1) I got to know that I'm not the only one who encountered with this bug.
Even one failure would have been sufficient to revert this for 3.0 (and,
for 3.1 as well if we find more troubles).
> 2) I tried keithp/drm-intel-next with i915.i915_en
On Thu, 4 Aug 2011 07:10:27 +0200, Francesco Allertsen
wrote:
> Hi Keith,
>
> On Wed, Aug 03, 2011 at 08:23:54PM -0700, Keith Packard wrote:
> > Jesse Barnes and I found a couple of issues where incorrect mode
> > setting would cause problems with RC6 enabled. We're hopeful that
> > fixing those
On Thu, 4 Aug 2011 17:40:24 +0800, Wu Fengguang wrote:
> Right. I actually have this chunk. dmesg shows that in intel_hdmi_detect(),
> the drm_encoder object is there, however encoder->crtc is NULL at the
> time.
Correct. encoder->crtc is set only when the output is active.
> You may wonder w
Signed-off-by: Hai Lan
---
tests/testdisplay.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/tests/testdisplay.c b/tests/testdisplay.c
index dae52ca..1d85acd 100644
--- a/tests/testdisplay.c
+++ b/tests/testdisplay.c
@@ -414,7 +414,7 @@ allocate_surface(int fd, int wid
On Thu, Aug 4, 2011 at 16:05, Ted Phelps wrote:
> I saw a bunch of stack traces like the one below, alternating between
> ring_put and ring_get, before the GPU was declared wedged.
How much time happens between the first wait_for_fifo backtrace and
the final gpu hang report? If it's short (order
Keith Packard writes:
> Jesse Barnes and I found a couple of issues where incorrect mode
> setting would cause problems with RC6 enabled. We're hopeful that
> fixing those will resolve the outstanding issues with a few machines
> that had trouble before 3.0 with rc6.
Thanks for continuing to bash
> On Mon, 1 Aug 2011 21:51:40 +0800, Wu Fengguang
> wrote:
>
> > 1) intel_write_eld() is not called at all
> >It seems we need to call intel_write_eld() in other places besides
> >inside ->mode_set(). Is ->detect() the right place to do so? In
> >other words, are there established co
12 matches
Mail list logo
