Skip to content
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

Add missing input devices #6

Open
Eeems opened this issue Oct 5, 2023 · 2 comments
Open

Add missing input devices #6

Eeems opened this issue Oct 5, 2023 · 2 comments

Comments

@Eeems
Copy link
Contributor

Eeems commented Oct 5, 2023

I've been poking around with running applications from toltec in the emulator, and quite a few of them hard code the input paths, which cause them to crash when attempting to run them. For example chessmarkable will panic if you try to run it. While it would be best to solve this by having the emulator expose the devices, another workaround would be to update the rm2fb client to spoof those paths.

@Eeems
Copy link
Contributor Author

Eeems commented Oct 5, 2023

reMarkable: ~/ LD_PRELOAD=/home/root/librm2fb_client.so chessmarkable
[2023-10-05T22:32:45Z DEBUG chessmarkable] Debug Mode is enabled by default.
    To change this, set the env "RUST_LOG" something else (e.g. info, warn, error or comma separated list of "[module=]<level>").
[2023-10-05T22:32:45Z INFO  chessmarkable::savestates] Savestates file doesn't exist (yet).
thread 'main' panicked at 'Failed to find the multitouch evdev!', /root/.cargo/registry/src/6github.com-1ecc6299db9ec823/libremarkable-0.4.3/src/input/scan.rs:114:13
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

@fenollp
Copy link
Contributor

fenollp commented Oct 9, 2023

I have the same issue (I'm also using libremarkable).

How does one expose udev devices with QEMU? I'd like to help

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants