From owner-freebsd-x11@FreeBSD.ORG Mon Mar 31 16:25:19 2008 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 801AF106566C; Mon, 31 Mar 2008 16:25:18 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: Joe Marcus Clarke Date: Mon, 31 Mar 2008 12:25:01 -0400 User-Agent: KMail/1.6.2 References: <200803281513.16819.jkim@FreeBSD.org> <1206980068.22600.4.camel@shumai.marcuscom.com> In-Reply-To: <1206980068.22600.4.camel@shumai.marcuscom.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200803311225.02955.jkim@FreeBSD.org> Cc: freebsd-x11@freebsd.org Subject: Re: [PATCH] xorg-server: fix mouse probing X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Mar 2008 16:25:19 -0000 On Monday 31 March 2008 12:14 pm, Joe Marcus Clarke wrote: > On Fri, 2008-03-28 at 15:13 -0400, Jung-uk Kim wrote: > > As you may have noticed from other threads, xorg-server has > > problem with HAL support (default). Please test the patch: > > > > http://people.freebsd.org/~jkim/xorg-server.diff > > > > You also have to patch sysutils/hal: > > > > http://www.marcuscom.com/downloads/hal.diff > > > > Changes: > > - Do not probe /dev/psm0 as SysMouse if HAL is enabled. > > - Add /dev/ums0 as SysMouse if HAL is disabled. > > - Do not force sysmouse(4) mode unless device is /dev/sysmouse. > > When moused(8) is not running, current mode level is untouched. - > > Correcly check if moused is actually running. Checking pid file > > is not enough because it may be /var/run/moused..pid when > > it is invoked by devd(8) for USB mice. > > - Do not attach device if it is opened by moused. > > - Correctly add device path for HAL. > > If you're waiting for some success reports, all is well on my two > previously affected systems with these patches. Actually I was waiting for regression test reports for non-affected systems as I have tested on two affected systems. Can anyone confirm? Thanks, Jung-uk Kim