> simon@xxxxxxxxxxxxx writes: >>> In line with practice for module parameters, we're adding a build-time >>> check that sysfs files aren't world-writable. >> >> So this is the equivalent of 'chmod 774 ...' rather than 'chmod >> 777...'? > > Yep. Though not sure why it was 777 rather than 666... > >> Yep I'm OK with that, however what it the recommended way to make sure >> that the end user is able to send changes to this /sys portal? I asked >> the >> same question before regarding the led class /sys interface, but never >> got >> any suggestions. >> >> Signed-off-by: Simon Wood <simon@xxxxxxxxxxxxx> > > If you need that, we'll need to make an exception. That's one purpose > of spamming everyone with these changs... What's the right way of doing it?... I don't need to be 'special'. ;-) The '/sys/.../range' control allows the user to limit the rotation of the gaming wheel from a maximum of 900' down to match the 'car' they sim-driving. Probably not many people use it, but it probably should be assigned properly. With gaming controllers the /dev/input/event* seem to get set appropriately, but I'm not sure how this happens. The same /should/ also happen for all the LED class controls, I don't want to have to 'sudo' just to set a LED on/off. This is currently a problem for (at least) hid-lg, hid-sony and hid-steelseries. Simon -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
