From: Chris Wilson <chris@chris-wilson.co.uk>
To: Matthew Willoughby <mattfredwill@gmail.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: QS57/HD Graphics support?
Date: Fri, 03 Dec 2010 17:22:35 +0000 [thread overview]
Message-ID: <849307$ak68ps@azsmga001.ch.intel.com> (raw)
In-Reply-To: <b9dded$h83ua3@orsmga002.jf.intel.com>
On Tue, 30 Nov 2010 09:21:37 +0000, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Tue, 30 Nov 2010 09:15:06 +0800, Matthew Willoughby <mattfredwill@gmail.com> wrote:
> > Enabling LVDS2 via xrandr turns the screen on and extends the desktop,
> > however all that is outputted is grey, occasionally white, and sometimes
> > flashing colours.
> > For information: A fresh install of Windows 7 can't use the second screen
> > either, until the Intel drivers are installed, so I'm assuming that this is
> > simply not supported in the linux drivers.
Ok, the device is configured differently to how I was expecting. It uses
SDVO to drive both LVDS (which I should have guessed given the drivers
report of 2 LVDS). At first glance, we think we are driving both panels,
i.e. we've attached a crtc to each and a bound the fbcon framebuffer to
both crtcs, yet only one panel is active. The likely suspect is inside
intel_sdvo.c.
A different adventure than the one I was anticipating. Perhaps this will
be my wayland test bed...
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2010-12-03 17:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 1:15 QS57/HD Graphics support? Matthew Willoughby
2010-11-30 9:21 ` Chris Wilson
2010-12-03 17:22 ` Chris Wilson [this message]
2010-12-03 23:34 ` Alberto Di Meglio
2010-12-03 23:39 ` Chris Wilson
2010-12-04 0:00 ` Chris Wilson
2010-12-04 11:23 ` Alberto Di Meglio
2010-12-04 12:54 ` Julien Cristau
2010-12-04 13:31 ` Matthew Willoughby
2010-12-04 20:43 ` Alberto Di Meglio
2010-12-04 14:24 ` Alberto Di Meglio
2011-01-05 10:00 ` Anfanglir
2011-01-05 10:13 ` Chris Wilson
2011-01-05 23:49 ` Anfanglir
2010-11-30 14:31 ` Paul Menzel
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='849307$ak68ps@azsmga001.ch.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mattfredwill@gmail.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 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.