From owner-freebsd-stable Thu Aug 17 8:59:40 2000 Delivered-To: freebsd-stable@freebsd.org Received: from citadel.cequrux.com (citadel.cequrux.com [192.96.22.18]) by hub.freebsd.org (Postfix) with ESMTP id A478837B6E6 for ; Thu, 17 Aug 2000 08:59:32 -0700 (PDT) Received: (from nobody@localhost) by citadel.cequrux.com (8.8.8/8.6.9) id RAA04437; Thu, 17 Aug 2000 17:59:17 +0200 (SAST) Received: by citadel.cequrux.com via recvmail id 4352; Thu Aug 17 17:58:25 2000 Message-ID: <399C0C26.EEA0EE8F@cequrux.com> Date: Thu, 17 Aug 2000 18:00:38 +0200 From: Graham Wheeler Organization: Cequrux Technologies X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 2.2.8-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Sean O'Connell" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ps2 mouse errors References: <20000817001624.A22518@jupiter.limit.org> <14748.115.748006.95674@onceler.kciLink.com> <20000817114143.H71098@stat.Duke.EDU> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sean O'Connell wrote: > > I think there are some subtle timing issues in syscons code or in moused > that are really ugly and have been around since just after 4.0-RELEASE It isn't a problem with moused, it is a problem with the psm driver, or possibly (but less likely) the kbd driver. People experience it in syscons consoles with moused, as well as under X without moused. It will be great when its finally solved, but it's a real nasty one to solve. Personally I suspect it is due to nested or lost interrupts; unfortunately the PS/2 mouse doesn't have a proper framing protocol which makes synchronisation difficult if any data is ever lost. gram -- Dr Graham Wheeler E-mail: gram@cequrux.com Director, Research and Development WWW: http://www.cequrux.com CEQURUX Technologies Phone: +27(21)423-6065 Firewalls/VPN Specialists Fax: +27(21)424-3656 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message