Re: Atomic driver and old remove FB behavior

Hi, Maarten! On 02/06/2018 05:37 PM, Maarten Lankhorst wrote: Op 06-02-18 om 15:43 schreef Oleksandr Andrushchenko: Hello, Maarten! On 02/01/2018 12:13 PM, Oleksandr Andrushchenko wrote: On 02/01/2018 12:04 PM, Maarten Lankhorst wrote: Op 01-02-18 om 08:08 schreef Oleksandr Andrushchenko:

Re: Atomic driver and old remove FB behavior

Op 06-02-18 om 15:43 schreef Oleksandr Andrushchenko: > Hello, Maarten! > > > On 02/01/2018 12:13 PM, Oleksandr Andrushchenko wrote: >> On 02/01/2018 12:04 PM, Maarten Lankhorst wrote: >>> Op 01-02-18 om 08:08 schreef Oleksandr Andrushchenko: Hi, all! I am working on a

Re: Atomic driver and old remove FB behavior

Hello, Maarten! On 02/01/2018 12:13 PM, Oleksandr Andrushchenko wrote: On 02/01/2018 12:04 PM, Maarten Lankhorst wrote: Op 01-02-18 om 08:08 schreef Oleksandr Andrushchenko: Hi, all! I am working on a para-virtualized frontend DRM driver for Xen [1] which implements display device I/O

Re: Atomic driver and old remove FB behavior

On 02/01/2018 12:04 PM, Maarten Lankhorst wrote: Op 01-02-18 om 08:08 schreef Oleksandr Andrushchenko: Hi, all! I am working on a para-virtualized frontend DRM driver for Xen [1] which implements display device I/O interface for Xen guest OSes [2]. At the moment I am rebasing the existing

Re: Atomic driver and old remove FB behavior

Op 01-02-18 om 08:08 schreef Oleksandr Andrushchenko: > Hi, all! > > I am working on a para-virtualized frontend DRM driver for Xen [1] > which implements display device I/O interface for Xen guest OSes [2]. > > At the moment I am rebasing the existing implementation from 4.9 kernel > to recent

Atomic driver and old remove FB behavior

Hi, all! I am working on a para-virtualized frontend DRM driver for Xen [1] which implements display device I/O interface for Xen guest OSes [2]. At the moment I am rebasing the existing implementation from 4.9 kernel to recent and found that when user-space DRM application exits then CRTC's