LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Chuck Ebbert <cebbert@redhat.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Pete Zaitcev <zaitcev@redhat.com>,
	linux-kernel@vger.kernel.org,
	linux-input@atrey.karlin.mff.cuni.cz,
	Peter Osterlund <petero2@telia.com>
Subject: Re: Fix sudden warps in mousedev
Date: Tue, 27 Mar 2007 12:04:47 -0400	[thread overview]
Message-ID: <4609409F.2070203@redhat.com> (raw)
In-Reply-To: <d120d5000703270846y87e4283m4009ff0a9f65dac4@mail.gmail.com>

Dmitry Torokhov wrote:
>>
>> And why did the mouse numbers all get rearranged in 2.6.20, e.g.
>> mouse1 became mouse2 for many people?
> 
> Input devices are not guaranteed to be stable.
> 

So people with z-axis mice need to redo their X config for each
kernel release when the device numbers change? Or should they
be using some other configuration?

People using this now have X crashes on kernel upgrade because
event1 became event2:

        Driver      "evdev"
        Option      "Device" "/dev/input/event1"


  reply	other threads:[~2007-03-27 16:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-24  7:16 Fix sudden warps in mousedev Pete Zaitcev
     [not found] ` <200703250134.03416.dtor@insightbb.com>
2007-03-25 18:19   ` Pete Zaitcev
2007-03-26  3:19     ` Dmitry Torokhov
2007-03-26 19:17       ` Pete Zaitcev
2007-03-26 19:30         ` Dmitry Torokhov
2007-03-26 21:42           ` Pete Zaitcev
2007-03-27  1:14             ` Dmitry Torokhov
2007-03-27 15:14               ` Chuck Ebbert
2007-03-27 15:46                 ` Dmitry Torokhov
2007-03-27 16:04                   ` Chuck Ebbert [this message]
2007-03-27 16:19                     ` Dmitry Torokhov
2007-03-28 20:51                       ` Matt Keenan
2007-04-11 21:51               ` Peter Osterlund

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=4609409F.2070203@redhat.com \
    --to=cebbert@redhat.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@atrey.karlin.mff.cuni.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=petero2@telia.com \
    --cc=zaitcev@redhat.com \
    /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).