From: Soeren Sonnenburg <kernel@nn7.de>
To: Jiri Kosina <jikos@jikos.cz>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
linux-usb-devel <linux-usb-devel@lists.sourceforge.net>
Subject: Re: 2.6.20-rc6 pb_fnmode regression
Date: Mon, 29 Jan 2007 11:32:17 +0100 [thread overview]
Message-ID: <1170066737.13904.12.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.64.0701291049190.9448@twin.jikos.cz>
On Mon, 2007-01-29 at 10:55 +0100, Jiri Kosina wrote:
> On Sat, 27 Jan 2007, Soeren Sonnenburg wrote:
>
> > I realized that any setting to /sys/module/usbhid/parameters/pb_fnmode
> > is just ignored until the machine does a suspend-resume cycle.
[...]
> I would rather be inclined to just make the
> /sys/module/usbhid/parameters/pb_fnmode read-only (which is what most of
> the drivers do anyway), to avoid this kind of confusion.
>
> Do you have really any strong use-case, when setting the parameter during
> runtime would be much more useful than just do it during modprobe or
> rmmod/modprobe cycle?
Well I need in-kernel usbhid and the way this was implemented in 2.6.19
(and before) one could change pb_fnmode on-the-fly. This is mentioned in
all the power/i/mac/book tutorials and everyone is used to switching
modes this way.
I can happily patch the kernel to use the pb_fnmode but nonetheless this
is a regression to pre 2.6.20* and will confuse others too...
Soeren
--
Sometimes, there's a moment as you're waking, when you become aware of
the real world around you, but you're still dreaming.
next prev parent reply other threads:[~2007-01-29 10:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-27 13:29 2.6.20-rc6 pb_fnmode regression Soeren Sonnenburg
2007-01-29 9:55 ` Jiri Kosina
2007-01-29 10:26 ` [linux-usb-devel] " Sergey Vlasov
2007-01-29 10:32 ` Soeren Sonnenburg [this message]
2007-01-29 10:40 ` Jiri Kosina
2007-01-29 11:13 ` Jiri Kosina
2007-01-29 11:24 ` Soeren Sonnenburg
2007-01-29 11:45 ` Jiri Kosina
2007-01-29 15:12 ` Soeren Sonnenburg
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=1170066737.13904.12.camel@localhost \
--to=kernel@nn7.de \
--cc=jikos@jikos.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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