From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Ivan Bulatovic <combuster@gmx.com>
Cc: Chris Wilson <chris@chris-wilson.co.uk>,
linux-kernel@vger.kernel.org, linux-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/tv: After disabling the pipe, use wait_for_vblank_off()
Date: Tue, 24 Aug 2010 16:05:55 -0700 [thread overview]
Message-ID: <20100824160555.142b71fe@virtuousgeek.org> (raw)
In-Reply-To: <1282691071.2120.28.camel@localhost.localdomain>
On Wed, 25 Aug 2010 01:04:31 +0200
Ivan Bulatovic <combuster@gmx.com> wrote:
> On Tue, 2010-08-24 at 22:52 +0100, Chris Wilson wrote:
> > On Tue, 24 Aug 2010 23:08:50 +0200, Ivan Bulatovic <combuster@gmx.com> wrote:
> > > Unfotunately I still get TV connection detected :(
> >
> > Jesse spotted the root cause and Linus has now pushed that fix for
> > intel_wait_for_vblank() out. This is just a very minor bug in comparison.
> > Can you please test against linus/master and check that resolves the
> > spurious TV detection for you?
> > Thanks.
> >
> > --
> > Chris Wilson, Intel Open Source Technology Centre
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
>
> Spurious TV detection is still here and + I have a new problem with
> resolution in init3 when KMS fires up, it occupies only 1/3rd of the
> screen when booting.
>
> I've tried patching the kernel I used for testing so far with that one
> liner and I've tried without patches we tried so far (git pull on a
> clean linux-git) and the symptoms are the same on both of them.
>
> So
> - PIPE_VBLANK_INTERRUPT_STATUS) == 0,
> + PIPE_VBLANK_INTERRUPT_STATUS),
> in intel_display.c doesn't fix the issue, plus it brings a new one in my
> case.
Ugg, one step forward, two steps back. Working on it.
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2010-08-24 23:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-24 1:00 i915: 2.6.36-rc2 wrong resolution on gdm start Ivan Bulatovic
2010-08-24 7:49 ` Chris Wilson
2010-08-24 8:35 ` Ivan Bulatovic
2010-08-24 8:50 ` Chris Wilson
2010-08-24 9:12 ` Ivan Bulatovic
2010-08-24 9:21 ` [PATCH] drm/i915/tv: Flush register writes before sleeping Chris Wilson
2010-08-24 11:03 ` Ivan Bulatovic
2010-08-24 15:11 ` [PATCH] drm/i915/tv: After disabling the pipe, use wait_for_vblank_off() Chris Wilson
2010-08-24 21:08 ` Ivan Bulatovic
2010-08-24 21:52 ` Chris Wilson
2010-08-24 23:00 ` Ivan Bulatovic
2010-08-24 23:04 ` Ivan Bulatovic
2010-08-24 23:05 ` Jesse Barnes [this message]
2010-08-24 23:06 ` Ivan Bulatovic
2010-08-25 8:15 ` Sitsofe Wheeler
2010-08-25 9:17 ` Ivan Bulatovic
2010-08-25 9:31 ` Ivan Bulatovic
2010-08-25 9:51 ` Kan-Ru Chen
2010-08-29 11:29 ` i915: 2.6.36-rc2 wrong resolution on gdm start Pekka Enberg
2010-08-29 13:37 ` Sitsofe Wheeler
2010-08-24 8:54 ` Pekka Enberg
2010-08-29 12:59 ` Maciej Rutecki
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=20100824160555.142b71fe@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=chris@chris-wilson.co.uk \
--cc=combuster@gmx.com \
--cc=linux-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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