From: Dave Airlie <airlied@gmail.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] qxl: add a connector property to denote hotplug should rescan modes.
Date: Fri, 1 Nov 2013 13:53:57 +1000 [thread overview]
Message-ID: <CAPM=9tyr3LJGPgCidXJVxZJ1+NwDidRny8sUXDt50W2LjNDvUQ@mail.gmail.com> (raw)
In-Reply-To: <20131011082132.GF8303@phenom.ffwll.local>
On Fri, Oct 11, 2013 at 6:21 PM, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Fri, Oct 11, 2013 at 11:05:00AM +1000, Dave Airlie wrote:
>> From: Dave Airlie <airlied@redhat.com>
>>
>> So GNOME userspace has an issue with when it rescans for modes on hotplug
>> events, if the monitor has no EDID it assumes that nothing has changed on
>> EDID as with real hw we'd never have new modes without a new EDID, and they
>> kind off rely on the behaviour now, however with virtual GPUs we would
>> like to rescan the modes and get a new preferred mode on hotplug events
>> to handle dynamic guest resizing (where you resize the host window and the
>> guest resizes with it).
>>
>> This is a simple property we can make userspace watch for to trigger new
>> behaviour based on it, and can be used to replaced EDID hacks in virtual
>> drivers.
>>
>> Signed-off-by: Dave Airlie <airlied@redhat.com>
>
> There's the related problem that we kinda don't tell userspace which
> connectors exactly changed when sending out a hotplug event. We could
> solve both issues with a hotplug_sequence counter that increments on any
> change. Probably more work though ;-)
Its kinda orthogonal problem though, I don't mind reprobing its more for the
case where userspace does nothing when we have no EDID I need to fix.
Dave.
prev parent reply other threads:[~2013-11-01 3:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 1:05 [PATCH] qxl: add a connector property to denote hotplug should rescan modes Dave Airlie
2013-10-11 8:21 ` Daniel Vetter
2013-11-01 3:53 ` Dave Airlie [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='CAPM=9tyr3LJGPgCidXJVxZJ1+NwDidRny8sUXDt50W2LjNDvUQ@mail.gmail.com' \
--to=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).