From owner-freebsd-arm@FreeBSD.ORG Wed Feb 27 20:51:36 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 0537EF4E; Wed, 27 Feb 2013 20:51:36 +0000 (UTC) (envelope-from ray@freebsd.org) Received: from smtp.dlink.ua (smtp.dlink.ua [193.138.187.146]) by mx1.freebsd.org (Postfix) with ESMTP id AC039E79; Wed, 27 Feb 2013 20:51:35 +0000 (UTC) Received: from rnote.ddteam.net (187-24-135-95.pool.ukrtel.net [95.135.24.187]) (Authenticated sender: ray) by smtp.dlink.ua (Postfix) with ESMTPSA id 7A735C4927; Wed, 27 Feb 2013 22:51:27 +0200 (EET) Date: Wed, 27 Feb 2013 22:51:12 +0200 From: Aleksandr Rybalko To: Adrian Chadd Subject: Re: Raspberry Pi Network Data Message-Id: <20130227225112.b480823a.ray@freebsd.org> In-Reply-To: References: <20130226120335.6928b473@ivory.wynn.com> <1361904727.16937.133.camel@revolution.hippie.lan> <20130226224901.04164f9d.ray@freebsd.org> Organization: FreeBSD.ORG X-Mailer: Sylpheed 3.1.2 (GTK+ 2.24.5; amd64-portbld-freebsd9.0) X-Operating-System: FreeBSD Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-arm@freebsd.org, Brett Wynkoop , Ian Lepore X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Feb 2013 20:51:36 -0000 On Tue, 26 Feb 2013 13:56:43 -0800 Adrian Chadd wrote: > On 26 February 2013 12:49, Aleksandr Rybalko wrote: > > > Hello ARM hackers! > > > > Guys, connect please RPi to good, standalone 5V powers supply (1-2A > > will be enough) instead of USB port of something. That will close > > most problems, at least Ian's problem :-D > > Sure! But the side question is - can the error handling be improved? > It's coming/going and that's fine; but can the reattach be made more > reliable? It will be very nice, but I have only one idea which may help somehow, it is check current and voltage on all ports if hub or phy support that. But there is too much troubles: * Most embedded devices connect USB +5V line directly to main supply bus; * Most controllers have only OVER_CURRENT flag, so you can't calculate total power consumption or get voltage level on rail; * We need to know power source parameters. So we don't know how that consumption affect system as result we have voltage lower than minimum required in main system (lost bits, then fault and reboot) or in attached USB device (just device lost). So I see no way to detect that properly :( Maybe Hans can give some hints? > > > > Adrian -- Aleksandr Rybalko