Kai Krakow

The extra data may be 127 keyboard bits as the controller supports mapping keyboard events. In HID mode (Bluetooth), the extra data in the reports actually map to keyboard events.

There's already an open PR implementing systemd logging. Maybe you could build upon that? It's a part of this commit series: https://github.com/medusalix/xow/pull/100/commits This also migrates to using the native syslog...

Feel free to cherry pick the three log related commits, then rebase yours to these. It would make merging easier later. I'm not sure when @medusalix is able to review...

I created these to beautify systemd logging (it didn't like the duplicate timestamp it was creating), and it has simple support for sending the log level through stderr/stdout by prepending...

> I don't like much mixing PR that do too much different things Actually, the logging commits should have been a separate PR anyways, I added these later and it's...

Usually logging to systemd is as simple as writing to stdout/stderr, the output will be captured, prepended with a timestamp and redirected to the journal, optionally you can add a...

The latest kernels contain a patch that returns `EINVAL` on out-of-bounds access during `ioctl()`, maybe that's the cause? https://github.com/kakra/linux/commit/851d0813ab80b47d3d85617d81836891bfb59094 Also, maybe some initialization is missing? Because there's another commit that...

No, those links do not point to anything to "install". You'd probably need build the xanmod kernel yourself. There should be a source package available for it for your distribution....

I didn't change anything about those commits. You should clone the xanmod kernel locally, then use `git revert ` to revert one of the changes that I think may introduce...

If this problem occurs during rumbles, it may be fixed by #100