From owner-freebsd-usb@FreeBSD.ORG Fri Dec 3 21:46:24 2004 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E5BE16A4CE for ; Fri, 3 Dec 2004 21:46:24 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id A755B43D55 for ; Fri, 3 Dec 2004 21:46:23 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iB3LhNAr008297; Fri, 3 Dec 2004 14:43:23 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Fri, 03 Dec 2004 14:44:32 -0700 (MST) Message-Id: <20041203.144432.89673091.imp@bsdimp.com> To: julian@elischer.org From: "M. Warner Losh" In-Reply-To: <41B0DD18.9080300@elischer.org> References: <41B0C118.8070001@elischer.org> <20041203.133422.67680751.imp@bsdimp.com> <41B0DD18.9080300@elischer.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-usb@FreeBSD.ORG Subject: Re: Question about pipes and ugen X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 21:46:24 -0000 In message: <41B0DD18.9080300@elischer.org> Julian Elischer writes: : : : M. Warner Losh wrote: : : >In message: <41B0C118.8070001@elischer.org> : > Julian Elischer writes: : >: I didn't say stack.. I said libusb (excepty I spelled it usblib) : > : >OK. I got confused... : > : >: it recovers on several machines where FreeBSD looses communications with : >: the target after an error. : > : >Hmmmm. Actually, FreeBSD does do the ClearFeature(Halt) on opening of : >pipes by the driver (which ugen does each time the pipe subdevice is : >opened). ClearFeature(Stall) was unfortunately typed from memory : >rather than looking at the standard (section 9.4.5). What were you : >thinking about changing in this area? : > : : BTW it does the halt too late.. by that time it has already tried to do : other opertations that : have probably timed out (at least on the stupid device I have) so it's : aborted before it ever gets : to the ClearFeature(Halt). It does this as soon as the driver opens the pipe. Nothing can have happened on the pipe before that. I don't understand what you are saying here. It might also do it other times, but it definitely does it on open... Warner