Completion routine not being called in Tx path of NDIS-WDM driver

Discussion in 'Windows Vista Drivers' started by Harshal Chhaya, Nov 11, 2004.

  1. Harshal Chhaya

    Harshal Chhaya Guest

    Hi,

    In an NDIS-WDM driver for a wireless device, I find that the Rx path
    works but the Tx path never calls the function specified in the
    'IoSetCompletionRoutine()' function.

    The NDIS portion of the driver processes the packet and sends it to
    the USB driver through an 'IoCallDriver()' function. The function
    always returns STATUS_PENDING which seems to be correct but then the
    completion routine never gets called.
    The Completion routine is called as expected on the Rx path.

    I used 'wdmsniff' to trace the packets being sent to the USB device
    and can see that every OUT transfer is followed by a 0-length IN
    transfer on the same endpoint. Is this expected?

    Any suggestions on what might be the problem?

    Thanks,
    - Harshal
     
    Harshal Chhaya, Nov 11, 2004
    #1

    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.
Similar Threads

  1. BindAdapterHandler for WDM/ NDIS protocol driver not called

  2. Irp/Urb Completion Routine Is Called Only Once

  3. Completion routine isn't called when reading from a interrupt pipe

  4. a question about driver completion routine

  5. Ndis Wdm miniport, Halt not called at device removal

  6. Completion routine not called!

  7. Which is the first NDIS routine registered by miniport with NDIS that needs to be called when networ

  8. AddDevice routine is not being called.

Loading...