[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20070331154318.05724805.zaitcev@redhat.com>
Date: Sat, 31 Mar 2007 15:43:18 -0700
From: Pete Zaitcev <zaitcev@...hat.com>
To: Jiri Kosina <jkosina@...e.cz>
Cc: dtor@...ightbb.com, linux-usb-devel@...ts.sourceforge.net,
linux-kernel@...r.kernel.org, stuard_hayes@...l.com,
zaitcev@...hat.com
Subject: Re: usb hid: reset NumLock
On Sat, 31 Mar 2007 21:35:19 +0200 (CEST), Jiri Kosina <jkosina@...e.cz> wrote:
> On Fri, 30 Mar 2007, Pete Zaitcev wrote:
> I think I see an issue here. Imagine that you boot a system initially with
> one keyboard connected (usb, ps/2, doesn't matter), and after some time
> you connect second USB keyboard (the NumLock is 'on' on the first keyboard
> when you connect the second one).
>
> Without your patch, the NumLock led will be OK on the second keyboard
> immediately. With your patch, the NumLock will be forced to 'off' and it
> will be out of sync with the first keyboard. The leds will get in sync
> later when any change occurs.
Oh, right, I missed it. The difficulty is how I rely on usages and fields
being already mapped by hidinput_configure_usage(). Thanks for letting me
know, I'll think about it.
-- Pete
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists