From owner-freebsd-firewire@FreeBSD.ORG Mon Jan 16 11:02:29 2006 Return-Path: X-Original-To: freebsd-firewire@freebsd.org Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3C3DE16A41F for ; Mon, 16 Jan 2006 11:02:29 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9024443D69 for ; Mon, 16 Jan 2006 11:02:25 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k0GB2P2V084827 for ; Mon, 16 Jan 2006 11:02:25 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k0GB2N6m084821 for freebsd-firewire@freebsd.org; Mon, 16 Jan 2006 11:02:23 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 16 Jan 2006 11:02:23 GMT Message-Id: <200601161102.k0GB2N6m084821@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-firewire@FreeBSD.org Cc: Subject: Current problem reports assigned to you 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: Mon, 16 Jan 2006 11:02:29 -0000 Current FreeBSD problem reports Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/11/22] kern/74238 firewire [firewire] fw_rcv: unknown response; fire o [2005/08/29] kern/85434 firewire [fwip] fwip (IP over firewire) doesn't wo 2 problems total. Non-critical problems From owner-freebsd-firewire@FreeBSD.ORG Mon Jan 16 22:14:23 2006 Return-Path: X-Original-To: freebsd-firewire@freebsd.org Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 64B9116A41F for ; Mon, 16 Jan 2006 22:14:23 +0000 (GMT) (envelope-from freebsd@sopwith.solgatos.com) Received: from schitzo.solgatos.com (c-67-168-241-176.hsd1.or.comcast.net [67.168.241.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17A0243D46 for ; Mon, 16 Jan 2006 22:14:17 +0000 (GMT) (envelope-from freebsd@sopwith.solgatos.com) Received: from sopwith.solgatos.com (uucp@localhost) by schitzo.solgatos.com (8.11.6/8.11.6) with UUCP id k0GMEDt23760 for freebsd-firewire@freebsd.org; Mon, 16 Jan 2006 14:14:13 -0800 Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id WAA06694; Mon, 16 Jan 2006 22:14:15 GMT Message-Id: <200601162214.WAA06694@sopwith.solgatos.com> To: freebsd-firewire@freebsd.org Date: Mon, 16 Jan 2006 14:14:15 +0000 From: Dieter Subject: Problems getting firewire properly initialized. X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd@sopwith.solgatos.com List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jan 2006 22:14:23 -0000 First, I assume that hot-plugging firewire devices is supposed to work in FreeBSD? I have FreeBSD 6.0 AMD64 / nforce4 ultra onboard VT6307 firewire controller NEC uPD72871/2 firewire controller on PCI card Canon DV firewire camcorder With the NEC fw controller, If I power up the camcorder after FreeBSD is running, FreeBSD does notice. "BUS reset" , "New S100 device" ... But "fwcontrol -S" doesn't work quite right. I suspect some flow control or protocol problem. If I bring down FreeBSD, power up the camcorder, then bring up FreeBSD, "fwcontrol -S" works fine. I'm guessing that something isn't getting initialized properly in the hot-plug (actually hot-powerup) case. I have tried "fwcontrol -s" and "fwcontrol -r" and they don't help. Interestingly, rebooting doesn't affect things. If it is working and I reboot, it still works after reboot. If it isn't working, rebooting doesn't help. Power cycling the camcorder does affect it. If it is working and I power cycle the camcorder, it stops working. The only method I have found that works is to power up the camcorder when FreeBSD is not running (e.g. at firmware or boot loader prompt), and then bring up FreeBSD. With the onboard VT6307 fw controller, I have yet to find a way to get "fwcontrol -S" to work properly. Perhaps related.