From owner-freebsd-current Mon Aug 13 2:27: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.121.85]) by hub.freebsd.org (Postfix) with ESMTP id 1B1D037B401 for ; Mon, 13 Aug 2001 02:27:02 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.143.29.Dial1.SanJose1.Level3.net [209.245.143.29]) by gull.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id CAA08705; Mon, 13 Aug 2001 02:26:52 -0700 (PDT) Message-ID: <3B779D85.F292A2F@mindspring.com> Date: Mon, 13 Aug 2001 02:27:33 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: Joe Kelsey , current@FreeBSD.ORG Subject: Re: FreeBSD's aggressive keyboard probe/attach References: <15222.50892.75406.972475@zircon.zircon.seattle.wa.us> <200108120813.RAA26578@zodiac.mech.utsunomiya-u.ac.jp> <200108130044.f7D0igW03766@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Warner Losh wrote: > > In message <15222.50892.75406.972475@zircon.zircon.seattle.wa.us> Joe Kelsey writes: > : I also second Terry's comment about 0x800. There is no reason to add > : yet more driver flags in order to "do the right thing". The "do the > : right thing" case should always be default and a flag (sysctl variable, > : etc) should be used for those who want "the wrong thing". > > The main reason that it wasn't added at the time was that it was > expensive in terms of CPU utilization, so it shouldn't be on by > default. There may be other reasons as well... ??? It was just recently added; I'd like to see it MFC'ed for 4.4, but certainly, Kazu hasn't been slacking on 0x8000. I personally don't see how it could be more costly in terms of CPU, since it only invokes in the case of a desynchronized mouse event coming in to the mouse driver: e.g. a failure case that only triggers when there's bot a failure, and a monkey on the other end of the mouse cable. 8-). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message