From owner-freebsd-multimedia@freebsd.org  Mon Mar  6 10:42:32 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 8EDE9CFAD5F
 for <freebsd-multimedia@mailman.ysv.freebsd.org>;
 Mon,  6 Mar 2017 10:42:32 +0000 (UTC) (envelope-from hps@selasky.org)
Received: from mail.turbocat.net (turbocat.net [88.99.82.50])
 (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 5390A12FF
 for <freebsd-multimedia@freebsd.org>; Mon,  6 Mar 2017 10:42:31 +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 E058D1FE086;
 Mon,  6 Mar 2017 11:41:59 +0100 (CET)
Subject: Re: What is wrong with FreeBSD and USB Support
To: Markus Rechberger <mrechberger@gmail.com>
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>
 <17db8b5b-9983-2ead-5c1d-960022afb1f6@selasky.org>
 <CA+O4pCLqORoQFT3cpfzLvor1HyQcP0Pr1CQq7QJM_9r=rTspdg@mail.gmail.com>
Cc: freebsd-multimedia@freebsd.org
From: Hans Petter Selasky <hps@selasky.org>
Message-ID: <9f51e1b1-d5df-afd3-f289-3bc55e417b5a@selasky.org>
Date: Mon, 6 Mar 2017 11:41:42 +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+O4pCLqORoQFT3cpfzLvor1HyQcP0Pr1CQq7QJM_9r=rTspdg@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:42:32 -0000

On 03/06/17 11:37, Markus Rechberger wrote:
> Are you sure? As from some of my signal analyzer dumps I do think that
> all those systems support
> multiple transfers within one completion event. I always request
> multiple frames within one request on those systems and they complete
> at once. And they only complete once all the buffers are filled.

Yes, I'm 100% sure. If you look at their APIs you will have to submit 
individual jobs as a URB in Linux. If you want to send 128 x 333 bytes 
as 333 byte sized USB HighSpeed BULK packets, then Linux/MacOS and 
Windows force you to generate 128 URBs/Jobs to send the 128 packets. In 
FreeBSD a single USB transfers can send 128x 333 bytes. Only in the case 
where you send full-sized packets having an optional short-sized packet 
in the end, Linux/MacOS and Windows allows you to accumulate them into a 
single completion event.

--HPS