All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Keenan <tank.en.mate@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Chuck Ebbert <cebbert@redhat.com>,
	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: Wed, 28 Mar 2007 21:51:34 +0100	[thread overview]
Message-ID: <460AD556.9090408@gmail.com> (raw)
In-Reply-To: <d120d5000703270919y16ae3e56kb7d2fbd293213939@mail.gmail.com>

Dmitry Torokhov wrote:
> On 3/27/07, Chuck Ebbert <cebbert@redhat.com> wrote:
>> 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"
>>
>
> I'd recommend matching on "phys" or individual capabilities bits
> instead of device node. See "man evdev".
>
I wrote a few udev rules to create specific /dev nodes for X with evedv 
(I run with multiple X users / screens / keyboards / mice on one 
machine).  I can forward you the udev rules and helper scripts if you 
want.  This means that you can hardcode the /dev nodes in your xorg.conf 
file and udev will make sure they don't move on you.  I wrote this up in 
the early days of evdev development before the phys stuff was there.

Matt

  reply	other threads:[~2007-03-28 20:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-24  7:16 Fix sudden warps in mousedev Pete Zaitcev
2007-03-24  7:16 ` Pete Zaitcev
2007-03-25  5:34 ` Dmitry Torokhov
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
2007-03-27 16:19                     ` Dmitry Torokhov
2007-03-28 20:51                       ` Matt Keenan [this message]
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=460AD556.9090408@gmail.com \
    --to=tank.en.mate@gmail.com \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.