From: Chris Wilson <chris@chris-wilson.co.uk>
To: Knut Petersen <Knut_Petersen@t-online.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/i915/sdvo: If at first we dont succeed in reading the response, wait
Date: Tue, 25 Jan 2011 22:11:03 +0000 [thread overview]
Message-ID: <b7da2f$q83ub3@fmsmga001.fm.intel.com> (raw)
In-Reply-To: <4D3F4849.4030905@t-online.de>
On Tue, 25 Jan 2011 23:01:45 +0100, Knut Petersen <Knut_Petersen@t-online.de> wrote:
> I think that patch also should be a candidate for 2.6.37.1 as it fixes a
> regression
> introduced in 2.6.37.
(Actually I think the bug is older than that...)
> Something new:
>
> Have a look at the attached new log. I connected a 2nd monitor, so
> there is a monitor attached to both
> the VGA-1 and DVI-1 connectors. At the framebuffer console prompt (no X
> running)
> I changed to console 2 and back to console 1. The log starts at the
> point of switching
> back to console 1. Now ... shouldn't I read something about a
> output_poll_execute for VGA-1?
In this case, no. VGA-1 has hw hotplug support, so that connector is not
polled but uses an interrupt instead.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-01-25 22:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 18:48 [BUG/REGRESSION] DRM / i915 / 2.6.37 and 2.6.38-rc*: DVI output gets disabled/reenabled under load Knut Petersen
2011-01-24 19:13 ` Chris Wilson
2011-01-25 11:50 ` Knut Petersen
2011-01-25 12:11 ` Chris Wilson
2011-01-25 12:35 ` Knut Petersen
2011-01-25 13:50 ` Chris Wilson
2011-01-25 14:14 ` Knut Petersen
2011-01-25 14:44 ` Chris Wilson
2011-01-25 15:06 ` [PATCH] drm/i915/sdvo: If at first we don't succeed in reading the response, wait Chris Wilson
2011-01-25 22:01 ` Knut Petersen
2011-01-25 22:11 ` Chris Wilson [this message]
2011-01-25 22:32 ` [PATCH] drm/i915/sdvo: If at first we dont " Knut Petersen
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='b7da2f$q83ub3@fmsmga001.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=Knut_Petersen@t-online.de \
--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