Could you give me a little more detail about what you are trying to
do? I am reasonably familiar with the 1394 stack and haven’t run into
this type of problem. The lower level 1394 drivers certainly have
many, what should I call them, undocumented features (never say bug).
Tim, thank you very much.
To be honesty, i know just a little about 1394 host controller. For we are only developing the window driver for the device ,we know the data format that the device
defined, and we fill cdb member in srb and so on, then pass the irp to the lower. That’s all. Then i will try to find is there any way to do like usb host controller,
thanks a again for your suggestion. But i have a question that i think that is very important.
When you according to the ddk, must do this, should do that, at last, problem encountered, then, what your way to solve the problem?
e.g, in this development, we found the driver that microsoft suplied(lower driver) return STATUS_PENDING from iocalldriver, but it can not be canceled, the completion
routine for the irp never got invoked. It takes me a lot of time to fix the problem, even so far, i have not found the solution. If i have the source of the lower driver,
i promise i fix the problem use much little time:)…
Robert Newton