All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Jackson <ajax@redhat.com>
To: dri-devel@lists.freedesktop.org
Subject: [PATCH 0/5] Initial DisplayPort OUI probing
Date: Mon, 14 May 2012 16:05:44 -0400	[thread overview]
Message-ID: <1337025949-2355-1-git-send-email-ajax@redhat.com> (raw)

DisplayPort has an escape hatch by which devices can identify each other.
I'm not super thrilled that it does, since that's just a clever way of
getting the spec to explicitly bless interoperability bugs.  But it may
be useful information when debugging link training problems, and there's
a cute trick you can do on iMacs that I think will require knowing this
information, so we may as well fill it in.

Tested on a Lenovo T500 against a DP->VGA adaptor (which turns out to be
an ST Microelectronics chip, who knew) and an HP LP2480zx (which does
not advertise OUI support, but also harmlessly returns 0s for the OUI
registers if you read them anyway).

- ajax

             reply	other threads:[~2012-05-14 20:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-14 20:05 Adam Jackson [this message]
2012-05-14 20:05 ` [PATCH 1/5] drm/dp: Add DPCD OUI register defines Adam Jackson
2012-05-14 20:05 ` [PATCH 2/5] drm/dp: Add DPCD defines for register 0x007 Adam Jackson
2012-05-14 20:05 ` [PATCH 3/5] drm/i915/dp: Probe branch/sink OUIs Adam Jackson
2012-05-14 20:05 ` [PATCH 4/5] drm/radeon/dp: " Adam Jackson
2012-05-14 20:05 ` [PATCH 5/5] drm/nouveau/dp: " Adam Jackson
2012-05-21 17:41 ` [PATCH 0/5] Initial DisplayPort OUI probing Adam Jackson
2012-05-21 18:32   ` Jerome Glisse
2012-05-21 18:47   ` Daniel Vetter
2012-05-21 19:27     ` Alex Deucher
2012-05-21 20:11       ` Adam Jackson
2012-05-21 20:35         ` Alex Deucher
2012-05-21 21:09           ` Adam Jackson
2012-05-21 21:48             ` Alex Deucher
2012-05-22  9:27 ` Dave Airlie

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=1337025949-2355-1-git-send-email-ajax@redhat.com \
    --to=ajax@redhat.com \
    --cc=dri-devel@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 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.