From owner-freebsd-firewire@FreeBSD.ORG Fri Jan 30 06:34:14 2004 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 4E3CF16A4CE for ; Fri, 30 Jan 2004 06:34:14 -0800 (PST) Received: from tora.nunu.org (YahooBB219003182070.bbtec.net [219.3.182.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3242843D1F for ; Fri, 30 Jan 2004 06:34:09 -0800 (PST) (envelope-from simokawa@sat.t.u-tokyo.ac.jp) Received: from tora.nunu.org (unknown [192.168.1.2]) by tora.nunu.org (Postfix) with ESMTP id EACDB4AF5B; Fri, 30 Jan 2004 23:33:54 +0900 (JST) Date: Fri, 30 Jan 2004 23:33:54 +0900 Message-ID: <87r7xhpktp.wl@tora.nunu.org> From: Hidetoshi Shimokawa To: Christian Laursen In-Reply-To: <86wu7e7qhu.fsf@borg.borderworlds.dk> References: <86isja24y0.fsf@borg.borderworlds.dk> <87ptd6rj6n.wl@tora.nunu.org> <86isiy99fg.fsf@borg.borderworlds.dk> <87n08arext.wl@tora.nunu.org> <86wu7e7qhu.fsf@borg.borderworlds.dk> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 MULE XEmacs/21.4 (patch 14) (Reasonable Discussion) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII cc: freebsd-firewire@freebsd.org Subject: Re: NEC uPD72873 X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jan 2004 14:34:14 -0000 At 26 Jan 2004 15:07:25 +0100, Christian Laursen wrote: > > Hidetoshi Shimokawa writes: > > > At 26 Jan 2004 13:33:07 +0100, > > Christian Laursen wrote: > > > > > > Hidetoshi Shimokawa writes: > > > > > > > Sorry to respond you late. > > > > Is the driver statically linked with kernel or loaded as a module? > > > > > > It is loaded as a module? > > > > > > Should I try to compile it into the kernel? > > > > Can you put the following line into the /boot/loader.conf? > > > > firewire_load="YES" > > That did the trick, thank you. The following change should fix your problem. Could you try again with manual load? ----------------------------------- simokawa 2004/01/30 06:28:12 PST FreeBSD src repository Modified files: sys/dev/firewire firewire.c fwohci.c fwohci_pci.c Log: Use device_identify and bus_add_child methods to add a firewire bus on fwohci. This should fix attach failure caused by a race between firewire and fwochi initialization for the kernel module. Revision Changes Path 1.69 +13 -4 src/sys/dev/firewire/firewire.c 1.73 +0 -1 src/sys/dev/firewire/fwohci.c 1.39 +44 -25 src/sys/dev/firewire/fwohci_pci.c ------------------------------------- > The patch I posted in my initial post is still relevant though, I guess, > as it just allows the chip to be identified. Committed, thanks. /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html