On Tue, 4 Apr 2017 17:52:20 +0100
Daniel Stone wrote:
> From: Ander Conselvan de Oliveira
>
> When using the atomic API, one request can span multiple CRTCs, however
> one event is generated per CRTC. As we cannot disambiguate the CRTC with
> user data (since we only have one piece of user dat
Hi Emil,
On Tue, 2017-04-04 at 18:12 +0100, Emil Velikov wrote:
> On 4 April 2017 at 17:52, Daniel Stone wrote:
> > @@ -846,7 +847,7 @@ struct drm_event_vblank {
> > __u32 tv_sec;
> > __u32 tv_usec;
> > __u32 sequence;
> > - __u32 reserved;
> > + __u32 crtc_id;
Hi Daniel,
Zero objections against the patch, just a couple of small notes.
On 4 April 2017 at 17:52, Daniel Stone wrote:
> From: Ander Conselvan de Oliveira
>
> When using the atomic API, one request can span multiple CRTCs, however
> one event is generated per CRTC. As we cannot disambiguate
From: Ander Conselvan de Oliveira
When using the atomic API, one request can span multiple CRTCs, however
one event is generated per CRTC. As we cannot disambiguate the CRTC with
user data (since we only have one piece of user data to pass in), newer
kernels can include the CRTC ID in the page fl
