From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932883AbXC0QTN (ORCPT ); Tue, 27 Mar 2007 12:19:13 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S933010AbXC0QTN (ORCPT ); Tue, 27 Mar 2007 12:19:13 -0400 Received: from wr-out-0506.google.com ([64.233.184.226]:50304 "EHLO wr-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932883AbXC0QTL (ORCPT ); Tue, 27 Mar 2007 12:19:11 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=qbDbmgsPdfLlPbneAkg5UALS/YbmQHhzI/y8GettiXY14shs4AoYYO+mpHCyd1Ynt6fLxAj6C6v74XlH2lX7KIHhXEHHY0LjaHwxkUJRU0nIcAWp7RKocfx9QQIj66lS6EEaeUYDs+PJa8ycgPLmZAP279SXDu88ua7xxCddjPs= Message-ID: Date: Tue, 27 Mar 2007 12:19:10 -0400 From: "Dmitry Torokhov" To: "Chuck Ebbert" Subject: Re: Fix sudden warps in mousedev Cc: "Pete Zaitcev" , linux-kernel@vger.kernel.org, linux-input@atrey.karlin.mff.cuni.cz, "Peter Osterlund" In-Reply-To: <4609409F.2070203@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070324001610.724a820a.zaitcev@redhat.com> <20070326144206.93805eeb.zaitcev@redhat.com> <200703262114.45287.dtor@insightbb.com> <460934D7.9030700@redhat.com> <4609409F.2070203@redhat.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@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