From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Dmitry Torokhov" Subject: Re: Fix sudden warps in mousedev Date: Tue, 27 Mar 2007 12:19:10 -0400 Message-ID: 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: <4609409F.2070203@redhat.com> Content-Disposition: inline Sender: owner-linux-input@atrey.karlin.mff.cuni.cz List-Help: List-Owner: List-Post: List-Unsubscribe: To: Chuck Ebbert Cc: Pete Zaitcev , linux-kernel@vger.kernel.org, linux-input@atrey.karlin.mff.cuni.cz, Peter Osterlund List-Id: linux-input@vger.kernel.org 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". -- Dmitry