From owner-freebsd-firewire@FreeBSD.ORG Tue May 20 03:19:02 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 9635237B401 for ; Tue, 20 May 2003 03:19:02 -0700 (PDT) Received: from mk-smarthost-2.mail.uk.tiscali.com (mk-smarthost-2.mail.uk.tiscali.com [212.74.114.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB17A43FA3 for ; Tue, 20 May 2003 03:19:01 -0700 (PDT) (envelope-from b.candler@pobox.com) Received: from [212.74.113.66] (helo=vaio.linnet.org) by mk-smarthost-2.mail.uk.tiscali.com with esmtp (Exim 4.14) id 19I4Cx-0006gb-SW; Tue, 20 May 2003 11:19:00 +0100 Received: from brian by vaio.linnet.org with local (Exim 4.20) id 19I4D1-0000PP-3E; Tue, 20 May 2003 10:19:03 +0000 Date: Tue, 20 May 2003 10:19:02 +0000 From: Brian Candler To: Hidetoshi Shimokawa Message-ID: <20030520101902.GA1534@uk.tiscali.com> References: <20030519140620.GA2377@uk.tiscali.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: freebsd-firewire@freebsd.org Subject: Re: Support for CXD1847A controller? 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: Tue, 20 May 2003 10:19:02 -0000 > But I afraid CXD1847A(actually this must be CXD1947A) > is not OHCI compliant and not supported anyway... Thanks for that information. Do you know how different this chip is to OHCI? If it's similar I could work on it myself. I actually installed 4.8-RELEASE last night, and did a tweak of fwohci_pci_probe to accept the chip. It then told me to set PNP_OS=NO in the BIOS, which I did. After that, it seemed to detect the interface: fwohci0: mem 0xfecffc00-0xfecffdff irq 9 at device 9.0 on pci0 fwohci0: PCI bus latency is 64. fwohci0: OHCI version 0.0 (ROM=0) fwohci0: No. of Isochronous channel is 0. fwohci0: EUI64 00:00:00:00:00:00:00:00 fwohci0: fwphy_rddata: loop=100, retry=101 fwohci0: Phy 1394 only S100, 0 ports. fwohci0: fwphy_rddata: loop=100, retry=101 fwohci0: Link S100, max_rec 2 bytes. fwohci0: max_rec 2 -> 512 firewire0: on fwohci0 sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: fwphy_rddata: loop=100, retry=101 fwohci0: fwphy_rddata: loop=100, retry=101 Hmm, looks like it failed to read anything back, and fwcontrol doesn't find anything either: # fwcontrol fwcontrol: open: Device not configured That's with no devices attached, but I imagine that the host controller itself should show up. So looks like a no go... Regards, Brian.