From owner-freebsd-current  Thu Jan  9 13:40:11 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id NAA22964
          for current-outgoing; Thu, 9 Jan 1997 13:40:11 -0800 (PST)
Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA22959
          for <current@freebsd.org>; Thu, 9 Jan 1997 13:40:08 -0800 (PST)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id OAA08361; Thu, 9 Jan 1997 14:39:44 -0700 (MST)
Date: Thu, 9 Jan 1997 14:39:44 -0700 (MST)
Message-Id: <199701092139.OAA08361@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
To: Andrew Stesin <stesin@gu.net>
Cc: current@freebsd.org
Subject: Re: Who Caught My PS/2 mouse?! + unknown PCI bridge + DD mode
In-Reply-To: <Pine.BSF.3.95.970110015228.226A-100000@trifork.gu.net>
References: <Pine.BSF.3.95.970110015228.226A-100000@trifork.gu.net>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> psm0: current command byte:0047
> psm0: status after reset 00 02 64
> psm: status 00 00 64 (get_mouse_buttons)
> psm0: status 00 02 64
> psm0 at 0x60-0x64 irq 12 on motherboard
> psm0: device ID 0, 2 buttons?
..

So far so good.
> -- ps/2 mouse is recognized Ok by the kernel (???)
>    Though I can't get moused working. Here is a duplicate
>    of messages seen while rebooting, done from a root' vty:
> 
> # moused -cdf -p /dev/psm0 -t ps/2

I don't think moused works (yet) on PS/2 mice due to blocking/unblocking

> # cat < /dev/psm0
> cat: stdin: Resource temporarily unavailable

This is expected behavior.

> No X11 yet because of no mouse, of course... what a pity.

X should work fine, it just moused that doesn't work.


Nate