From owner-freebsd-multimedia@freebsd.org  Mon Mar  6 10:35:40 2017
Return-Path: <owner-freebsd-multimedia@freebsd.org>
Delivered-To: freebsd-multimedia@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 CB7D3CFA9CF
 for <freebsd-multimedia@mailman.ysv.freebsd.org>;
 Mon,  6 Mar 2017 10:35:40 +0000 (UTC) (envelope-from hps@selasky.org)
Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::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 92E4D1E15
 for <freebsd-multimedia@freebsd.org>; Mon,  6 Mar 2017 10:35:40 +0000 (UTC)
 (envelope-from hps@selasky.org)
Received: from hps2016.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 5B71D1FE086;
 Mon,  6 Mar 2017 11:35:09 +0100 (CET)
Subject: Re: What is wrong with FreeBSD and USB Support
To: Markus Rechberger <mrechberger@gmail.com>, freebsd-multimedia@freebsd.org
References: <CA+O4pCK4+1rE5ft4Boy_3xPdCxK31UtTQ2BYpnBUn5jxZr+z_g@mail.gmail.com>
 <CA+O4pCJr5Bq-sgjzvZQB-mFRT6x7Tp3psga6f__V9Ag-=v-mhw@mail.gmail.com>
 <CA+O4pC+f5xzOjENKSJu_sQeaiN3XL3WiTcRQvm4vVweQ71Xtrg@mail.gmail.com>
 <CA+O4pC+1t67ODF7bkyVhcojXTLnFkS28RbFAc+e-tjNncogMAQ@mail.gmail.com>
 <CA+O4pCLRJRFG8Sv6C=FK6myBDPdUfhNjZ88P=e1uuH2=ojB75w@mail.gmail.com>
From: Hans Petter Selasky <hps@selasky.org>
Message-ID: <1aff0983-deb6-2884-472c-bb1e1037275c@selasky.org>
Date: Mon, 6 Mar 2017 11:34:51 +0100
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101
 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CA+O4pCLRJRFG8Sv6C=FK6myBDPdUfhNjZ88P=e1uuH2=ojB75w@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-multimedia@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Multimedia discussions <freebsd-multimedia.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-multimedia>, 
 <mailto:freebsd-multimedia-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-multimedia/>
List-Post: <mailto:freebsd-multimedia@freebsd.org>
List-Help: <mailto:freebsd-multimedia-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-multimedia>, 
 <mailto:freebsd-multimedia-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Mar 2017 10:35:40 -0000

On 03/06/17 11:00, Markus Rechberger wrote:
> even though it's going up and down DVB-T is okay due to the lower
> bandwidth so something's obviously wrong with the freebsd USB Support.

Hi,

Can you provide a usbdump trace and send it to me off-list?

usbdump -i usbusX -f Y -s65536 -w usb_capture.pcap

X and Y are number after ugenX.Y

If you are using ISOCHRONOUS high-speed transfers with an XHCI USB 
controller, the XHCI is much less forgiving about the USB PIDs of the 
multi-data payloads coming from the USB device than the EHCI. I have 
seen at least one DVB-T USB adapter which is totally broken with XHCI 
and works just fine with EHCI. This has been verified with a USB wire 
analyzer.

--HPS