UDEV Rule for Joystick/JS0
by triley831 from LinuxQuestions.org on (#4STFK)
Good afternoon Community,
hoping someone can give some advice. We have a joystick running on a piece of equipment running RHEL 7.7 server that has software that looks for the joystick at JS0. However, something else on the system is grabbing js0 and leaving the Joystick to use JS1.
I was thinking I could write a udev rule to force the joystick to use JS0, but have a question related to the last parameter of the rule.
Using the "hwinfo --usb" command I can easily get the device path. So currently here is how my rule looks:
SUBSYSTEM=="net", ACTION=="add", DEVPATH=="/devices/pci0000:00/0000:00:14.0/usb3/3-11/e-11.4/3-11.4.3/3.11.4.3:1.0/input/*", NAME=js0
Of course this rule isn't working to force the joystick on js0. I think the problem is with the end of my rule in that I used "NAME". I don't think I can use this parameter for js0. But I don't know how to describe (or if I can) in a udev rule, what js0 is.
THanks in advance for any info that can be provided
hoping someone can give some advice. We have a joystick running on a piece of equipment running RHEL 7.7 server that has software that looks for the joystick at JS0. However, something else on the system is grabbing js0 and leaving the Joystick to use JS1.
I was thinking I could write a udev rule to force the joystick to use JS0, but have a question related to the last parameter of the rule.
Using the "hwinfo --usb" command I can easily get the device path. So currently here is how my rule looks:
SUBSYSTEM=="net", ACTION=="add", DEVPATH=="/devices/pci0000:00/0000:00:14.0/usb3/3-11/e-11.4/3-11.4.3/3.11.4.3:1.0/input/*", NAME=js0
Of course this rule isn't working to force the joystick on js0. I think the problem is with the end of my rule in that I used "NAME". I don't think I can use this parameter for js0. But I don't know how to describe (or if I can) in a udev rule, what js0 is.
THanks in advance for any info that can be provided