Date: Sat, 11 Aug 2001 22:10:42 -0700 From: Joe Kelsey <joe@zircon.seattle.wa.us> To: current@FreeBSD.ORG Subject: Re: FreeBSD's aggressive keyboard probe/attach Message-ID: <15222.4050.319209.150062@zircon.zircon.seattle.wa.us> In-Reply-To: <200108120422.f7C4MY150223@harmony.village.org> References: <200108112351.AAA26897@banks.cogsci.ed.ac.uk> <200108120422.f7C4MY150223@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Warner Losh writes: > : > In addition, the PS/2 mouse driver is smart enough to bitch > : > about synchronization, but too stupid to resynchronize (reset) > : > when it happens. Duh. > > Ummm, what does adding flags 0x8000 buy you? I think that fixed it > for me on the machines that I was seeing it. > > Except for the machines I'd see it after suspend/resume, then flags > 0x4000 worked. Adding flags is not the point. The point is that no other operating system requires any special treatment in order for any mouse to work. The default behavior should work all of the time, no exceptions, no flags. The code is completely opaque and not easily accessible to someone who did not write it. The documentation is vague and confusing. What is so hard about making it work in all situations. Why does my mouse work all of the time on Solaris, whether or not I use a KVM, but sometines on FreeBSD I have to set the 0x100 flags and on the next reboot I have to reset the 0x100 flags? It does not make any sense. Why should I have to attempt to fix a driver with no documentation on the code and no documentation on the hardware? Mike seems to think that I should be able to follow a poorly documented piece of code with no documentation on what the hardware sepcifications are and no documentation on the design decisions embodied in the code are. It is definitely not reasonable to believe that you can document code designs in CVS notes. Design documentation belongs is a single coherent document, preferably attached to the code, either as a literate program or as some sort of commentary. /Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15222.4050.319209.150062>