Tapani Pälli wrote:
Hmm let's see if we could come up with a nice solution with discussion.
Direct access to fb would mean permission problems. But there could be
another fb with different permissions (?) ... Maybe at first the tearing
should be solved at driver level so that client can request
ext Frantisek Dufka wrote:
> Tapani Pälli wrote:
>>> As for the manual vs automatic updates, that brings another question.
>>> How often is the screen really updated? I saw in the kernel source
>>> there is manual vs automatic update mode but which one is actualy
>>
>> We are updating areas (dirty
Tapani Pälli wrote:
As for the manual vs automatic updates, that brings another question.
How often is the screen really updated? I saw in the kernel source
there is manual vs automatic update mode but which one is actualy
We are updating areas (dirty-rects), it would hog the memorybus if we
w
ext Frantisek Dufka wrote:
> Eero Tamminen wrote:
>> Hi,
>>
>>> Yes. So to draw without tearing effect either X of framebuffer driver
>>> should report when to draw (vblank period or which line is currently
>>> drawn by hardware)
>>
>> Another possibility is that (SDL) application could ask X serve
Eero Tamminen wrote:
Hi,
Yes. So to draw without tearing effect either X of framebuffer driver
should report when to draw (vblank period or which line is currently
drawn by hardware)
Another possibility is that (SDL) application could ask X server to
ask Framebuffer to flush the framebuffer c
