From owner-freebsd-firewire@FreeBSD.ORG  Fri Aug 22 01:28:02 2008
Return-Path: <owner-freebsd-firewire@FreeBSD.ORG>
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 42E0C1065682
	for <freebsd-firewire@freebsd.org>;
	Fri, 22 Aug 2008 01:28:02 +0000 (UTC)
	(envelope-from freebsd@sopwith.solgatos.com)
Received: from parsely.rain.com (parsely.rain.com [199.26.172.196])
	by mx1.freebsd.org (Postfix) with ESMTP id CDD3D8FC18
	for <freebsd-firewire@freebsd.org>;
	Fri, 22 Aug 2008 01:28:01 +0000 (UTC)
	(envelope-from freebsd@sopwith.solgatos.com)
Received: from sopwith.solgatos.com (uucp@localhost)
	by parsely.rain.com (8.11.4/8.11.4) with UUCP id m7M1Rsg60239;
	Thu, 21 Aug 2008 18:27:54 -0700 (PDT)
	(envelope-from freebsd@sopwith.solgatos.com)
Received: from localhost by sopwith.solgatos.com (8.8.8/6.24)
	id BAA25657; Fri, 22 Aug 2008 01:26:13 GMT
Message-Id: <200808220126.BAA25657@sopwith.solgatos.com>
To: Sean Bruno <sbruno@miralink.com>
In-reply-to: Your message of "Thu, 21 Aug 2008 13:35:00 PDT."
	<48ADD174.90002@miralink.com> 
Date: Thu, 21 Aug 2008 18:26:13 +0100
From: Dieter <freebsd@sopwith.solgatos.com>
Cc: 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 <freebsd-firewire.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-firewire>, 
	<mailto:freebsd-firewire-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-firewire>
List-Post: <mailto:freebsd-firewire@freebsd.org>
List-Help: <mailto:freebsd-firewire-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-firewire>, 
	<mailto:freebsd-firewire-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Aug 2008 01:28:02 -0000

> Can you run a live linux distro(unbuntu or knoppix) and see if linux can 
> "reset"
> your NEC f/w controller?

Grumble...  If I get penguinix to boot will you look at

http://www.freebsd.org/cgi/query-pr.cgi?pr=113785
http://www.freebsd.org/cgi/query-pr.cgi?pr=118093

These two are more problematic than the NEC.

> Otherwise, I will be going down a very long and tedious path to try and 
> discover what has
> broken.  This will take me a long time.

Before you do that...

	What path are you planning on going down?
	We don't know what broke it: fwcontrol, camera in
	camera mode, or something else we haven't thought of.

	Seems to me that the solution is to look at the
	datasheet and the device driver and figure out what
	isn't getting initialized.  So we need to find the
	datasheet for the NEC.