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 From owner-freebsd-firewire@FreeBSD.ORG Fri Jan 30 07:26:36 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 C030E16A4D1 for ; Fri, 30 Jan 2004 07:26:36 -0800 (PST) Received: from ferengi.borderworlds.dk (borderworlds.dk [62.79.110.124]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3148F43D1D for ; Fri, 30 Jan 2004 07:26:35 -0800 (PST) (envelope-from xi@borderworlds.dk) Received: from borg.borderworlds.dk (localhost [127.0.0.1]) by ferengi.borderworlds.dk (Postfix) with ESMTP id C35CF5C42; Fri, 30 Jan 2004 16:26:31 +0100 (CET) Received: by borg.borderworlds.dk (Postfix, from userid 1001) id 36BA5B831; Fri, 30 Jan 2004 16:26:31 +0100 (CET) Sender: xi@borderworlds.dk To: Hidetoshi Shimokawa 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> <87r7xhpktp.wl@tora.nunu.org> From: Christian Laursen Date: 30 Jan 2004 16:26:31 +0100 In-Reply-To: <87r7xhpktp.wl@tora.nunu.org> Message-ID: <8665ete9ug.fsf@borg.borderworlds.dk> Lines: 25 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 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 15:26:36 -0000 Hidetoshi Shimokawa writes: > At 26 Jan 2004 15:07:25 +0100, > Christian Laursen wrote: > > > > Hidetoshi Shimokawa writes: > > > > > 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? Unfortunately I just moved the card to the production server, which currently runs 5.1-RELEASE (which doesn't seem to have problems when loading the module manually). I will look into it when I get around to get it upgraded to 5.2-RELEASE. -- Best regards Christian Laursen From owner-freebsd-firewire@FreeBSD.ORG Sat Jan 31 06:27:08 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 E542616A4CE; Sat, 31 Jan 2004 06:27:08 -0800 (PST) Received: from smtp0.libero.it (smtp0.libero.it [193.70.192.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4988A43D1D; Sat, 31 Jan 2004 06:27:07 -0800 (PST) (envelope-from saturnero@gufi.org) Received: from pigra.saturnero.sat (151.37.55.168) by smtp0.libero.it (7.0.020-DD01) id 401B73BA00021188; Sat, 31 Jan 2004 15:27:06 +0100 Received: from [192.168.99.200] (libera.saturnero.sat [192.168.99.200]) by pigra.saturnero.sat (Postfix) with ESMTP id 154D8E7061; Sat, 31 Jan 2004 15:27:05 +0100 (CET) From: Dario Freni To: freebsd-firewire@freebsd.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-YCx9lmcUif3A/TCv/Vbt" Message-Id: <1075559223.615.9.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Sat, 31 Jan 2004 15:27:03 +0100 cc: freebsd-net@freebsd.org Subject: Will rfc2734 be supported? 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: Sat, 31 Jan 2004 14:27:09 -0000 --=-YCx9lmcUif3A/TCv/Vbt Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi guys, I was wondering if the standard implementation of IPoFW is planning to be implemented. I'm not expert on device writing, I was also looking for some workarounds, like attach the fwe0:lower netgraph hook to a virtual interface, but reading the rfc I realized that the normal IP packet needs an encapsulation before it's sent on the wire. Bye, Dario --=20 Dario Freni (saturnero@gufi.org) - SaturNero on IRCNet, Azzurra Gruppo Utenti FreeBSD Italia (http://www.gufi.org) GPG Public key at http://www.saturnero.net/saturnero.asc --=-YCx9lmcUif3A/TCv/Vbt Content-Type: application/pgp-signature; name=signature.asc Content-Description: Questa parte del messaggio =?ISO-8859-1?Q?=E8?= firmata -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBAG7s3Z1XqWj1OqUERAsyPAKCcHYfzuOWtgARjwpZ4wfplQbz0lACdEOib fb38jNKekHhYE8aVXsIHTWQ= =CWfh -----END PGP SIGNATURE----- --=-YCx9lmcUif3A/TCv/Vbt-- From owner-freebsd-firewire@FreeBSD.ORG Sun Feb 1 21:50:40 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 EFAE316A4CE; Sun, 1 Feb 2004 21:50:40 -0800 (PST) Received: from tora.nunu.org (YahooBB219003182070.bbtec.net [219.3.182.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3FD3343D1F; Sun, 1 Feb 2004 21:50:38 -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 EC88F4B02A; Mon, 2 Feb 2004 14:50:36 +0900 (JST) Date: Mon, 02 Feb 2004 14:50:36 +0900 Message-ID: <87d68yowr7.wl@tora.nunu.org> From: Hidetoshi Shimokawa To: Dario Freni In-Reply-To: <1075559223.615.9.camel@localhost> References: <1075559223.615.9.camel@localhost> 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=ISO-8859-1 Content-Transfer-Encoding: quoted-printable cc: freebsd-net@freebsd.org cc: freebsd-firewire@freebsd.org Subject: Re: Will rfc2734 be supported? 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: Mon, 02 Feb 2004 05:50:41 -0000 At Sat, 31 Jan 2004 15:27:03 +0100, Dario Freni wrote: >=20 > [1 ] > Hi guys, > I was wondering if the standard implementation of IPoFW is planning to > be implemented. I'm not expert on device writing, I was also looking for > some workarounds, like attach the fwe0:lower netgraph hook to a virtual > interface, but reading the rfc I realized that the normal IP packet > needs an encapsulation before it's sent on the wire. I have no plan to implement rfc2734 by myself near future. IEEE1394 is somewhat complicated, compared with Ethernet. Because there are some types of packets, fwe and IPoFW uses very different packet type and formats, so you don't have an easy workaround using netgraph. If you are interested in implementing rfc2734, you need several steps. - Implement rfc2734 encapsulation as /sys/net/if_ethersubr.c for ethernt. rfc2734 uses very different packet format from ethernet. - Implement generic GASP receive routin in the firewire driver. You need this service for multicast/broadcast packet such as an arp packet. - Implement if_fw.c for the interface device. Though I'm not sure it actually worked, the firewire driver for FreeBSD-4.0 seems to have a support for IPoFW See ftp://ftp.uec.ac.jp/pub/firewire/ for the patch. > Bye, > Dario >=20 > --=20 > Dario Freni (saturnero@gufi.org) - SaturNero on IRCNet, Azzurra > Gruppo Utenti FreeBSD Italia (http://www.gufi.org) > GPG Public key at http://www.saturnero.net/saturnero.asc > [2 Questa parte del messaggio =E8 firmata ] >=20 /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html From owner-freebsd-firewire@FreeBSD.ORG Sun Feb 1 22:22: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 84BB216A4CE; Sun, 1 Feb 2004 22:22:14 -0800 (PST) Received: from ns.koganei.wide.ad.jp (koganei.wide.ad.jp [202.249.37.254]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE9B943D1D; Sun, 1 Feb 2004 22:22:11 -0800 (PST) (envelope-from ikob@koganei.wide.ad.jp) Received: from [202.249.37.10] (tweedledee.koganei.wide.ad.jp [202.249.37.10]) (authenticated bits=0) by ns.koganei.wide.ad.jp (8.12.9/8.12.6) with ESMTP id i126M9JD057052; Mon, 2 Feb 2004 15:22:09 +0900 (JST) (envelope-from ikob@koganei.wide.ad.jp) In-Reply-To: <87d68yowr7.wl@tora.nunu.org> References: <1075559223.615.9.camel@localhost> <87d68yowr7.wl@tora.nunu.org> Mime-Version: 1.0 (Apple Message framework v612) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Message-Id: <21FEFF58-5548-11D8-AD86-000A95C44FDC@koganei.wide.ad.jp> Content-Transfer-Encoding: quoted-printable From: Kobayashi Katsushi Date: Mon, 2 Feb 2004 15:22:10 +0900 To: Hidetoshi Shimokawa X-Mailer: Apple Mail (2.612) cc: freebsd-net@freebsd.org cc: freebsd-firewire@freebsd.org cc: Dario Freni Subject: Re: Will rfc2734 be supported? 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: Mon, 02 Feb 2004 06:22:14 -0000 Hi, I have once tried to implement IP over firewire with earlier ID. spec. in the previous version of driver. The packetization, ARP and broadcast is not difficult to implement. However, I cannot believe the MCAP mechanism will not work properly, since limited No. of acceptable stream channels is supported on current firewire chipset. I think the current IP over Firewire spec.=20 does not include mechanism to suppress channel allocation in the case of receiver cannot open more stream channels. On 2004/02/02, at 14:50, Hidetoshi Shimokawa wrote: > At Sat, 31 Jan 2004 15:27:03 +0100, > Dario Freni wrote: >> >> [1 ] >> Hi guys, >> I was wondering if the standard implementation of IPoFW is planning = to >> be implemented. I'm not expert on device writing, I was also looking=20= >> for >> some workarounds, like attach the fwe0:lower netgraph hook to a=20 >> virtual >> interface, but reading the rfc I realized that the normal IP packet >> needs an encapsulation before it's sent on the wire. > > I have no plan to implement rfc2734 by myself near future. > IEEE1394 is somewhat complicated, compared with Ethernet. > Because there are some types of packets, fwe and IPoFW uses very > different packet type and formats, so you don't have an easy > workaround using netgraph. > > If you are interested in implementing rfc2734, you need several steps. > > - Implement rfc2734 encapsulation as /sys/net/if_ethersubr.c for > ethernt. rfc2734 uses very different packet format from ethernet. > > - Implement generic GASP receive routin in the firewire driver. > You need this service for multicast/broadcast packet such as an arp > packet. > > - Implement if_fw.c for the interface device. > > Though I'm not sure it actually worked, the firewire driver for > FreeBSD-4.0 seems to have a support for IPoFW > See ftp://ftp.uec.ac.jp/pub/firewire/ for the patch. > >> Bye, >> Dario >> >> --=20 >> Dario Freni (saturnero@gufi.org) - SaturNero on IRCNet, Azzurra >> Gruppo Utenti FreeBSD Italia (http://www.gufi.org) >> GPG Public key at http://www.saturnero.net/saturnero.asc >> [2 Questa parte del messaggio =E8 firmata > (7bit)>] >> > > /\ Hidetoshi Shimokawa > \/ simokawa@sat.t.u-tokyo.ac.jp > PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html > _______________________________________________ > freebsd-firewire@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-firewire > To unsubscribe, send any mail to=20 > "freebsd-firewire-unsubscribe@freebsd.org" From owner-freebsd-firewire@FreeBSD.ORG Tue Feb 3 01:27:33 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 147DC16A4CE; Tue, 3 Feb 2004 01:27:33 -0800 (PST) Received: from herring.nlsystems.com (mailgate.nlsystems.com [80.177.232.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A6B043D45; Tue, 3 Feb 2004 01:27:30 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from [10.0.0.2] (herring.nlsystems.com [10.0.0.2]) i139RHpE055169; Tue, 3 Feb 2004 09:27:18 GMT (envelope-from dfr@nlsystems.com) From: Doug Rabson To: Hidetoshi Shimokawa In-Reply-To: <87d68yowr7.wl@tora.nunu.org> References: <1075559223.615.9.camel@localhost> <87d68yowr7.wl@tora.nunu.org> Content-Type: text/plain Message-Id: <1075800437.50848.14.camel@herring.nlsystems.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Tue, 03 Feb 2004 09:27:17 +0000 Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on herring.nlsystems.com cc: freebsd-net@freebsd.org cc: freebsd-firewire@freebsd.org cc: Dario Freni Subject: Re: Will rfc2734 be supported? 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: Tue, 03 Feb 2004 09:27:33 -0000 On Mon, 2004-02-02 at 05:50, Hidetoshi Shimokawa wrote: > At Sat, 31 Jan 2004 15:27:03 +0100, > Dario Freni wrote: > > > > [1 ] > > Hi guys, > > I was wondering if the standard implementation of IPoFW is planning to > > be implemented. I'm not expert on device writing, I was also looking for > > some workarounds, like attach the fwe0:lower netgraph hook to a virtual > > interface, but reading the rfc I realized that the normal IP packet > > needs an encapsulation before it's sent on the wire. > > I have no plan to implement rfc2734 by myself near future. > IEEE1394 is somewhat complicated, compared with Ethernet. > Because there are some types of packets, fwe and IPoFW uses very > different packet type and formats, so you don't have an easy > workaround using netgraph. > > If you are interested in implementing rfc2734, you need several steps. > > - Implement rfc2734 encapsulation as /sys/net/if_ethersubr.c for > ethernt. rfc2734 uses very different packet format from ethernet. > > - Implement generic GASP receive routin in the firewire driver. > You need this service for multicast/broadcast packet such as an arp > packet. > > - Implement if_fw.c for the interface device. > > Though I'm not sure it actually worked, the firewire driver for > FreeBSD-4.0 seems to have a support for IPoFW > See ftp://ftp.uec.ac.jp/pub/firewire/ for the patch. I spent a little time recently thinking about what would be needed for this and came to similar conclusions. The most interesting part is implementing generic GASP receive. I think the nicest way of doing that would be to implement a new network protocol for firewire, allowing userland programs to do something like: struct sockaddr_firewire a; s = socket(PF_FIREWIRE, SOCK_DGRAM, 0); a.sof_address = 0x12345000; ...; bind(s, &a, sizeof a); ...; len = recv(s, buf, sizeof buf, 0); Internally, this probably means arranging for all asynchronous packets to be DMA'd directly into mbufs and would probably change the firewire code a great deal. Still, it might be worth it to gain a familiar socket-based user api. From owner-freebsd-firewire@FreeBSD.ORG Tue Feb 3 05:33:05 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 018E816A4CF; Tue, 3 Feb 2004 05:33:05 -0800 (PST) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 58A3F43D31; Tue, 3 Feb 2004 05:33:03 -0800 (PST) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id 804B1654EF; Tue, 3 Feb 2004 13:33:01 +0000 (GMT) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 39397-02-3; Tue, 3 Feb 2004 13:33:01 +0000 (GMT) Received: from saboteur.dek.spc.org (82-147-17-88.dsl.uk.rapidplay.com [82.147.17.88]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by arginine.spc.org (Postfix) with ESMTP id C0EF5654E1; Tue, 3 Feb 2004 13:32:58 +0000 (GMT) Received: by saboteur.dek.spc.org (Postfix, from userid 1001) id 91B9740; Tue, 3 Feb 2004 13:32:57 +0000 (GMT) Date: Tue, 3 Feb 2004 13:32:57 +0000 From: Bruce M Simpson To: Dario Freni Message-ID: <20040203133257.GJ713@saboteur.dek.spc.org> Mail-Followup-To: Dario Freni , freebsd-firewire@freebsd.org, freebsd-net@freebsd.org, jkh@FreeBSD.org References: <1075559223.615.9.camel@localhost> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3siQDZowHQqNOShm" Content-Disposition: inline In-Reply-To: <1075559223.615.9.camel@localhost> cc: freebsd-net@freebsd.org cc: freebsd-firewire@freebsd.org cc: jkh@FreeBSD.org Subject: Re: Will rfc2734 be supported? 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: Tue, 03 Feb 2004 13:33:05 -0000 --3siQDZowHQqNOShm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sat, Jan 31, 2004 at 03:27:03PM +0100, Dario Freni wrote: > I was wondering if the standard implementation of IPoFW is planning to > be implemented. I'm not expert on device writing, I was also looking for I've already asked Jordan about a code drop from Apple; he's trying to get an answer from the appropriate people. BMS --3siQDZowHQqNOShm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Comment: '' iD8DBQFAH6MIueUpAYYNtTsRAlAWAKClyKvsZ6MbiBqjfvd/ex4UX6xaBQCfRdyb w0In6x2AUBq0sP4gPFaoYsw= =2EIO -----END PGP SIGNATURE----- --3siQDZowHQqNOShm-- From owner-freebsd-firewire@FreeBSD.ORG Tue Feb 3 09:19:36 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 304C616A4CF; Tue, 3 Feb 2004 09:19:36 -0800 (PST) Received: from jkh-gw.brierdr.com (adsl-64-173-3-158.dsl.sntc01.pacbell.net [64.173.3.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B44D43D5D; Tue, 3 Feb 2004 09:19:35 -0800 (PST) (envelope-from jkh@queasyweasel.com) Received: from [64.173.15.98] (IDENT:1234-ident-is-a-completely-pointless-protocol-that-offers-no-security-or-traceability-at-all-so-tak@adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by jkh-gw.brierdr.com (8.12.10/8.12.10) with ESMTP id i13HJCi5030359; Tue, 3 Feb 2004 09:19:12 -0800 (PST) (envelope-from jkh@queasyweasel.com) In-Reply-To: <20040203133257.GJ713@saboteur.dek.spc.org> References: <1075559223.615.9.camel@localhost> <20040203133257.GJ713@saboteur.dek.spc.org> Mime-Version: 1.0 (Apple Message framework v612) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <1C6EE8A8-566D-11D8-A1CB-000393BB9222@queasyweasel.com> Content-Transfer-Encoding: 7bit From: "Jordan K. Hubbard" Date: Tue, 3 Feb 2004 09:19:23 -0800 To: Bruce M Simpson X-Mailer: Apple Mail (2.612) cc: Jordan Hubbard cc: freebsd-net@freebsd.org cc: Dario Freni cc: freebsd-firewire@freebsd.org cc: Kevin Van Vechten Subject: Re: Will rfc2734 be supported? 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: Tue, 03 Feb 2004 17:19:36 -0000 It's up on the web site now, according to Kevin on the CC line (who was supposed to contact you but evidently did not :-). - Jordan On Feb 3, 2004, at 5:32 AM, Bruce M Simpson wrote: > On Sat, Jan 31, 2004 at 03:27:03PM +0100, Dario Freni wrote: >> I was wondering if the standard implementation of IPoFW is planning to >> be implemented. I'm not expert on device writing, I was also looking >> for > > I've already asked Jordan about a code drop from Apple; he's trying to > get > an answer from the appropriate people. > > BMS > -- Jordan K. Hubbard Engineering Manager, BSD technology group Apple Computer From owner-freebsd-firewire@FreeBSD.ORG Tue Feb 3 11:02:19 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 A9FED16A4CE; Tue, 3 Feb 2004 11:02:19 -0800 (PST) Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 857B943D45; Tue, 3 Feb 2004 11:02:18 -0800 (PST) (envelope-from kvv@apple.com) Received: from mailgate2.apple.com (a17-128-100-204.apple.com [17.128.100.204])i13J2IX3002285; Tue, 3 Feb 2004 11:02:18 -0800 (PST) Received: from relay2.apple.com (relay2.apple.com) by mailgate2.apple.com ; Tue, 3 Feb 2004 11:02:18 -0800 Received: from apple.com (wisenheimer.apple.com [17.202.41.161]) by relay2.apple.com (8.12.11/8.12.11) with ESMTP id i13J2FLK006294; Tue, 3 Feb 2004 19:02:16 GMT Date: Tue, 3 Feb 2004 11:02:15 -0800 Content-Type: text/plain; delsp=yes; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) To: Bruce M Simpson From: Kevin Van Vechten In-Reply-To: <1C6EE8A8-566D-11D8-A1CB-000393BB9222@queasyweasel.com> Message-Id: <7AEC679F-567B-11D8-9298-000A956D3902@apple.com> Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.552) cc: freebsd-net@freebsd.org cc: Dario Freni cc: freebsd-firewire@freebsd.org cc: Jordan Hubbard Subject: Re: Will rfc2734 be supported? 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: Tue, 03 Feb 2004 19:02:20 -0000 The source code of the Mac OS X 10.3 (Panther) implementation is available from Apple's open source web site (APSL registration required): There is also a mirror at OpenDarwin.org: - Kevin On Tuesday, February 3, 2004, at 09:19 AM, Jordan K. Hubbard wrote: > It's up on the web site now, according to Kevin on the CC line (who > was supposed to contact you but evidently did not :-). > > - Jordan > > On Feb 3, 2004, at 5:32 AM, Bruce M Simpson wrote: > >> On Sat, Jan 31, 2004 at 03:27:03PM +0100, Dario Freni wrote: >>> I was wondering if the standard implementation of IPoFW is planning >>> to >>> be implemented. I'm not expert on device writing, I was also looking >>> for >> >> I've already asked Jordan about a code drop from Apple; he's trying >> to get >> an answer from the appropriate people. >> >> BMS >> > -- > Jordan K. Hubbard > Engineering Manager, BSD technology group > Apple Computer > From owner-freebsd-firewire@FreeBSD.ORG Sat Feb 7 03:38:08 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 9390C16A4CE for ; Sat, 7 Feb 2004 03:38:08 -0800 (PST) Received: from hermes2.uwskoeln.de (unknown [194.8.213.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id 39B2C43D39 for ; Sat, 7 Feb 2004 03:38:08 -0800 (PST) (envelope-from oliver.hoffmann@uw-service.de) Received: from [192.168.8.25] (helo=uw-service.de) by hermes2.uwskoeln.de with esmtp (Exim 3.36 #1 (Debian)) id 1AoO35-0003qr-00 for ; Wed, 04 Feb 2004 15:30:39 +0100 Received: from hoffmann.uwskoeln.de by uw-service.de with SMTP (MDaemon.PRO.v5.0.5.R) for ; Wed, 04 Feb 2004 15:34:03 +0100 From: Oliver Hoffmann To: freebsd-firewire@freebsd.org Date: Wed, 4 Feb 2004 15:30:19 +0100 User-Agent: KMail/1.5.4 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200402041530.19751.oliver.hoffmann@uw-service.de> X-Return-Path: oliver.hoffmann@uw-service.de X-MDaemon-Deliver-To: freebsd-firewire@freebsd.org Subject: Odd problems with 5.1 RELEASE 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: Sat, 07 Feb 2004 11:38:08 -0000 Hi all! I do backups to external firewire-hds. The fw-controler-card is the Texas Instruments TSB12LV26. I connected an external 5.25" case (oxford 911) with a mobilerack inside. In this rack is a160 GB (Maxtor 6Y160PO) harddisk. It runs FreeBSD 5.1 RELEASE on an Athlon 1500+ with an Abit motherboard. It has one ICP-Vortex with a raid-system (ca. 200 GB, level 5). I had a lot of trouble with 4.7 and 4.8 and I couldn't use 5.0 because of the raid-controler. Thus the time I installed the system 5.1 REL. was probably the best for my situation. But this server is not stable (not as stable as I expect from FreeBSD). I'm not sure whether this has something to do with firewire or not: http://www.freebsd.org/cgi/query-pr.cgi?pr=i386/60919. Does somebody had such problems in combination with fw? Another issue are strange sporadic crashes particular at night after or during the backups. There is nothing to see in the logs or at ttyv0. It just hangs completely. These crashes occured more often after I connected a second HD for a monthly backup. I have a second fileserver (5.1 REL.) with IDE-raid, but the same firewire hardware (only one fw-HD). It works flawless. When I switch off the second fw-disk (/dev/da0) and then try too mount the first one or start sysinstall those processes will be in the process list for ever (without doing what I want of course). It is not possible to kill them until I switch this device on again. I want to remove da0 again, because I want to check whether this second disk has an influence concerning stability. But how can I do that? I wonder why the second fw-disk gets the name da0 and the first one da2. I also wonder why I have to switch of da2 in order to get the system booting. A df -h with both backup-disks mounted: Filesystem Size Used Avail Capacity Mounted on /dev/ad0s1a 475M 71M 366M 16% / devfs 1.0K 1.0K 0B 100% /dev /dev/ad0s1g 15G 2.0K 14G 0% /data /dev/ad0s1e 248M 10.0K 228M 0% /tmp /dev/ad0s1f 989M 615M 295M 68% /usr /dev/ad0s1d 248M 7.5M 220M 3% /var /dev/da1s1e 157G 84G 60G 58% /mnt/raid1 /dev/da1s1f 44G 29G 11G 72% /mnt/raid2 /dev/da0s1d 184G 2.0K 169G 0% /mnt/fw2 /dev/da2s1e 148G 16G 120G 12% /mnt/fw Thanks a lot for help in advance! Greetings, Oliver.