Help in NDIS Driver
- From: Kans <rkappan@xxxxxxxxx>
- Date: Mon, 22 Oct 2007 11:04:39 -0000
Hello,
I am writing virtual network i/f driver for a PCI card.
This driver also requires a IOCTL dispatch routine for few device
control those are not related to network subsystem.
I am using NdisMRegisterDevice() to register the IRP interfaces for
IRP_MJ_XXX.
The IOCTL routines used to read / write data from / to the PCI card
if device buffers are available. Otherwise, I am marking those IRPs
as pending, and set a completion routine for the IRP.
Once the device frees the memory, it will notify through an Interrupt,
where I am calling the IoCompleteRequest for any pending IRPs.
The system gives panic at this point(after IoCompleteRequest). The
failing module is noted as NT (from WinDBG).
I believe it may be due to the reason that the PDEVICE_OBJECT is not
proper, as, while
trying to access the device extension through PDEVICE_OBJECT parameter
of the IOCTL handler, the device extension's address was different
from the one I have allocated.
can anyone throw some pointers on this issue.
also are there any mechanisms if i write a wdm driver, how can I
communicate to NDIS ?
--
kans.
.
- Follow-Ups:
- Re: Help in NDIS Driver
- From: Stephan Wolf [MVP]
- Re: Help in NDIS Driver
- Prev by Date: KsPinGetLeadingEdgeStreamPointer returns NULL
- Next by Date: Re: Accessing disabled SCSI devices via Storport
- Previous by thread: KsPinGetLeadingEdgeStreamPointer returns NULL
- Next by thread: Re: Help in NDIS Driver
- Index(es):
Relevant Pages
|
