Date: Fri, 13 Jan 2012 10:18:45 -0500 From: John Baldwin <jhb@freebsd.org> To: Justin Smith <freebsd.users@gmail.com> Cc: freebsd-gnats-submit@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: amd64/164036: Moused fails on 9_0_RELENG Message-ID: <201201131018.45939.jhb@freebsd.org> In-Reply-To: <CAOhdvrU-eB1L8JuQ3bGZeeqeAuAggi1RFxdDd06j5KA8iMF_8A@mail.gmail.com> References: <201201120439.q0C4dOJ1025920@red.freebsd.org> <201201130808.03827.jhb@freebsd.org> <CAOhdvrU-eB1L8JuQ3bGZeeqeAuAggi1RFxdDd06j5KA8iMF_8A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201201131018.45939.jhb>