From owner-freebsd-arm@FreeBSD.ORG Mon May 5 19:24:29 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 58687C1E for ; Mon, 5 May 2014 19:24:29 +0000 (UTC) Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) (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 2802B5DE4 for ; Mon, 5 May 2014 19:24:28 +0000 (UTC) Received: from c-24-8-230-52.hsd1.co.comcast.net ([24.8.230.52] helo=damnhippie.dyndns.org) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1WhOV1-0008Mv-IJ; Mon, 05 May 2014 19:24:27 +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 s45JOOqs024057; Mon, 5 May 2014 13:24:24 -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: U2FsdGVkX1/IfNjCO2qZbnOGEuDZgoTM Subject: Re: USB audio device on Raspberry Pi - link_elf: symbol isa_dmastatus undefined From: Ian Lepore To: ticso@cicely.de In-Reply-To: <20140505182722.GD78493@cicely7.cicely.de> 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> <5362638B.1080104@selasky.org> <20140505173709.GR43976@funkthat.com> <20140505182722.GD78493@cicely7.cicely.de> Content-Type: text/plain; charset="us-ascii" Date: Mon, 05 May 2014 13:24:24 -0600 Message-ID: <1399317864.22079.260.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 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, 05 May 2014 19:24:29 -0000 On Mon, 2014-05-05 at 20:27 +0200, Bernd Walter wrote: > On Mon, May 05, 2014 at 10:37:09AM -0700, John-Mark Gurney wrote: > > Hans Petter Selasky wrote this message on Thu, May 01, 2014 at 17:08 +0200: > > > 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. > > > > So, I have both a BBW and a BBB and both devices don't have working > > USB... If I plug in a device, like a uftdi serial adapter, the blue > > light flashes briefly but then stays off... It should stay on... > > AFAIK we don't switch any LED at all, so this probably is a power problem. > What rating has your power supply? > Do you use the barrel or USB plug to power the board? > I think you need to use the barrel plug for additional load, since > the board has some kind of current limitation for the USB connector. > That LED behavior is the FDTI adapter hardware. Depending on how you wire them, you can get several behaviors out of FTDI LEDs. If you wired an LED to the PWREN# it would behave like that if the host system told the hub to shutdown port power. I had such a problem with the new FTDI H-series chips once, because their device descriptor says they need up to 150mA (although in normal uart modes they never draw anywhere near that). I was plugging them into a bus-powered hub and it would power up, read the descriptor, and power right back down. When I plugged the hub's power adapter in it started working fine. -- Ian