From owner-freebsd-bluetooth@FreeBSD.ORG Mon Apr 17 12:19:13 2006 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BD91316A402 for ; Mon, 17 Apr 2006 12:19:13 +0000 (UTC) (envelope-from plunky@rya-online.net) Received: from mail05.svc.cra.dublin.eircom.net (mail05.svc.cra.dublin.eircom.net [159.134.118.21]) by mx1.FreeBSD.org (Postfix) with SMTP id 3758443D45 for ; Mon, 17 Apr 2006 12:19:12 +0000 (GMT) (envelope-from plunky@rya-online.net) Received: (qmail 64981 messnum 3334258 invoked from network[83.70.176.191/unknown]); 17 Apr 2006 12:08:51 -0000 Received: from unknown (HELO rya-online.net) (83.70.176.191) by mail05.svc.cra.dublin.eircom.net (qp 64981) with SMTP; 17 Apr 2006 12:08:51 -0000 Received: (nullmailer pid 164 invoked by uid 1000); Mon, 17 Apr 2006 12:06:56 -0000 Date: Mon, 17 Apr 2006 13:06:56 +0100 (BST) To: Maksim Yevmenkin In-Reply-To: <44248823.3040907@savvis.net> References: <4423D096.2010205@udc.es> <44248823.3040907@savvis.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Message-Id: <1145275616.851775.858.nullmailer@galant.ukfsn.org> From: Iain Hibbert Cc: freebsd-bluetooth@freebsd.org Subject: USB isoc xfers X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Apr 2006 12:19:13 -0000 Hi Maksim, I am having a little trouble with the USB isoc data, and I see you also had the same trouble.. | 3) Understand and fix isoc. USB transfers (SCO data) | | Currenty device reports that is got zero bytes and calls | isoc_in_complete callback over and over again. Why? | Also might need to setup at least two isoc. transfers in | both directions and switch them on the fly. Just to ensure | there at least one transfer at any time ready to run. if you solved this already, any tips? So far I am supposing that for USB isoc transfers, the transfer would be fulfilled in any case after a timeout (3ms ?) which is why I get zero bytes, and I would be happy with that but it seems that the uhci/usbdi part gets lost in a loop when I restart the xfer (possibly caused by some DIAGNOSTIC logic) To have isoc xfers consuming processor cycles continuously when no data is being sent does not seem like a great idea though, maybe I got the wrong impression there.. regards, iain