As per the title. I was able to hack a workaround by modifying the 50-legion_go.yaml file to explicitly only hide the touchpad and keyboard devices from evdev, thereby allowing the mouse device through; but I feel it would be more in keeping with the spirit of this program to pass these through as emulated events.
Running native SteamOS (from the latest image on their website), inputplumber 0.58.0-1 according to pacman.
One thing I did note that seems to be odd is that running inputplumber device 0 targets list returns a single device of the type deck-uhid, as opposed to the four devices suggested in the YAML profile. As far as I can tell, this should only be triggered on the Legion Go S, not the original Legion Go in use here, Not sure if it’s related, but I thought it worth mentioning.
As per the title. I was able to hack a workaround by modifying the 50-legion_go.yaml file to explicitly only hide the touchpad and keyboard devices from evdev, thereby allowing the mouse device through; but I feel it would be more in keeping with the spirit of this program to pass these through as emulated events.
Running native SteamOS (from the latest image on their website), inputplumber 0.58.0-1 according to pacman.
One thing I did note that seems to be odd is that running
inputplumber device 0 targets listreturns a single device of the typedeck-uhid, as opposed to the four devices suggested in the YAML profile. As far as I can tell, this should only be triggered on the Legion Go S, not the original Legion Go in use here, Not sure if it’s related, but I thought it worth mentioning.