From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932652AbXC0QEx (ORCPT ); Tue, 27 Mar 2007 12:04:53 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932837AbXC0QEx (ORCPT ); Tue, 27 Mar 2007 12:04:53 -0400 Received: from mx1.redhat.com ([66.187.233.31]:51515 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932652AbXC0QEw (ORCPT ); Tue, 27 Mar 2007 12:04:52 -0400 Message-ID: <4609409F.2070203@redhat.com> Date: Tue, 27 Mar 2007 12:04:47 -0400 From: Chuck Ebbert Organization: Red Hat User-Agent: Thunderbird 1.5.0.10 (X11/20070302) MIME-Version: 1.0 To: Dmitry Torokhov CC: Pete Zaitcev , linux-kernel@vger.kernel.org, linux-input@atrey.karlin.mff.cuni.cz, Peter Osterlund Subject: Re: Fix sudden warps in mousedev References: <20070324001610.724a820a.zaitcev@redhat.com> <20070326144206.93805eeb.zaitcev@redhat.com> <200703262114.45287.dtor@insightbb.com> <460934D7.9030700@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org 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"