On Wed, Nov 19, 2014 at 8:47 PM, Paulo Zanoni wrote:
>
> 2. How should the driver interface look like?
>
>a. All the possibilities are passed through the function call, so the
> drm.ko
> code needs to set the struct members itself.
>b. The caller already sets the struct members ins
On Thu, Nov 27, 2014 at 09:25:15AM +1000, Dave Airlie wrote:
> >> ---
> >> TL;DR summary:
> >> I wrote patches. Help me choose the best implementation and interface.
> >> ---
> >>
> >> So the i915.ko driver could use some mechanism to run functions after a
> >> given
> >> number of vblanks. Implem
>> ---
>> TL;DR summary:
>> I wrote patches. Help me choose the best implementation and interface.
>> ---
>>
>> So the i915.ko driver could use some mechanism to run functions after a given
>> number of vblanks. Implementations for this mechanism were already proposed
>> in
>> the past (by Chris W
On Wed, Nov 19, 2014 at 05:47:07PM -0200, Paulo Zanoni wrote:
> From: Paulo Zanoni
>
> Hi
>
> ---
> TL;DR summary:
> I wrote patches. Help me choose the best implementation and interface.
> ---
>
> So the i915.ko driver could use some mechanism to run functions after a given
> number of vblanks
From: Paulo Zanoni
Hi
---
TL;DR summary:
I wrote patches. Help me choose the best implementation and interface.
---
So the i915.ko driver could use some mechanism to run functions after a given
number of vblanks. Implementations for this mechanism were already proposed in
the past (by Chris Wil
