On Wed, May 5, 2010 at 11:37 AM, Jesse Barnes <jbar...@virtuousgeek.org> wrote: > On Wed, 5 May 2010 11:12:13 +1000 > Dave Airlie <airl...@gmail.com> wrote: >> So at startup X drivers genearlly seem to ask for a list of >> connectors and status for them, and if it can't find any connected, >> it goes to unknown, and if none of those they fall over and X exits. >> Idea 1 was to just pick a connector and claim it is connected when >> nothing else is, however this falls over, for DVI esp on a dual-DVI >> card. You pick a DVI connector, claim it is connected, you most >> likely end up turning on the analog portion of it, you hotplug a >> digital connector and the uevent gets sent, the client app repolls >> the connector status, sees the connector is still connected so >> doesn't do anything. Forcing a disconnect/connect is incredibly racy >> and hard. So Ben Skeggs suggested we just fake a disconnected >> connector for this case. It looks a bit messy in xrandr, but from >> what I can see the gnome client ignores it as it should. > > It's an ugly problem... When the hotplug event is received, wouldn't > you re-probe and find a digital monitor attached? If so, that would > mean a mode set sent in by the X server should end up being a full one > since the current config is incompatible. Which means X just has to > know it forced a mode, so when any event comes in it should re-set the > mode unconditionally...
Userspace (as in gnome/kde/xrandr) doesn't know what is attached, digital or analog, it just sees a connected status, notices it was connected before, it still connected and doesn't do anything. Dave. ------------------------------------------------------------------------------ -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
