Date: Wed, 18 May 2016 09:51:34 +0200 From: Hans Petter Selasky <hps@selasky.org> To: Karl Denninger <karl@denninger.net>, freebsd-usb@freebsd.org Subject: Re: Oddity with ugen Message-ID: <46bd6efe-5335-f659-0b07-5107b0e9a326@selasky.org> In-Reply-To: <b24c5a9a-cb18-c014-75ab-9b923853a70c@denninger.net> References: <b24c5a9a-cb18-c014-75ab-9b923853a70c@denninger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 05/17/16 18:53, Karl Denninger wrote: > If this is a condition of some sort in the device or driver I've not > been able to figure out what it is, or how to force it to clear -- or to > prove whether it's in the device or the ugen driver. > > Any ideas? Hi, The most easy way to know this for sure, is to check the real data traffic using usbdump: usbdump -i usbusX -f Y -s 65536 -vvv My guess is there is some data toggle issue, and that the USB stack tries to clear some error using a clear-stall command, which possibly your device does not handle properly. --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46bd6efe-5335-f659-0b07-5107b0e9a326>