Closed raisjn closed 3 years ago
some possible solutions:
another solution proposed (by bokluk) is to use semaphores and would work something like:
when WAIT ioctl is issued on the client:
first attempt in https://github.com/ddvk/remarkable2-framebuffer/pull/45. this solves some weird behavior i was seeing in an app previously and i expect it should work in other places too
in mxcfb on rM1, using ioctl there is ability to do:
in rm2fb, there is no longer the "wait for update" ability due to two things:
1) there's only single way communication from client -> server 2) the framebuffer API has a command, "waitForLastUpdate()" but it does not support supplying a marker ID (i think). translating "send_update; wait_for_update ID" into "send_update; waitForLastUpdate()" requires knowing when to call waitForLastUpate() after drawing an update, but the
wait_for_update
can come at any arbitrary time and we process the incoming events in order.this task is to give the ability for rM2 apps to wait for a previous draw to finish.