From owner-freebsd-usb@freebsd.org Wed May 18 15:42:45 2016 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 43104B41E86 for ; Wed, 18 May 2016 15:42:45 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1039A18A2 for ; Wed, 18 May 2016 15:42:45 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (unknown [62.141.129.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 0CB2C1FE024; Wed, 18 May 2016 17:42:42 +0200 (CEST) Subject: Re: Oddity with ugen To: Karl Denninger , freebsd-usb@freebsd.org References: <46bd6efe-5335-f659-0b07-5107b0e9a326@selasky.org> From: Hans Petter Selasky Message-ID: Date: Wed, 18 May 2016 17:46:03 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 May 2016 15:42:45 -0000 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 ? --HPS