Re: NDIS WDM driver installation for multi-port NIC

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Am I correct in undersstanding that in my case, because I've created a PDO
for the port from the c5ebus driver, the miniport can use the PDO to retrieve
the bus driver's FDO and send IRPs to that device object?


No, there is no system provided way to get the parent's FDO. You can devise your own interface to do that.

Does this also mean that when the miniport is not installed as a filter
driver but as a function driver, that any interfaces that the c5ebus
registers is now accessible once again by a user application since the c5ebus
driver is once again at the top of the device stack?


Correct.

.

Relevant Pages

  • Re: [PATCH] Intel Management Engine Interface
    ... new file mode 100644 ... * Number of queue lists used by this driver ... * @dev: Device object for our driver ...
    (Linux-Kernel)
  • Bug Check 0x7B: INACCESSIBLE_BOOT_DEVICE with /nolowmem.
    ... We are planning to test our DMA based driver under 64-Bit environment. ... on x86 systems the boot.ini file must be edited or on ARC ... is the actual length of the Unicode string, ... If the argument is a pointer to a device object, then the format of the first ...
    (microsoft.public.development.device.drivers)
  • Re: Infamous BSOD Stop 7B Error
    ... SATA drives should work with XPe. ... Debugger and got some more info. ... Driver Library which requires the user to do a custom install. ... If the argument is a pointer to a device object, ...
    (microsoft.public.windowsxp.embedded)
  • Infamous BSOD Stop 7B Error
    ... relentless to boot from an AHCI enabled drive. ... Debugger and got some more info. ... Driver Library which requires the user to do a custom install. ... If the argument is a pointer to a device object, ...
    (microsoft.public.windowsxp.embedded)
  • Re: Power callbacks
    ... driver calls the AV mini-driver power callback on the way down for the D ... Device Object Extension: 8f579eb0: ...
    (microsoft.public.development.device.drivers)