From: Chris Wilson <chris@chris-wilson.co.uk>
To: Knut Petersen <Knut_Petersen@t-online.de>
Cc: jesse.barnes@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [BUG/REGRESSION] DRM / i915 / 2.6.37 and 2.6.38-rc*: DVI output gets disabled/reenabled under load
Date: Tue, 25 Jan 2011 13:50:31 +0000 [thread overview]
Message-ID: <b7da2f$q7ufnf@fmsmga001.fm.intel.com> (raw)
In-Reply-To: <4D3EC393.3010403@t-online.de>
On Tue, 25 Jan 2011 13:35:31 +0100, Knut Petersen <Knut_Petersen@t-online.de> wrote:
> Attached find the startup logs. Both debuglevel 0xf.
2.6.36:
> [ 2.699943] [drm:intel_sdvo_debug_write], SDVOC: W: 02 (SDVO_CMD_GET_DEVICE_CAPS)
> [ 2.736984] [drm:intel_sdvo_debug_response], SDVOC: R: 02 C2 01 01 01 3D 3E 00 (Success)
2.6.38:
> [ 2.561275] [drm:intel_sdvo_debug_write], SDVOC: W: 02 (SDVO_CMD_GET_DEVICE_CAPS)
> [ 2.565952] [drm:intel_sdvo_read_response], SDVOC: R: (Success) 02 C2 01 01 01 3D 3E 00
> [ 2.579730] [drm:intel_sdvo_get_capabilities], SDVO capabilities:
> [ 2.579735] vendor_id: 2
> [ 2.579736] device_id: 194
> [ 2.579737] device_rev_id: 1
> [ 2.579738] sdvo_version_major: 1
> [ 2.579739] sdvo_version_minor: 1
> [ 2.579740] sdvo_inputs_mask: 1
> [ 2.579741] smooth_scaling: 1
> [ 2.579742] sharp_scaling: 1
> [ 2.579743] up_scaling: 1
> [ 2.579744] down_scaling: 1
> [ 2.579745] stall_support: 0
> [ 2.579746] output_flags: 62
Both report output_flags of 0x3e, which includes VGA and a few
complementary TV out modes. The VGA-2 seems to be ignored by 2.6.36, but
does seem legitimate. Hmm.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-01-25 13:50 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 [this message]
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 ` [PATCH] drm/i915/sdvo: If at first we dont " Chris Wilson
2011-01-25 22:32 ` 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$q7ufnf@fmsmga001.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=Knut_Petersen@t-online.de \
--cc=jesse.barnes@intel.com \
--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