From: Chris Wilson <chris@chris-wilson.co.uk>
To: dmarkh@cfl.rr.com
Cc: markh@compro.net,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
linux-kernel@vger.kernel.org
Subject: Re: drm_kms_helper problems
Date: Tue, 23 Oct 2012 10:21:15 +0100 [thread overview]
Message-ID: <eeac1e$4nt1bk@AZSMGA002.ch.intel.com> (raw)
In-Reply-To: <20121023083623.774f093e@pluto.restena.lu>
[-- Attachment #1: Type: text/plain, Size: 746 bytes --]
On Tue, 23 Oct 2012 08:36:23 +0200, Bruno Prémont <bonbons@linux-vserver.org> wrote:
> On Mon, 22 Oct 2012 17:54:26 Mark Hounschell wrote:
> > I'm still getting the same messages spewed into the kernel log file. So
> > this looks to me like the kernel is confused. Again, I ask, why do I have 3
> > HDMIs and 3 DPs but just one VGA.
>
> Maybe Daniel or Chris can comment on that high quantity of DP/HDMI
> connectors seen by driver. Those are probably also the cause of the
> persistent EDID complaints in kernel log.
That's what the hardware reports as being present; praise be to
cost-cutting manufacturers who do not want to spend extra money to wire
up their boards to spec.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
[-- 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
next prev parent reply other threads:[~2012-10-23 9:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-21 14:43 drm_kms_helper problems Mark Hounschell
2012-10-21 14:58 ` Bruno Prémont
2012-10-21 18:18 ` [Intel-gfx] " Mark Hounschell
2012-10-21 19:18 ` Bruno Prémont
2012-10-22 11:42 ` Mark Hounschell
2012-10-22 17:40 ` Mark Hounschell
2012-10-22 21:54 ` Mark Hounschell
2012-10-23 6:36 ` Bruno Prémont
2012-10-23 9:21 ` Chris Wilson [this message]
2012-10-23 9:59 ` Mark Hounschell
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='eeac1e$4nt1bk@AZSMGA002.ch.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=dmarkh@cfl.rr.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markh@compro.net \
/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