From owner-freebsd-current@FreeBSD.ORG Sat Aug 28 03:31:24 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5451916A4CE for ; Sat, 28 Aug 2004 03:31:24 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id D85F143D1D for ; Sat, 28 Aug 2004 03:31:23 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.11/8.12.11) with ESMTP id i7S3TCIJ021054; Fri, 27 Aug 2004 21:29:12 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Fri, 27 Aug 2004 21:29:12 -0600 (MDT) Message-Id: <20040827.212912.43023076.imp@bsdimp.com> To: apeiron@comcast.net From: "M. Warner Losh" In-Reply-To: <20040828025829.GA51618@prophecy.dyndns.org> References: <20040826161900.GA31925@prophecy.dyndns.org> <20040827.204132.36022184.imp@bsdimp.com> <20040828025829.GA51618@prophecy.dyndns.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: midian@ihme.org Subject: Re: USB keyboard problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Aug 2004 03:31:24 -0000 In message: <20040828025829.GA51618@prophecy.dyndns.org> Christopher Nehren writes: : On Fri, Aug 27, 2004 at 22:41:32 EDT, M. Warner Losh scribbled these : curious markings: : > I guess it all depends on what you mean by recently. I'd thought that : > some of my recent changes had broken it, but the breakage goes back : > further than that. 5.2 release isn't 'recent', and I fully believe : > that things may have changed since then... I see a major uhid upgrade : > in that time frame, which may be the time of breakage... : : I understand your point, but that doesn't sit well with the fact that my joypad : broke *after* I updated from 5.2-CURRENT of ~ August 15 to 6.0-CURRENT of ~ : August 19. Logically, if it had been busted by the uhid upgrade in March, then : it could not possibly have worked with 5.2-CURRENT (which it did, just : as well as it did with 5.2.1-RELEASE[1]), correct? : : [1] Better, in fact, as the device wasn't detected at boot time in 5.2.1 : but was in 5.2-CURRENT. Then I'm very confused... Time to dig deeper... Warner