-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make qemu images for the reMarkable #21
Comments
Are you aware of https://github.com/evidlo/remarkable_sim ? |
yes, we helped build resim by making sure it sent the proper events and the correct coordinates: https://github.com/rmkit-dev/remarkable_sim rmkit supports resim (is the only project to support it, afaik) bc resim was created to address the problems with rmkit''s viewer.py. but resim is not enough, i want testing that simulates the device through qemu. perhaps using resim is a good first step though for projects that can work with resim |
also, I'm not sure this is not a toolchain issue, it is for CI testing of built apps, to make sure installation works and other common tasks |
Well, it's a bit in-between, since if I understand correctly we'll need to have a replica of the reMarkable system for this to work. In particular, we'll need to have the same set of available libs. |
Transferring this to a more general repo since it’s not totally in scope for the toolchain repo. |
bordaigorl/rmview#22 (comment) is relevant explanation from @pl-semiotics on how to set something like this up |
I managed to make a QEMU VM run the rM stock system. There’s still a lot of work remaining to make the emulation closer to the true device, though. Here are some notes on how I got it working: https://gist.github.com/matteodelabre/92599920b46e5fac9daf58670d367950 |
it would be really cool if we were able to run a qemu image with arm and emulate the rM execution environment. we could then run tests, take screenshots and do other things from a CI machine
The text was updated successfully, but these errors were encountered: