From: Keith Packard <keithp@keithp.com>
To: Simon Farnsworth <simon.farnsworth@onelan.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCHv5] drm/i915: Enable SDVO hotplug interrupts for HDMI and DVI
Date: Wed, 21 Sep 2011 08:47:50 -0700 [thread overview]
Message-ID: <yunehz9gamx.fsf@aiko.keithp.com> (raw)
In-Reply-To: <201109211618.55592.simon.farnsworth@onelan.co.uk>
[-- Attachment #1.1: Type: text/plain, Size: 931 bytes --]
On Wed, 21 Sep 2011 16:18:55 +0100, Simon Farnsworth <simon.farnsworth@onelan.co.uk> wrote:
> I'm ANDing the value returned by hardware with 3 - I should be ANDing it with
> an appropriate ~3. The rest of the code (setting those bits in
> intel_sdvo_dvi_init based on what functions I have) should be OK.
Oh, that's a good point. I'd say that you shouldn't change any bits you
don't know about.
So, fetch the current active hotplug value and then clear bits 0 and 1
so that we change only those.
> I would still like someone with the spec to go over what I'm doing - this
> seems appropriate, but *all* I have to test against are two different
> motherboards with "integrated" DVI-D that turns out to be an SDVO
> device.
Yeah, I've been digging around for an SDVO spec, but it's buried as it
contains a pile of stuff for macro-vision and other content protection
bits.
--
keith.packard@intel.com
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2011-09-21 15:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 17:31 [PATCHv5] drm/i915: Enable SDVO hotplug interrupts for HDMI and DVI Simon Farnsworth
2011-09-20 19:43 ` Keith Packard
2011-09-21 9:08 ` Simon Farnsworth
2011-09-21 14:58 ` Keith Packard
2011-09-21 15:18 ` Simon Farnsworth
2011-09-21 15:47 ` Keith Packard [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=yunehz9gamx.fsf@aiko.keithp.com \
--to=keithp@keithp.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=simon.farnsworth@onelan.co.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.