From owner-freebsd-current@FreeBSD.ORG Sat Feb 27 14:20:29 2010 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0A577106566B for ; Sat, 27 Feb 2010 14:20:29 +0000 (UTC) (envelope-from freebsd-current@chrishedley.com) Received: from smtp5.enta.net (smtp5.enta.net [78.33.48.15]) by mx1.freebsd.org (Postfix) with ESMTP id BD2AB8FC08 for ; Sat, 27 Feb 2010 14:20:28 +0000 (UTC) Received: from mail.chrishedley.com (unknown [78.32.138.135]) by smtp5.enta.net (Postfix) with ESMTP id 4824D146B568 for ; Sat, 27 Feb 2010 14:20:27 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.chrishedley.com (Postfix) with ESMTP id D813C2994 for ; Sat, 27 Feb 2010 14:20:26 +0000 (GMT) X-Virus-Scanned: amavisd-new at chrishedley.com Received: from mail.chrishedley.com ([127.0.0.1]) by localhost (mail.chrishedley.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id QYHFLMl2UsNL for ; Sat, 27 Feb 2010 14:20:21 +0000 (GMT) Received: from teapot.cbhnet (teapot.cbhnet [192.168.1.1]) by mail.chrishedley.com (Postfix) with ESMTP id 7ACF52971 for ; Sat, 27 Feb 2010 14:20:21 +0000 (GMT) Date: Sat, 27 Feb 2010 14:20:21 +0000 (GMT) From: Chris Hedley X-X-Sender: cbh@teapot.cbhnet To: freebsd-current@FreeBSD.org In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Subject: Re: ums fails to initialise correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Feb 2010 14:20:29 -0000 On Mon, 22 Feb 2010, Chris Hedley wrote: > I'm having a lot of problems getting the ums (USB mouse) driver to initialise > the mouse correctly. I've been wading through the kernel source trying to see if I can find anything, but nothing's grabbed me yet. What I'm looking for is something that would explain: a) why does the keyboard not have the same problem when using the same KVM switch when it's also a high-speed device? There are differences in the ums and ukbd modules (obviously) but I lack the experience to see which ones may be relevant. and b) why does the mouse initialise correctly when physically disconnected and reconnected, but not when simply switching back and forth with the KVM or using the usbconfig power_on/power_off/reset command? I'm assuming that the physical reconnection calls some additional piece of code that isn't called by a logical reconnection, though I've little enough idea of where to even start looking let alone how to fiddle about with it. Anybody experienced with this area of code have any pointers for me? Thanks!