From mboxrd@z Thu Jan 1 00:00:00 1970 From: Valdis.Kletnieks@vt.edu (Valdis.Kletnieks at vt.edu) Date: Thu, 12 Nov 2015 20:02:00 -0500 Subject: is there a reason "usbhid.quirks" parameter is not root writable? In-Reply-To: <20151113004435.GA25513@kroah.com> References: <20151113004435.GA25513@kroah.com> Message-ID: <43522.1447376520@turing-police.cc.vt.edu> To: kernelnewbies@lists.kernelnewbies.org List-Id: kernelnewbies.lists.kernelnewbies.org On Thu, 12 Nov 2015 16:44:35 -0800, Greg KH said: > On Thu, Nov 12, 2015 at 03:15:41AM -0700, Robert P. J. Day wrote: > > module_param_array_named(quirks, quirks_param, charp, NULL, 0444); > > MODULE_PARM_DESC(quirks, "Add/modify USB HID quirks by specifying " > > You can add a runtime quirk to the device itself when it shows up in > sysfs for the hid driver. Use that instead of the module parameter for > that specific device. That's a workaround. Still unexplained is why it's mode 0444 for "add/modify". But to answer Robert's question: I suspect that it's mode 0444 so you can read the current list, but changing the list after modprobe time is for some reason problematic. Having said that, I admit I haven't looked at the source deep enough to find the exact reason. It's probably something subtle, because simply adding an ID to a list of IDs shouldn't be that hard.... -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 848 bytes Desc: not available Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20151112/a7eb0f33/attachment.bin