On Tue, Feb 19, 2013 at 1:49 PM, Chris Wilson <chris at chris-wilson.co.uk> wrote: > On Tue, Feb 19, 2013 at 01:30:40PM +0100, Daniel Vetter wrote: >> They reliably cause HDMI to not be detected on some systems (like my >> ivb or the bug reporters gm45). To fix up the very slow unplug issues >> we might want to fire up a 2nd detect cycle a few hundred ms after >> each hotplug. But for now at least make displays work again. > > If the status bit is not being set, how is the hotplug event being > generated? Is it ever set? > > Before we throw it away, I'd just like to have a little more evidence > that it is unsalvageable. Bug reporter is a bit unresponsive, but the bit simply isn't ever set. On my ivb here it seems to not work at all (i.e. even the hotplug interrupt doesn't happen ...). I dunno what exactly to do with that. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch
