From: Chris Wilson <chris@chris-wilson.co.uk>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: "Matsumura, Ryan" <ryan.matsumura@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: Second HDMI port not visible
Date: Fri, 9 Aug 2013 13:50:46 +0100 [thread overview]
Message-ID: <20130809125046.GA7207@cantiga.alporthouse.com> (raw)
In-Reply-To: <20130807132953.5ad95f07@jbarnes-desktop>
On Wed, Aug 07, 2013 at 01:29:53PM -0700, Jesse Barnes wrote:
> Chris's machine would be a good regression test for this. If it works
> for him too, I think we should push it.
Well, the good news is that it adds another HDMI connection. The bad
news is that the hardware refuses to acknowledge my connections anyway
so I have no idea if it is now broken.
Doesn't look for any reason like it should spontaneously break, so lgtm.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
prev parent reply other threads:[~2013-08-09 12:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 3:10 Second HDMI port not visible Matsumura, Ryan
2013-08-07 7:41 ` Daniel Vetter
2013-08-07 10:44 ` Ville Syrjälä
2013-08-07 15:48 ` Jesse Barnes
2013-08-07 19:15 ` Matsumura, Ryan
2013-08-07 20:29 ` Jesse Barnes
2013-08-09 12:50 ` Chris Wilson [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=20130809125046.GA7207@cantiga.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.org \
--cc=ryan.matsumura@intel.com \
/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