Kd1394.dll just uses whatever channel you hard-code into the boot
options. It then stuffs the information into the registry, which can be
read by the regular 1394 drivers. The heavy lifting is done by the
regular drivers.
To answer your original question, you can put a breakpoint anywhere in
the regular 1394 stack. It’s not actively involved in debugging.
Jake Oshins
Windows Kernel Group
This posting is provided “AS IS” with no warranties, and confers no
rights.
-----Original Message-----
Subject: RE: I am going to write a book - ITP usage
From: “Maxim S. Shatskih”
Date: Mon, 14 Oct 2002 23:47:34 +0400
X-Message-Number: 34
> Max, look at kd1394.dll I don’t think they are calling ohci1394.sys
OK. Let’s suppose they do not call ohci1394.
What will occur if, say, DV will choose the same isoch channel number
as the debugger have chosen? They must at least arbitrate the isoch
channel number over the bus to avoid some other 2 1394 nodes from
talking on the debugger’s “wavelength”.
Such an arbitration is rather hard a code. Have they copy-pasted it
from ohci1394/1394bus to kd1394?
Max