Daniel Martin <[email protected]> writes:

> From: Daniel Martin <[email protected]>
>
> When receiving a hotplug uevent, check if we have to add or remove
> outputs and act accordingly.
>
> Signed-off-by: Daniel Martin <[email protected]>
> ---
> With this patch we create or destroy outputs as a reaction to uevents.
>
> Due to my limited experience, the solution is either total crap, cause
> I'm doing it wrong, or it is that complicated, cause the server never
> had disappearing outputs in mind, or a combination of both.

Both of these patches look awesome; RandR and the xf86 code is all
designed to support output/crtc hot-plugging, but we've never had a
driver that did it.

I've reviewed the code, and it looks correct. As it's essentially new
functionality, it would normally wait until after 1.17 anyways, but in
this case, we should wait until we have some way of testing it before
merging it in.

For 7/8 and 8/8 in this series:

Reviewed-by: Keith Packard <[email protected]>

-- 
[email protected]

Attachment: signature.asc
Description: PGP signature

_______________________________________________
[email protected]: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: http://lists.x.org/mailman/listinfo/xorg-devel

Reply via email to