On Mon, Aug 15, 2016 at 4:05 AM, Emil Velikov
wrote:
> On 11 August 2016 at 23:26, Kevin Strasser
> wrote:
> > Some applications continue to use the Xlib client library and expect that
> > VK_KHR_xlib_surface will be available in the driver. Service these
> > applications by converting the Displ
On 11 August 2016 at 23:26, Kevin Strasser wrote:
> Some applications continue to use the Xlib client library and expect that
> VK_KHR_xlib_surface will be available in the driver. Service these
> applications by converting the Display pointer to xcb_connection_t and use
> the existing xcb code in
Some applications continue to use the Xlib client library and expect that
VK_KHR_xlib_surface will be available in the driver. Service these
applications by converting the Display pointer to xcb_connection_t and use
the existing xcb code in the driver.
Signed-off-by: Kevin Strasser
Cc: Jason Ekst
On Thu, Aug 11, 2016 at 3:26 PM, Kevin Strasser
wrote:
> Some applications continue to use the Xlib client library and expect that
> VK_KHR_xlib_surface will be available in the driver. Service these
> applications by converting the Display pointer to xcb_connection_t and use
> the existing xcb c
Some applications continue to use the Xlib client library and expect that
VK_KHR_xlib_surface will be available in the driver. Service these
applications by converting the Display pointer to xcb_connection_t and use
the existing xcb code in the driver.
Signed-off-by: Kevin Strasser
Cc: Jason Ekst
