From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: is there a reason "usbhid.quirks" parameter is not root writable?
Date: Thu, 12 Nov 2015 17:31:06 -0800 [thread overview]
Message-ID: <20151113013106.GA26907@kroah.com> (raw)
In-Reply-To: <43522.1447376520@turing-police.cc.vt.edu>
On Thu, Nov 12, 2015 at 08:02:00PM -0500, Valdis.Kletnieks at vt.edu wrote:
> 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....
To do that you now need to keep a separate dynmic list of ids that you
also need to check, and clean up when shut down, it's not as "simple" as
you might think. Not impossible, we do it for lots of other places, and
the hid core does handle dynamic quirks as I pointed out, so you should
be fine.
If people have questions about this, please ask them on the linux-input
mailing list, where the HID developers are at.
thanks,
greg k-h
next prev parent reply other threads:[~2015-11-13 1:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 10:15 is there a reason "usbhid.quirks" parameter is not root writable? Robert P. J. Day
2015-11-13 0:44 ` Greg KH
2015-11-13 1:02 ` Valdis.Kletnieks at vt.edu
2015-11-13 1:31 ` Greg KH [this message]
2015-11-13 7:53 ` Robert P. J. Day
2015-11-13 8:11 ` Bjørn Mork
2015-11-13 8:24 ` Robert P. J. Day
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151113013106.GA26907@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).