cvs commit: src/sys/dev/firewire firewire.c firewire.h firewirereg.h fwdev.c

[Hidetoshi Shimokawa]

At Wed, 6 Aug 2003 11:32:57 +0930,
Greg 'groggy' Lehey wrote:
> 
> [1  <text/plain; us-ascii (7bit)>]
> On Wednesday,  6 August 2003 at 10:59:39 +0900, Hidetoshi Shimokawa wrote:
> > At Wed, 6 Aug 2003 11:11:41 +0930,
> > Greg 'groggy' Lehey wrote:
> >>
> >> On Monday,  4 August 2003 at 20:11:39 -0700, Hidetoshi Shimokawa wrote:
> >>> simokawa    2003/08/04 20:11:39 PDT
> >>>   Log:
> >>>   Change device name notation.
> >>>   - /dev/fw{,mem}X.Y represents the Y'th unit on the X'th bus.
> >>>   - /dev/fw{,mem}X is an alias of fw{,mem}X.0 for compatibility.
> >>
> >> Just out of interest, how compatible is this with NetBSD and OpenBSD?
> >
> > As far as I know, they use very different code base from ours.
> 
> Yes, I've heard that too, at least in the case of NetBSD.  That in
> itself isn't an issue.  It would be nice to have some compatibility in
> the way it's used at user level.

I understand your concern.

Actually, the main apprications of IEEE1394 are only SBP2(SCSI) and DV
stream now. As for SPB2(SCSI), we implemented it as a shim of CAM and
userland interface is (almost) unnecessary. CAM itself is different from
SCSI interface of NetBSD. As for DV stream, there is no
major application(*1) now for FreeBSD and NetBSD.

In my opinion, if we need some emulation/compatibility with other OS's,
we should consider about compatibility with Linux because they have
some application for DV streams.

IP over 1394 is another (minor?) application which will be implemented in
the kernel.

I've not checked the OpenBSD code.

(*1) We can use fwcontrol(8) to send/receive DV stream and we have DVTS
in ports collection.

/\ Hidetoshi Shimokawa
\/  simokawa at sat.t.u-tokyo.ac.jp
PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html