Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

In the repo I linked somehow they get this "damage" information from the Linux kernel where it's already being computed.


I will have a look, but at first sight it looks like the repo you mentioned is for reMarkable first version which is using a kernel based implementation of the Framebuffer. It is a bit different for reMarkable2 as the framebuffer is managed by the main process




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: