From owner-freebsd-usb@FreeBSD.ORG Fri Jan 14 02:32:34 2005 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 4ECC016A4CE for ; Fri, 14 Jan 2005 02:32:34 +0000 (GMT) Received: from szamoca.krvarr.bc.ca (s142-179-111-232.bc.hsia.telus.net [142.179.111.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id 093FE43D55 for ; Fri, 14 Jan 2005 02:32:34 +0000 (GMT) (envelope-from sandy@krvarr.bc.ca) Received: from szamoca.krvarr.bc.ca (localhost [127.0.0.1]) by szamoca.krvarr.bc.ca (8.13.1/8.12.11) with ESMTP id j0E2WJGO046705; Thu, 13 Jan 2005 18:32:19 -0800 (PST) (envelope-from sandy@szamoca.krvarr.bc.ca) Received: (from sandy@localhost) by szamoca.krvarr.bc.ca (8.13.1/8.12.11/Submit) id j0E2WIup046702; Thu, 13 Jan 2005 18:32:18 -0800 (PST) (envelope-from sandy) From: Sandy Rutherford MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16871.12082.427060.456051@szamoca.krvarr.bc.ca> Date: Thu, 13 Jan 2005 18:32:18 -0800 To: freebsd-usb@freebsd.org X-Mailer: VM 7.07 under Emacs 21.3.1 cc: julian@elischer.org Subject: Re: ulpt hangs on offline status 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, 14 Jan 2005 02:32:34 -0000 Julian Elischer wrote: Sandy Rutherford wrote: >This is with FreeBSD 4.10 / i386. > >1. Has anybody else seen this behaviour? > >2. Is it a driver bug or a problem with the Entrega adapter? The > specs of my adapter and USB controller are below. > >3. Does anybody know of a patch to ultp.c to fix this problem? > >4. Any ideas for a (software) workaround, such as a way to force a soft > detach/attach? > You might close and reopen the device. Can that be done from userland? >I am willing to muck around with the driver to try to fix this myself, >but it would be useful to know if anybody else has seen or worked on >this problem. > not yet but I'm willing to believe that you may need to poll the device to see the change in status. That would be handled in the "interrupt" type transfers.. We do not support them very well yet. That was my guess as well. Thanks, Sandy