From owner-freebsd-firewire@FreeBSD.ORG Tue Aug 19 02:25:32 2008 Return-Path: Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9BA201065679; Tue, 19 Aug 2008 02:25:32 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from plato.miralink.com (mail.miralink.com [70.103.185.20]) by mx1.freebsd.org (Postfix) with ESMTP id 789F18FC0A; Tue, 19 Aug 2008 02:25:32 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from localhost (localhost.localdomain [127.0.0.1]) by plato.miralink.com (Postfix) with ESMTP id 1AE1D1A9149; Mon, 18 Aug 2008 19:18:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at X-Spam-Flag: NO X-Spam-Score: -4.399 X-Spam-Level: X-Spam-Status: No, score=-4.399 tagged_above=-10 required=6.6 tests=[ALL_TRUSTED=-1.8, BAYES_00=-2.599] Received: from plato.miralink.com ([127.0.0.1]) by localhost (plato.miralink.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YCqGY5Zy7xjT; Mon, 18 Aug 2008 19:18:02 -0700 (PDT) Received: from [10.47.1.6] (vpn.office.miralink.com [10.0.0.5]) by plato.miralink.com (Postfix) with ESMTP id 5AF8E1A90DC; Mon, 18 Aug 2008 19:18:02 -0700 (PDT) Message-ID: <48AA2F1A.9040306@miralink.com> Date: Mon, 18 Aug 2008 19:25:30 -0700 From: Sean Bruno User-Agent: Thunderbird 2.0.0.16 (X11/20080723) MIME-Version: 1.0 To: Dieter References: <200808190213.CAA20684@sopwith.solgatos.com> In-Reply-To: <200808190213.CAA20684@sopwith.solgatos.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Scott Long , freebsd-firewire@freebsd.org Subject: Re: Something broke :-( Re: fwcontrol update X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Aug 2008 02:25:32 -0000 Dieter wrote: > I tried rebooting again, and then powered up the camera > and pressed play. Without running fwcontrol at all. > The console spewed away. > > Just to be explicit, it didn't do this until today. > > So I think the kernel device driver needs to reset and/or > initialize something, probably on the fw controller chip. > Thoughts? > Ok, good times. Can you post the output of "fwcontrol -p" for me? -- Sean Bruno MiraLink Corporation 6015 NE 80th Ave, Ste 100 Portland, OR 97218 Cell 503-358-6832 Phone 503-621-5143 Fax 503-621-5199 MSN: sbruno@miralink.com Google: seanwbruno@gmail.com