On Fri, May 11, 2012 at 06:35:29PM +0200, Marc-André Lureau wrote:
> QXL_ESCAPE_SET_CUSTOM_DISPLAY is Windows specific message
> to tell the display & miniport driver to update the mode
> table with a custom resolution.
>
> The mode table needs to be forcefully refreshed after
> setting a custom display, it can be done by querying an
> invalid/unknown mode:
>
> EnumDisplaySettings(dev_name, 0xffffff, &tempDevMode);
> ---
> spice/Makefile.am | 1 +
> spice/qxl_windows.h | 20 ++++++++++++++++++++
> 2 files changed, 21 insertions(+)
> create mode 100644 spice/qxl_windows.h
>
> diff --git a/spice/Makefile.am b/spice/Makefile.am
> index 167b69c..a54ae89 100644
> --- a/spice/Makefile.am
> +++ b/spice/Makefile.am
> @@ -13,6 +13,7 @@ spice_protocol_include_HEADERS = \
> macros.h \
> protocol.h \
> qxl_dev.h \
> + qxl_windows.h \
> start-packed.h \
> stats.h \
> types.h \
> diff --git a/spice/qxl_windows.h b/spice/qxl_windows.h
> new file mode 100644
> index 0000000..d1df684
> --- /dev/null
> +++ b/spice/qxl_windows.h
> @@ -0,0 +1,20 @@
> +#ifndef _H_QXL_WINDOWS
> +#define _H_QXL_WINDOWS
> +
> +#include <spice/types.h>
> +
> +#include <spice/start-packed.h>
> +
> +enum {
> + QXL_ESCAPE_SET_CUSTOM_DISPLAY = 0x10001,
> +};
> +
> +typedef struct SPICE_ATTR_PACKED QXLEscapeSetCustomDisplay {
> + uint32_t xres;
> + uint32_t yres;
> + uint32_t bpp;
> +} QXLEscapeSetCustomDisplay;
Do you think we should add fields for later having multiple outputs on a
single device, i.e. VidPN ? ACK if you think this is premature.
> +
> +#include <spice/end-packed.h>
> +
> +#endif /* _H_QXL_WINDOWS */
> --
> 1.7.10.1
>
> _______________________________________________
> Spice-devel mailing list
> Spice-devel@xxxxxxxxxxxxxxxxxxxxx
> http://lists.freedesktop.org/mailman/listinfo/spice-devel
_______________________________________________
Spice-devel mailing list
Spice-devel@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/spice-devel