From owner-freebsd-firewire@FreeBSD.ORG Thu Jan 10 20:15:08 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 2A3CB16A421 for ; Thu, 10 Jan 2008 20:15:08 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from schitzo.solgatos.com (pool-96-225-216-68.ptldor.fios.verizon.net [96.225.216.68]) by mx1.freebsd.org (Postfix) with ESMTP id EFF1213C442 for ; Thu, 10 Jan 2008 20:15:07 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from schitzo.solgatos.com (localhost.home.localnet [127.0.0.1]) by schitzo.solgatos.com (8.14.1/8.13.8) with ESMTP id m0AJfDgR012204 for ; Thu, 10 Jan 2008 11:41:13 -0800 Received: from sopwith.solgatos.com (uucp@localhost) by schitzo.solgatos.com (8.14.1/8.13.4/Submit) with UUCP id m0AJfDSc012201 for freebsd-firewire@freebsd.org; Thu, 10 Jan 2008 11:41:13 -0800 Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id TAA05489; Thu, 10 Jan 2008 19:39:00 GMT Message-Id: <200801101939.TAA05489@sopwith.solgatos.com> To: freebsd-firewire@freebsd.org Date: Thu, 10 Jan 2008 11:39:00 +0000 From: Dieter Subject: Can I force "non CYCLEMASTER mode" ? 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: Thu, 10 Jan 2008 20:15:08 -0000 Re: kern/113785 Could "CYCLEMASTER mode" vs. "non CYCLEMASTER mode" be the source of my firewire problems? Is it possible to force FreeBSD to be in "non CYCLEMASTER mode" ? Thanks. ------- Forwarded Message > > There is no initialization packet to send streams; > > By initialization, I meant whatever conversation FreeBSD and the > camcorder have once they are both up. > > > however, > > it might be a problem who is the cycle/bus/IR manager. > > Can you see some difference of the output of the fwcontrol(8) and demsg(8) > > in node-id, cycle master and etc. between success and failed cases? > > Yes, we have a couple of new clues: > > When FreeBSD says "CYCLEMASTER mode" it does not work. > When FreeBSD says "non CYCLEMASTER mode" it works. > > Also: > > The controller that works (if booted in correct order): > > just bsd: > # fwcontrol -u 1 -t > crc_len: 3 generation:2 node_count:1 sid_count:1 > id link gap_cnt speed delay cIRM power port0 port1 port2 ini more > 00 1 5 S400 0 1 -9W - - 1 0 > > now power up camcorder (does not work): > > # fwcontrol -u 1 -t > crc_len: 4 generation:3 node_count:2 sid_count:2 > id link gap_cnt speed delay cIRM power port0 port1 port2 ini more > 00 1 63 S100 0 1 0W - P 1 0 > 01 1 5 S400 0 1 -9W - C 0 0 > > Looks like the S400 & non-zero power device (BSD box) changed id from 00 to 01? > > after booting camcorder and FreeBSD in correct order (works): > > # fwcontrol -u 1 -t > crc_len: 4 generation:1 node_count:2 sid_count:2 > id link gap_cnt speed delay cIRM power port0 port1 port2 ini more > 00 1 63 S400 0 1 -9W - P 1 0 > 01 1 63 S100 0 1 0W - C 0 0 > > Note that the BSD box is id 00. > > The controller that never works: > > # fwcontrol -u 0 -t > crc_len: 4 generation:2 node_count:2 sid_count:2 > id link gap_cnt speed delay cIRM power port0 port1 port2 ini more > 00 1 5 S100 0 1 0W - P 0 0 > 01 1 5 S400 0 1 15W C - 1 0 > > The BSD box is id 01. > Perhaps the "C" showing up under port0 instead of port1 is significant? > > So: if the BSD box is id 00, camcorder is id 01 -> works > if the BSD box is id 01, camcorder is id 00 -> does not work > > > Thanks for a fix for the compiler warning. > > You're welcome. ------- End of Forwarded Message