*BSD News Article 15071


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!munnari.oz.au!hp9000.csc.cuhk.hk!saimiri.primate.wisc.edu!ames!pacbell.com!iggy.GW.Vitalink.COM!psinntp!psinntp!sbcs.sunysb.edu!stark.UUCP!gene
From: gene@cs.sunysb.edu!stark (Gene Stark)
Newsgroups: comp.os.386bsd.questions
Subject: Re: [NetBSD] Bus Mouse driver?
Date: 25 Apr 93 06:39:41
Organization: Gene Stark's home system
Lines: 32
Message-ID: <GENE.93Apr25063941@stark.uucp>
References: <1993Apr24.232122.18272@cs.cornell.edu>
NNTP-Posting-Host: stark.uucp
In-reply-to: cchase@cs.cornell.edu's message of Sat, 24 Apr 1993 23:21:22 GMT

In article <1993Apr24.232122.18272@cs.cornell.edu> cchase@cs.cornell.edu (Craig Chase) writes:

>   So, what all may have changed since the good old days of 386BSD patchkit 1
>   and NetBSD that would break Rick Macklem's bus mouse driver?
>
>   First, you need a new major device number, since 14 is being used.
>   I stuck it at 26 (until somebody tells me something else).

Yes, there is a need for a bus mouse major device number.  I have mine
at 21 (codrv), since I am using syscons.

>   Then, selwakeup seems to be expecting a pid_t instead of a struct proc*
>   so you need to edit all occurences of sc_selp to change that to the pid.

Yes, that is what I did, back around patchkit 0.2, I think. 

>   OK, that makes things *almost* work in XFree86.  But there's still
>   some confusion with the TTY drivers.  Specifically, tty input is
>   not delivered to the windows until a mouse event occurs.

I am running 386bsd 0.1 + patchkit 0.2.2, and I do not have this problem
with Macklem's driver (edited) and XFree86.

>   Could someone point me in the right direction to fix this problem?

I will send you (in private E-mail) the version I am using.  Don't be mad
that I am still using my version of the original InPort patches from back
in October rather than yours :-)

							- Gene Stark
--
							stark@cs.sunysb.edu