From owner-freebsd-arm@FreeBSD.ORG Thu May 1 15:08:10 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 64D17625 for ; Thu, 1 May 2014 15:08:10 +0000 (UTC) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 202F315EE for ; Thu, 1 May 2014 15:08:09 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 69B061FE029; Thu, 1 May 2014 17:08:02 +0200 (CEST) Message-ID: <5362638B.1080104@selasky.org> Date: Thu, 01 May 2014 17:08:59 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Johny Mattsson , freebsd-arm@freebsd.org Subject: Re: USB audio device on Raspberry Pi - link_elf: symbol isa_dmastatus undefined References: <20140425154430.GA76168@utility-01.thismonkey.com> <535A8AEA.1000100@selasky.org> <20140425204134.GA458@cicely7.cicely.de> <20140430091411.GA45015@utility-01.thismonkey.com> <5360C0A7.9010407@selasky.org> <1398867266.22079.51.camel@revolution.hippie.lan> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2014 15:08:10 -0000 On 05/01/14 01:34, Johny Mattsson wrote: > On 1 May 2014 00:14, Ian Lepore wrote: > >> I was doing some testing on a wandboard (about twice as fast an an rpi) >> with >> more than 20k int/sec without having any problems. >> > > On a similar note, I've pushed an i.MX 283 (400MHz) board to above 300k > int/sec, on Linux. Admittedly at that point my shell wasn't what you'd call > "responsive" however =) The ISR in that scenario was the GPIO handler, so > probably a bit more light-weight than an audio ISR. Hi, I'll have a look and see if I can fix it. --HPS