From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Domen Puncer <domen@coderock.org>
Cc: Mikkel Krautz <krautz@gmail.com>,
vojtech@ucw.cz, linux-kernel@vger.kernel.org, greg@kroah.com
Subject: Re: [PATCH] hid-core: Configurable USB HID Mouse Interrupt Polling Interval
Date: Mon, 07 Feb 2005 09:00:59 -0800 [thread overview]
Message-ID: <42079ECB.2090706@osdl.org> (raw)
In-Reply-To: <20050207171646.GB15840@nd47.coderock.org>
Domen Puncer wrote:
> On 07/02/05 07:59 -0800, Randy.Dunlap wrote:
>
>>>+static unsigned int hid_mousepoll_interval;
>>>+module_param_named(mousepoll, hid_mousepoll_interval, uint, 0644);
>>
>>Why is it writable by root? IOW, will writing a new value to it
>>change the operational value dynamically?
>>
>>Also, from the kernel-parameters.txt patch:
>>+ usbhid.mousepoll=
>>+ [USBHID] The interval at wich mice are to be polled at.
>>
>>(a) "which"
>>(b) drop one of the "at"s... either one.
>
>
> Is listing module parameters in kernel-parameters.txt the right thing
> to do? (There are lots of them, not many are listed)
It's currently the right thing to do, but some automated overhaul
sure would make sense.
> I see some options that might be better:
> - Kconfig magic which extracts module_param* and MODULE_PARM_DESC from
> sources and appends them to help text.
> - a userspace script, that goes trough all modules and generates
> kernel-module-parameters.txt for example.
> - modinfo like tool (but i think it would require source or descriptions
> compiled in kernel)
--
~Randy
next prev parent reply other threads:[~2005-02-07 17:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-07 15:44 [PATCH] hid-core: Configurable USB HID Mouse Interrupt Polling Interval Mikkel Krautz
2005-02-07 15:59 ` Randy.Dunlap
2005-02-07 17:16 ` Domen Puncer
2005-02-07 17:00 ` Randy.Dunlap [this message]
[not found] ` <20050207174303.GA3113@ucw.cz>
2005-02-07 17:51 ` Mikkel Krautz
2005-02-07 17:56 ` Mikkel Krautz
[not found] ` <20050207183818.GB2006@ucw.cz>
2005-02-07 18:41 ` Mikkel Krautz
-- strict thread matches above, loose matches on Subject: below --
2005-02-07 18:57 Mikkel Krautz
2005-02-08 15:15 ` zyphr
2005-02-08 16:02 ` Oliver Neukum
2005-02-08 16:09 ` Vojtech Pavlik
2005-02-07 16:46 Mikkel Krautz
2005-02-07 15:42 Mikkel Krautz
2004-12-18 2:12 Mikkel Krautz
2004-12-18 0:43 ` Gene Heskett
2004-12-18 1:27 ` Greg KH
2004-12-18 4:22 ` Mikkel Krautz
2004-12-18 3:36 ` Gene Heskett
2004-12-18 4:42 ` Mikkel Krautz
2004-12-18 2:59 ` Greg KH
2004-12-18 4:55 ` Mikkel Krautz
2004-12-18 17:39 ` Mikkel Krautz
2004-12-18 15:40 ` Marcel Holtmann
2004-12-18 17:44 ` Mikkel Krautz
2004-12-18 16:53 ` Greg KH
2004-12-19 1:52 ` Mikkel Krautz
2005-02-06 19:07 ` Vojtech Pavlik
2005-02-06 20:00 ` Mikkel Krautz
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=42079ECB.2090706@osdl.org \
--to=rddunlap@osdl.org \
--cc=domen@coderock.org \
--cc=greg@kroah.com \
--cc=krautz@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@ucw.cz \
/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