From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Keenan Subject: Re: Fix sudden warps in mousedev Date: Wed, 28 Mar 2007 21:51:34 +0100 Message-ID: <460AD556.9090408@gmail.com> References: <20070324001610.724a820a.zaitcev@redhat.com> <20070326144206.93805eeb.zaitcev@redhat.com> <200703262114.45287.dtor@insightbb.com> <460934D7.9030700@redhat.com> <4609409F.2070203@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: owner-linux-input@atrey.karlin.mff.cuni.cz List-Help: List-Owner: List-Post: List-Unsubscribe: To: Dmitry Torokhov Cc: Chuck Ebbert , Pete Zaitcev , linux-kernel@vger.kernel.org, linux-input@atrey.karlin.mff.cuni.cz, Peter Osterlund List-Id: linux-input@vger.kernel.org Dmitry Torokhov wrote: > On 3/27/07, Chuck Ebbert 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