From owner-freebsd-firewire@FreeBSD.ORG Sun Jul 20 02:51:52 2003 Return-Path: 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 59ECE37B401 for ; Sun, 20 Jul 2003 02:51:52 -0700 (PDT) Received: from is2.mh.itc.u-tokyo.ac.jp (is2.mh.itc.u-tokyo.ac.jp [133.11.205.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id F402543F85 for ; Sun, 20 Jul 2003 02:51:48 -0700 (PDT) (envelope-from simokawa@sat.t.u-tokyo.ac.jp) Received: from is2.mh.itc.u-tokyo.ac.jp (is2.mh.itc.u-tokyo.ac.jp [127.0.0.1]) by is2.mh.itc.u-tokyo.ac.jp (Postfix) with ESMTP id 6BE45378376 for ; Sun, 20 Jul 2003 18:51:46 +0900 (JST) Received: from mailhosting.itc.u-tokyo.ac.jp (IDENT:mirapoint@mailhosting.itc.u-tokyo.ac.jp [133.11.205.3]) h6K9pk0S019595; Sun, 20 Jul 2003 18:51:46 +0900 Received: from ett.sat.t.u-tokyo.ac.jp (ett.sat.t.u-tokyo.ac.jp [133.11.135.3])3.3.5-GR) with ESMTP id AJJ53776; Sun, 20 Jul 2003 18:51:44 +0900 (JST) Date: Sun, 20 Jul 2003 18:51:44 +0900 Message-ID: From: Hidetoshi Shimokawa To: "Petr Holub" In-Reply-To: <000001c34e9b$e0d99880$2be86cc2@kloboucek> References: <000001c34e9b$e0d99880$2be86cc2@kloboucek> User-Agent: Wanderlust/2.11.0 (Wonderwall) REMI/1.14.3 (Matsudai) FLIM/1.14.3 (=?ISO-8859-1?Q?Unebigory=F2mae?=) APEL/10.3 MULE XEmacs/21.4 (patch 8) (Honest Recruiter) (i386--freebsd) X-Face: OE([KxWyJI0r[R~S/>7ia}SJ)i%a,$-9%7{*yihQk|]gl}2p#"oXmX/fT}Bn7: #j7i14gu$jgR\S*&C3R/pJX cc: firewire@freebsd.org Subject: Re: firewire problem on 5.1-RELEASE X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Vendors pre-release coordination List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Jul 2003 09:51:52 -0000 At Sun, 20 Jul 2003 10:49:49 +0200, Petr Holub wrote: > > Hi Hidetoshi, > > > Those may indicate some hardware problem. > > 5.1 does more strict check on sid buffer. > > the machine is the same and it used to work on 5.0. When I say > "work" I mean I've been able to read from the camera without any > problem. > > If it helps dmesg output is below. > > > > fwohci0: IR DMA overrun (0x40008011) > > > fwohci0: IR DMA overrun (0x40008011) > > > fwohci0: IR DMA overrun (0x40008011) > > > fwohci0: IR DMA overrun (0x40008011) > > > > How do you read from camera and where do you write the data? > > If you cannot read/write fast enough, the buffer overrun > > could ocurr. > > The code for reading is based on your dv/dvrecv/dvsend that you gave > me some time ago (approx. March this year) when I was wondering > why DVTS doesn't work. This code used to work on 5.0 so that's > why I'm a bit confused why it stopped working. I have changed API since 5.0. Use fwcontrol instead of dv*. /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html