On 07/02/2018 09:12 AM, Oleksandr Andrushchenko wrote:
> On 07/02/2018 11:20 AM, Juergen Gross wrote:
>> On 02/07/18 09:10, Oleksandr Andrushchenko wrote:
>>> Hello, Boris, Juergen!
>>>
>>> Do you think I can re-base the series (which already has
>>> all required R-b's from Xen community) onto the
On 07/02/2018 11:20 AM, Juergen Gross wrote:
On 02/07/18 09:10, Oleksandr Andrushchenko wrote:
Hello, Boris, Juergen!
Do you think I can re-base the series (which already has
all required R-b's from Xen community) onto the latest kernel
with API changes to patches 5 (of_dma_configure) and 8
On 02/07/18 09:10, Oleksandr Andrushchenko wrote:
> Hello, Boris, Juergen!
>
> Do you think I can re-base the series (which already has
> all required R-b's from Xen community) onto the latest kernel
> with API changes to patches 5 (of_dma_configure) and 8
> (dma-buf atomic ops) and we can merge
Boris, Juergen!
Thank you so much for your comments and time spent on this
series. Appreciate that very much!
Thank you,
Oleksandr
On 06/15/2018 09:27 AM, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko
This work is in response to my previous attempt to introduce Xen/DRM
From: Oleksandr Andrushchenko
This work is in response to my previous attempt to introduce Xen/DRM
zero-copy driver [1] to enable Linux dma-buf API [2] for Xen based
frontends/backends. There is also an existing hyper_dmabuf approach
available [3] which, if reworked to utilize the proposed
