Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Farnsworth <simon.farnsworth@onelan.com>
To: Adam Jackson <ajax@redhat.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Unexpected behaviour of xrandr and the Intel driver on monitor hotplug
Date: Tue, 18 May 2010 18:07:54 +0100	[thread overview]
Message-ID: <201005181807.54812.simon.farnsworth@onelan.com> (raw)
In-Reply-To: <1274192359.25350.3776.camel@atropine.boston.devel.redhat.com>

On Tuesday 18 May 2010, Adam Jackson <ajax@redhat.com> wrote:
> On Mon, 2010-05-17 at 12:13 +0100, Simon Farnsworth wrote:
> > The first bit of misbehaviour I'm seeing is caching of EDID across
> > hotplug events. If I boot my system with no display attached, I
> > correctly see no EDID property. When I connect a monitor via VGA, using
> > cabling that supports DDC, I see EDID. When I unplug the monitor, I
> > continue to see the old EDID. When I then plug in using a cable that
> > doesn't support DDC, I see an extra mode appear in the mode list, but
> > the EDID has not changed. Connecting using the original cable, or
> > disconnecting cables completely removes this extra mode.
> 
> commit 725398322d05486109375fbb85c3404108881e17
> Author: Zhao Yakui <yakui.zhao@intel.com>
> Date:   Thu Mar 4 08:25:55 2010 +0000
> 
Adding that to my kernel build nearly fixed things for me. I still can't 
explain why the 848x480 mode appears when I connect a DDC-crippled cable to 
the GMA 945, but I can live with that, I suspect (it looks to be XServer side, 
anyway, and I'm about to have to generate patches there, as I don't want 
default modes).
-- 
Simon Farnsworth
Software Engineer
ONELAN Limited
http://www.onelan.com/

  reply	other threads:[~2010-05-18 17:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-17 11:13 Unexpected behaviour of xrandr and the Intel driver on monitor hotplug Simon Farnsworth
2010-05-18 14:19 ` Adam Jackson
2010-05-18 17:07   ` Simon Farnsworth [this message]
2010-05-18 17:57     ` Adam Jackson

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=201005181807.54812.simon.farnsworth@onelan.com \
    --to=simon.farnsworth@onelan.com \
    --cc=ajax@redhat.com \
    --cc=intel-gfx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox