From owner-freebsd-mobile@FreeBSD.ORG Mon May 5 19:10:07 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ECFDA37B404 for ; Mon, 5 May 2003 19:10:07 -0700 (PDT) Received: from parmenides.zen.co.uk (parmenides.zen.co.uk [212.23.8.69]) by mx1.FreeBSD.org (Postfix) with SMTP id 331FD43FA3 for ; Mon, 5 May 2003 19:10:06 -0700 (PDT) (envelope-from tony@ubik.demon.co.uk) Received: (qmail 12591 invoked from network); 6 May 2003 02:10:05 -0000 Received: from protagoras.zen.co.uk (212.23.8.61) by parmenides.zen.co.uk with QMQP; 6 May 2003 02:10:05 -0000 Received: from dsl-217-155-183-134.zen.co.uk (HELO ubik.demon.co.uk) (217.155.183.134) by protagoras.zen.co.uk with SMTP; 6 May 2003 02:10:04 -0000 X-Zen-Trace: 217.155.183.134 Message-ID: Date: Tue, 6 May 2003 02:09:09 +0000 To: Maksim Yevmenkin From: Anthony Naggs References: <3EB69929.1070900@cw.com> <20030505171500.74191.qmail@web40305.mail.yahoo.com> In-Reply-To: <20030505171500.74191.qmail@web40305.mail.yahoo.com> MIME-Version: 1.0 X-Mailer: Turnpike Integrated Version 5.01 U cc: Doug Barton cc: mobile@freebsd.org cc: Tobias Roth Subject: Re: uhub2: device problem (was: Bluetooth stack for FreeBSD) X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 May 2003 02:10:08 -0000 In article <20030505171500.74191.qmail@web40305.mail.yahoo.com>, Maksim Yevmenkin writes >Hello, > >> > So that's why my mouse quit working! Yes, I think this should be fixed >> > prior to 5.1 as well. >> >> Definitely :-) >> >> So, do you take care of this or should we/I who had to do with this >> problem lately do so? >> >> I know some people collected a lot of debug output and took it to the >> current ml, but without much luck or response from the usb specialists >> (please correct me if I am wrong here and missed anything). I am a bit >> at a loss concerning how to proceed. > >well, after looking more into the w2k dumps i put at > >http://www.geocities.com/m_evmenkin/usb/ > >i found out that w2k resets USB port twice when new device is attached. >why? is it just w2k thing or it is some kind of workaround? any USB guru >care to comment? This is how the Windows (all flavours) USB stack works: detects device arrival, signal reset on port, start reading device descriptors to find out device Class Id, Vendor & Model Id, etc... Each candidate driver found by the Plug'n'Play system is loaded: the driver signals another bus reset on the port, reads the device descriptors itself and decides whether it recognises the device. This continues until a driver recognises the device as one it supports, or all candidates drivers have been tried. The drivers are tried in the order: more specific to least specific. So a driver listed in the Registry for Vendor Id & Model Id pair is tried before one Registered for the USB device Class. (Sorry if that is a bit too vague, the exact details are in the Windows DDK.) >i will try to play with uhun(4) code as soon as i get my -current more >stable :) I would love to dig around the USB stack. I haven't yet found time to get Current running & do so. :-( Tony