On 04/04/2017 11:07 PM, Konrad Rzeszutek Wilk wrote:
.snip..
+ *- Protocol version --
+ *
+ * version
+ * Values:
+ *
+ * Protocol version, chosen among the ones supported by the backend.
+ *
..snip..
+#define
.snip..
> > + *- Protocol version
> > --
> > + *
> > + * version
> > + * Values:
> > + *
> > + * Protocol version, chosen among the ones supported by the backend.
> > + *
..snip..
> > +#define XENDISPL_FIELD_BE_VERSIONS
Hi, Konrad!
On 04/04/2017 10:38 PM, Konrad Rzeszutek Wilk wrote:
Hey!
I only had minor comments - and if you are OK with them
comments seem to be reasonable to me
I can also
put them in the patch when checking them in
Please, do me a favor
(or if you want you can
repost it right away
Hey!
I only had minor comments - and if you are OK with them I can also
put them in the patch when checking them in (or if you want you can
repost it right away and I will check in the new version).
>
> ---
> Changes since v3:
> * add clarification on buffer's size/depth/format and
>
ping
On 03/20/2017 10:56 AM, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko
This is the ABI for the two halves of a para-virtualized
display driver.
This protocol aims to provide a unified protocol which fits more
sophisticated use-cases than
From: Oleksandr Andrushchenko
This is the ABI for the two halves of a para-virtualized
display driver.
This protocol aims to provide a unified protocol which fits more
sophisticated use-cases than a framebuffer device can handle. At the
moment basic
From: Oleksandr Andrushchenko
This is the ABI for the two halves of a para-virtualized
display driver.
This protocol aims to provide a unified protocol which fits more
sophisticated use-cases than a framebuffer device can handle. At the
moment basic