From owner-freebsd-current@FreeBSD.ORG Sat Aug 28 02:58:33 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 E1A9916A4CE for ; Sat, 28 Aug 2004 02:58:33 +0000 (GMT) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id BACF543D2F for ; Sat, 28 Aug 2004 02:58:33 +0000 (GMT) (envelope-from apeiron@comcast.net) Received: from prophecy.velum (pcp08490587pcs.levtwn01.pa.comcast.net[68.83.169.224]) by comcast.net (rwcrmhc11) with SMTP id <2004082802583201300hfhu7e> (Authid: apeiron@comcast.net); Sat, 28 Aug 2004 02:58:33 +0000 Date: Fri, 27 Aug 2004 22:58:29 -0400 From: Christopher Nehren To: "M. Warner Losh" Message-ID: <20040828025829.GA51618@prophecy.dyndns.org> References: <20040820220601.G33344@midi.ihme.net> <20040826161900.GA31925@prophecy.dyndns.org> <20040827.204132.36022184.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="k1lZvvs/B4yU6o8G" Content-Disposition: inline In-Reply-To: <20040827.204132.36022184.imp@bsdimp.com> X-Please-CC-Me: In List And Group Replies User-Agent: Mutt/1.5.6i 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 02:58:34 -0000 --k1lZvvs/B4yU6o8G Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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 jo= ypad=20 broke *after* I updated from 5.2-CURRENT of ~ August 15 to 6.0-CURRENT of ~= =20 August 19. Logically, if it had been busted by the uhid upgrade in March, t= hen=20 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. --=20 I abhor a system designed for the "user", if that word is a coded pejorative meaning "stupid and unsophisticated". -- Ken Thompson - Unix is user friendly. However, it isn't idiot friendly. --k1lZvvs/B4yU6o8G Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (FreeBSD) iD8DBQFBL/TVk/lo7zvzJioRAlpLAJ0Y8Wx5RYc3CpXb/UwiyCeHebS4XgCfYByA xCMh/rqCj+pGtfZw45FdQ54= =yKX7 -----END PGP SIGNATURE----- --k1lZvvs/B4yU6o8G--