I have added my firewire controller and now detect a scsibus0 instance but
I don't appear to attach devices. I tried the USB trick of having the device
attached across hard reboot, no avail.

dmesg:

$ dmesg | grep fw
fwohci0 at pci2 dev 0 function 2: Ricoh 5C552 PCI-CardBus bridge/Firewire (rev. 0x02)
fwohci0: interrupting at irq 11
fwohci0: OHCI 1.0, 00:06:1b:03:10:03:af:90, 400Mb/s, 2048 max_rec, 4 ir_ctx, 4 it_ctx
fw0 at fwohci0: 00:06:1b:03:10:03:af:90:0a:02:ff:ff:f0:01:00:00
fwnode0 at fwohci0 Node 1: UID 08:00:46:09:00:05:a2:17
fwnode0: Link Speed: 400Mb/s, max_rec: 2048 bytes
sbpscsi0 at fwnode0

the device can be attached as USB 2.0:

cd0 at atapibus0 drive 0: <SONY, DVD RW DRU-510A, 1.0c> cdrom removable

is this as simple as adding some kind of fw equivalent of umass/wd so I do
ATAPI over firewire instead of SCSI?

kernel has:

# PCI IEEE1394 controllers
fwohci* at pci? dev ? function ?       # IEEE1394 Open Host Controller

# CardBus IEEE1394 controllers
fwohci* at cardbus? dev ? function ?   # IEEE1394 Open Host Controller

fw*    at fwbus?                       # IP over 1394

# IEEE1394 nodes
fwnode* at fwbus? idhi ? idlo ? 
sbpscsi* at fwnode?
scsibus* at sbpscsi?


-- 
George Michaelson       |  APNIC                 |  See you at APNIC 18
Email: ggm@apnic.net    |  PO Box 2131 Milton    |  Nadi, Fiji
Phone: +61 7 3858 3150  |  QLD 4064 Australia    |  31 Aug -3 Sep 2004
  Fax: +61 7 3858 3199  |  http://www.apnic.net  |  www.apnic.net/meetings/18