From: Ali Akcaagac <aliakc@web.de>
To: dtor_core@ameritech.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] 2.6.12-rc1/rc2 mouse0 became mouse1
Date: Fri, 08 Apr 2005 17:51:45 +0200 [thread overview]
Message-ID: <1112975505.1813.0.camel@localhost> (raw)
In-Reply-To: <d120d50005040807135bd29429@mail.gmail.com>
On Fri, 2005-04-08 at 09:13 -0500, Dmitry Torokhov wrote:
> Input devices names are not guaranteed to be stable, they get them in
> order of their registration and therefore can change based on config,
> order in which modules are loaded and changes in other modules. In
> this case shift was caused by scroll support recently added to atkbd.
>
> Ideally hotplug system should notify interested parties about current
> layout, but for programs that do not support dynamic setup changes
> please use mice multiplexor device (/dev/input/mice) that gives access
> to data from _all_ mouse-like devices in the system.
>
> Hope that helps.
I see, thank you... Good to know this wasn't a bug or something.
next prev parent reply other threads:[~2005-04-08 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-08 11:58 [BUG] 2.6.12-rc1/rc2 mouse0 became mouse1 Ali Akcaagac
2005-04-08 14:13 ` Dmitry Torokhov
2005-04-08 15:51 ` Ali Akcaagac [this message]
2005-04-14 19:21 ` Pavel Machek
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=1112975505.1813.0.camel@localhost \
--to=aliakc@web.de \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.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