From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 13 15:30:14 2012 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 342AD1065670 for ; Fri, 13 Jan 2012 15:30:14 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1FD528FC22 for ; Fri, 13 Jan 2012 15:30:14 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q0DFUDMx010673 for ; Fri, 13 Jan 2012 15:30:14 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0DFUD8S010670; Fri, 13 Jan 2012 15:30:13 GMT (envelope-from gnats) Date: Fri, 13 Jan 2012 15:30:13 GMT Message-Id: <201201131530.q0DFUD8S010670@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: John Baldwin Cc: Subject: Re: amd64/164036: Moused fails on 9_0_RELENG X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John Baldwin List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2012 15:30:14 -0000 The following reply was made to PR amd64/164036; it has been noted by GNATS. From: John Baldwin To: Justin Smith Cc: freebsd-amd64@freebsd.org, freebsd-gnats-submit@freebsd.org Subject: Re: amd64/164036: Moused fails on 9_0_RELENG Date: Fri, 13 Jan 2012 10:18:45 -0500 On Friday, January 13, 2012 9:20:53 am Justin Smith wrote: > Yeah, its strange for sure. But I have this issue on two different > systems with different hardware (ASUS board & BIOSTAR Board). > > devinfo -vr : http://paste.pocoo.org/show/534240/ Hmm. So the "problem" is your BIOS putting the keyboard resources on the PS/2 port. You can fix this by editing your AML and moving the IO Port resources out of _CRS for the PS2M device and moving them to the PS2K device instead. However, fixing it automatically would be a bigger pain as we would need to patch both the atkbdc and psmcpnp drivers to cooperate to move the I/O ports over. We already have a similar hack for handling IRQ 12. We should perhaps expand that further so that we have atkbdc somehow attach to both PS/2 devices and merge any resources into a single logical device. -- John Baldwin