Date: Wed, 18 May 2016 17:46:03 +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: <b04006da-8b3b-7daa-e8d0-0cea8d1583ed@selasky.org> In-Reply-To: <af57a994-2e7a-c0d0-1d84-a333c2b2096b@denninger.net> References: <b24c5a9a-cb18-c014-75ab-9b923853a70c@denninger.net> <46bd6efe-5335-f659-0b07-5107b0e9a326@selasky.org> <af57a994-2e7a-c0d0-1d84-a333c2b2096b@denninger.net>
index | next in thread | previous in thread | raw e-mail
On 05/18/16 17:32, Karl Denninger wrote: > If I'm reading this correctly usbdump is showing me exactly what the > device is sending; that is, there is no "driver" involved here (just bus > traffic) -- correct? Hi, usbdump is showing exactly what the USB controller driver is sending and receiving. It is similar to a USB wire trace. > > If so that looks like a device bug (and a nasty one that I may have all > sorts of fun trying to work around.) Yes, most likely a bug on the device side. I assume you are running this software on a regular computer with EHCI/XHCI/OHCI/UHCI ? --HPShelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b04006da-8b3b-7daa-e8d0-0cea8d1583ed>