Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 06 Jan 1999 11:10:56 +0900
From:      Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
To:        Terry Lambert <tlambert@primenet.com>
Cc:        yokota@zodiac.mech.utsunomiya-u.ac.jp, hackers@FreeBSD.ORG
Subject:   Re: psm0 on laptops. 
Message-ID:  <199901060210.LAA26565@zodiac.mech.utsunomiya-u.ac.jp>
In-Reply-To: Your message of "Tue, 05 Jan 1999 18:58:43 GMT." <199901051858.LAA10934@usr02.primenet.com> 
References:  <199901051858.LAA10934@usr02.primenet.com> 

next in thread | previous in thread | raw e-mail | index | archive | help

>> I don't know how the W*ndows PS/2 mouse driver can detect that a new
>> mouse has suddenly appeared at the PS/2 mouse port and switch to a
>> different protocol.  You see, both the internal PS/2 mouse/pointing
>> device and the external device are wired to the same PS/2 mouse
>> port...
>
>If you have access to the Micorsoft DDK (Device Driver Kit), it
>contains the Microsoft mouse driver source code.  Including the
>code that is used to probe serial ports for mice without mucking
>up modems.

We are talking about *PS/2 mice*, not serial mice.

What you are referring to is probably the PnP COM device standard,
which `moused' already supports.

Kazu

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199901060210.LAA26565>