From owner-freebsd-hardware Sun Jan 7 01:10:14 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA28499 for hardware-outgoing; Sun, 7 Jan 1996 01:10:14 -0800 (PST) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA28487 for ; Sun, 7 Jan 1996 01:10:08 -0800 (PST) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id KAA06734; Sun, 7 Jan 1996 10:08:03 +0100 Message-Id: <199601070908.KAA06734@ra.dkuug.dk> Subject: Re: PS/2 AUX mouse problems with 2.1 To: brett@selgus.com (Brett Bourbin) Date: Sun, 7 Jan 1996 10:08:03 +0100 (MET) Cc: freebsd-hardware@FreeBSD.org In-Reply-To: <30EF5A63.20E@selgus.com> from "Brett Bourbin" at Jan 6, 96 09:30:11 pm From: sos@FreeBSD.org Reply-to: sos@FreeBSD.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hardware@FreeBSD.org Precedence: bulk In reply to Brett Bourbin who wrote: > > Are there any other issues with the 2.1 psm PS/2 AUX mouse driver, than > those listed in the FAQ? > > I have added a psm0 line (exactly the way it was in the LINT config) > along with the PSM_NO_RESET option and made the device, but the kernel > still does not think the mouse is there. > > It is, since I am writing this mail from the same box under Win95. > > I have looked at psm.c and inserted some debugging printf's and the > probe read (the inb() call) is returning 0x55. The check it seems to > be doing is if bit 2 is set, the mouse is not there. Is this correct? > It also assumes that it is at port 0x60, and IRQ 12. I know the > interrupt is correct, and I assume the port it right. Hmm I use it here, and it works fine for me, my config is something like: device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr that works on a ASUS p55tp4xeg motherboard with an IBM mouse.. There is work underways in this area as the way its done now is not optimal -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time.