From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 13 16:55:30 2012 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 74D33106564A; Fri, 13 Jan 2012 16:55:30 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 4685D8FC0A; Fri, 13 Jan 2012 16:55:30 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) by cyrus.watson.org (Postfix) with ESMTPSA id DBEA846B3F; Fri, 13 Jan 2012 11:55:29 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 6AC0FB922; Fri, 13 Jan 2012 11:55:29 -0500 (EST) From: John Baldwin To: Justin Smith Date: Fri, 13 Jan 2012 11:54:36 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p10; KDE/4.5.5; amd64; ; ) References: <201201120439.q0C4dOJ1025920@red.freebsd.org> <201201131018.45939.jhb@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201201131154.36090.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 13 Jan 2012 11:55:29 -0500 (EST) Cc: freebsd-gnats-submit@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: amd64/164036: Moused fails on 9_0_RELENG X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list 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 16:55:30 -0000 On Friday, January 13, 2012 11:17:35 am Justin Smith wrote: > On Fri, Jan 13, 2012 at 11:18 PM, John Baldwin wrote: > > 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 > > Been there done that (ASUS board AML), doesn't work. I have no > settings for PS2M to PS2K on BIOSTAR BIOS. Err, not a BIOS setting, but actually editing the AML. Assuming you edited the ASUS AML, can you show me a diff of the original and modified AML? -- John Baldwin