On Mon, Jun 10, 2013 at 12:27 AM, Chris Wilson
wrote:
> It is these machines that require the per-connector quirk to turn off
> hotplug detection anyway. And there are users that need to turn off all
> hotplug detection (hardware and polling) on certain connectors whilst
> plugged into their kvm.
On Mon, Jun 10, 2013 at 12:27 AM, Chris Wilson wrote:
> It is these machines that require the per-connector quirk to turn off
> hotplug detection anyway. And there are users that need to turn off all
> hotplug detection (hardware and polling) on certain connectors whilst
> plugged into their kvm.
On Sat, Jun 08, 2013 at 02:34:20PM +0200, Daniel Vetter wrote:
> On Sat, Jun 8, 2013 at 9:08 AM, Chris Wilson
> wrote:
> > On Wed, Jun 05, 2013 at 10:59:23PM +0100, Chris Wilson wrote:
> >> It is useful for userspace to know when it may be able to skip a forced
> >> detection cycle as the connect
On Sat, Jun 08, 2013 at 02:34:20PM +0200, Daniel Vetter wrote:
> On Sat, Jun 8, 2013 at 9:08 AM, Chris Wilson wrote:
> > On Wed, Jun 05, 2013 at 10:59:23PM +0100, Chris Wilson wrote:
> >> It is useful for userspace to know when it may be able to skip a forced
> >> detection cycle as the connector
On Sat, Jun 8, 2013 at 9:08 AM, Chris Wilson
wrote:
> On Wed, Jun 05, 2013 at 10:59:23PM +0100, Chris Wilson wrote:
>> It is useful for userspace to know when it may be able to skip a forced
>> detection cycle as the connector maintains an accurate status. It also
>> provides status feedback to t
On Sat, Jun 8, 2013 at 9:08 AM, Chris Wilson wrote:
> On Wed, Jun 05, 2013 at 10:59:23PM +0100, Chris Wilson wrote:
>> It is useful for userspace to know when it may be able to skip a forced
>> detection cycle as the connector maintains an accurate status. It also
>> provides status feedback to th
