Re: 1394 isochronous troubles
- From: "J. Koeter" <j_koeter@xxxxxxxxxxx>
- Date: Sun, 18 Jun 2006 04:03:20 GMT
r_konjeti@xxxxxxxxxxxx wrote:
1) I think by windows driver design(not just 1394) the device object
is NULL in completion routine. Use your context properly to pass
device object information.
2) I also think your DetachCompletionRoutine should not do
AttachBuffer.
Thanks for your comments!
I finaly found a solution for my problem.
Since I am fairly new to driver writing all sugestions are welcome so I
did as you suggested; I don't use the device object in the completion
routine, I just call IoFreeIrp, ExFreePool(irb) and return
STATUS_MORE_PROCESSING_REQUIRED.
Then, I put the AttachBuffer in the callback function after the
DetachBuffer.
As mentioned before, this works fine for me.
Regards, Jeroen
.
- References:
- 1394 isochronous troubles
- From: Jeroen Koeter
- Re: 1394 isochronous troubles
- From: cristalink
- Re: 1394 isochronous troubles
- From: r_konjeti
- 1394 isochronous troubles
- Prev by Date: Re: sync/async NdisTransferData()
- Next by Date: Re: cardbus driver
- Previous by thread: Re: 1394 isochronous troubles
- Next by thread: Transmission Timeout on parallel
- Index(es):
Relevant Pages
|
