4 ms·
xochitl (the rM GUI) doesn't need to be run when other GUI programs are running. I don't fully understand the way this works but for anyone interested, here is
by eloeffler 5y ago
xochitl (the rM GUI) doesn't need to be run when other GUI programs are running. I don't fully understand the way this works but for anyone interested, here is the link for the framebuffer workaround: https://github.com/ddvk/remarkable2-framebuffer https://github.com/ddvk/remarkable2-framebuffer
On rM1 it was possible to write to the framebuffer directly, on rM2 it is not exposed as a device file directly.
- AshamedCaptain 5y agoThe link you are sharing explicitly mentions you need xochitl running with the LD_PRELOAD hack, which is what becomes "the framebuffer server". In fact, > To do their job, both the client and the server need to know the address at which a number of functions reside in the Xochitl binary. These addresses change from one release to the next. This is absurdly fragile. In fact, it's even worse than I was guessing :/.
- eloeffler 5y agoHuh, I really had the wrong idea... Thanks. I'm still very happy with the device but I'll keep that in mind when recommending it to others.