Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH] drm/i915: fixup TV load detect
Date: Sat, 1 Dec 2012 02:21:09 +0100	[thread overview]
Message-ID: <20121201012109.GF4384@phenom.ffwll.local> (raw)
In-Reply-To: <1352812997-23122-1-git-send-email-daniel.vetter@ffwll.ch>

On Tue, Nov 13, 2012 at 02:23:17PM +0100, Daniel Vetter wrote:
> The docs recommend that we use one high sense to detect composite and
> S-Video, and low/inverted sense for component (or general output
> detection, but we don't bother with that).
> 
> This might or might not finally clear up the confusion around TV
> detection. Historically we've flip-flopped an aweful lot between high
> and low sense, with varying amounts of justification (usually none
> that would have survived scrunitation). The last just change was
> 
> commit d42c9e2c24f7e7897405b85816bdf4ac924881c0
> Author: Daniel Vetter <daniel.vetter@ffwll.ch>
> Date:   Sun Mar 25 22:56:14 2012 +0200
> 
>     drm/i915: reinstate GM45 TV detection fix
> 
> Motivated by the last TV detection bug I could find in our bugzilla.
> 
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=31519
> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>

This actually makes matters worse as I've just found out on my gm45 - now
it detects a spurious TV. Back to the drawing board.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

      reply	other threads:[~2012-12-01 12:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-13 13:23 [PATCH] drm/i915: fixup TV load detect Daniel Vetter
2012-12-01  1:21 ` Daniel Vetter [this message]

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=20121201012109.GF4384@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@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