linux-kernel - Re: [PATCH] drm/i915/tv: After disabling the pipe, use wait_for_vblank

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1282691196.2120.30.camel@localhost.localdomain>
Date:	Wed, 25 Aug 2010 01:06:36 +0200
From:	Ivan Bulatovic <combuster@....com>
To:	Chris Wilson <chris@...is-wilson.co.uk>
Cc:	linux-kernel@...r.kernel.org,
	Jesse Barnes <jbarnes@...tuousgeek.org>
Subject: Re: [PATCH] drm/i915/tv: After disabling the pipe, use
 wait_for_vblank_off()

On Tue, 2010-08-24 at 22:52 +0100, Chris Wilson wrote: 
> On Tue, 24 Aug 2010 23:08:50 +0200, Ivan Bulatovic <combuster@....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@...r.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.

/edit: had to remove linux-gfx from cc or mail wouldn't send otherwise

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/