From owner-freebsd-arm@FreeBSD.ORG Mon May 12 23:45:30 2014 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CB12D201; Mon, 12 May 2014 23:45:30 +0000 (UTC) Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 452BD2351; Mon, 12 May 2014 23:45:30 +0000 (UTC) Received: from c-24-8-230-52.hsd1.co.comcast.net ([24.8.230.52] helo=damnhippie.dyndns.org) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1WjzuS-0009sP-EV; Mon, 12 May 2014 23:45:28 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id s4CNjPJE034492; Mon, 12 May 2014 17:45:26 -0600 (MDT) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 24.8.230.52 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX19ajsmkMzdW1cGOhTWFPnEQ Subject: Re: USB isochronous traffic with Rasberry Pi [WAS: Re: USB audio device on Raspberry Pi] From: Ian Lepore To: Winston Smith In-Reply-To: References: <20140425154430.GA76168@utility-01.thismonkey.com> <5362638B.1080104@selasky.org> <5363C133.2000304@selasky.org> <53677CB8.5000800@selasky.org> <1399303695.22079.239.camel@revolution.hippie.lan> <1399304157.22079.243.camel@revolution.hippie.lan> <5368A93D.3070608@selasky.org> <5368AC03.8080401@selasky.org> <536CE5E9.8020408@selasky.org> <1399647986.22079.367.camel@revolution.hippie.lan> <536D0575.1040407@selasky.org> <1399661378.22079.376.camel@revolution.hippie.lan> <536DDA6D.7060101@selasky.org> <536E2EBB.7030104@selasky.org> <1399742062.22079.403.camel@revolution.hippie.lan> <536EA597.3070700@selasky.org> <536EA753.40905@selasky.org> <1399764190.22079.425.camel@revolution.hippie.lan> <536F17A1.8060807@selasky.org> <1399899978.22079.436.camel@revolution.hippie.lan> Content-Type: text/plain; charset="us-ascii" Date: Mon, 12 May 2014 17:45:25 -0600 Message-ID: <1399938325.50937.6.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: "freebsd-arm@freebsd.org" , Alexander Motin X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2014 23:45:31 -0000 On Mon, 2014-05-12 at 19:24 -0400, Winston Smith wrote: > On Mon, May 12, 2014 at 9:06 AM, Ian Lepore wrote: > > Committed as r265913; thanks for tracking this down! > > I think I lost track of this in the email thread, but: > > 1) Was this the cause of the stalls Tim described on the BBB? I don't think so. > 2) What's the criteria for this to be MFC'd back to 10-STABLE? Catching up with MFCs would be the main thing, and I'm getting started on that today. A few things here and there have been merged recently, but in general the arm tree was last sync'd 11->10 in a big way in mid-December. It's a little harder to keep arm stable branches in sync because on -current we've had so much instability for so long that it's a bit scary to MFC a change a few days or even a couple weeks after it goes into head, when you know that change is at best a small piece of fixing the overall stability and might actually de-stabilize the 10-stable branch. I think all that is calming down and things are in pretty good shape on -current right now, so it seems like a good time to get several months worth of work merged to 10-stable all at once (meaning over the next few days, as close as I can get to "at once" and still do some testing along the way). -- Ian