On 02.07.2014 12:11, Michel D?nzer wrote:
> On 02.07.2014 12:01, Dieter N?tzel wrote:
>> Am 02.07.2014 02:29, schrieb Michel D?nzer:
>>> On 02.07.2014 01:46, Dieter N?tzel wrote:
Am 01.07.2014 10:14, schrieb Michel D?nzer:
> From: Michel D?nzer
>
> But move the programming back to
On 02.07.2014 12:01, Dieter N?tzel wrote:
> Am 02.07.2014 02:29, schrieb Michel D?nzer:
>> On 02.07.2014 01:46, Dieter N?tzel wrote:
>>> Am 01.07.2014 10:14, schrieb Michel D?nzer:
From: Michel D?nzer
But move the programming back to the vertical blank interrupt handler.
And si
On 02.07.2014 01:46, Dieter N?tzel wrote:
> Am 01.07.2014 10:14, schrieb Michel D?nzer:
>> From: Michel D?nzer
>>
>> But move the programming back to the vertical blank interrupt handler.
>> And signal the flip as being completed immediately after programming it
>> to the hardware.
>>
>> This way
Am 02.07.2014 02:29, schrieb Michel D?nzer:
> On 02.07.2014 01:46, Dieter N?tzel wrote:
>> Am 01.07.2014 10:14, schrieb Michel D?nzer:
>>> From: Michel D?nzer
>>>
>>> But move the programming back to the vertical blank interrupt
>>> handler.
>>> And signal the flip as being completed immediately
Am 01.07.2014 10:14, schrieb Michel D?nzer:
> From: Michel D?nzer
>
> But move the programming back to the vertical blank interrupt handler.
> And signal the flip as being completed immediately after programming it
> to the hardware.
>
> This way we don't have to guess whether or not the hardwar
From: Michel D?nzer
But move the programming back to the vertical blank interrupt handler.
And signal the flip as being completed immediately after programming it
to the hardware.
This way we don't have to guess whether or not the hardware will execute
the flip in a given vertical blank period,
Am 01.07.2014 10:14, schrieb Michel D?nzer:
> From: Michel D?nzer
>
> But move the programming back to the vertical blank interrupt handler.
> And signal the flip as being completed immediately after programming it
> to the hardware.
>
> This way we don't have to guess whether or not the hardware