Date: Mon, 17 Apr 2006 13:06:56 +0100 (BST) From: Iain Hibbert <plunky@rya-online.net> To: Maksim Yevmenkin <maksim.yevmenkin@savvis.net> Cc: freebsd-bluetooth@freebsd.org Subject: USB isoc xfers Message-ID: <1145275616.851775.858.nullmailer@galant.ukfsn.org> In-Reply-To: <44248823.3040907@savvis.net> References: <4423D096.2010205@udc.es> <44248823.3040907@savvis.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1145275616.851775.858.nullmailer>