I need to obtain the identity of the Secondary PCI bus of a PCI bridge on
my PCI board.
When this operation needed to be performed on an NT Legacy driver, the
identity of the Secondary bus was obtained by a call to HalGetBusData
which populated a PCI_COMMON_CONFIG structure.
When I had to do this on a WDM driver, I followed the directions in
Q253232 and used IRP_MN_READ_CONFIG (which I assume populates
PCI_COMMON_CONFIG structure, although I can find no documentation to
indicate this). However, this does not return the secondary bus identity.
Q. How do I obtain the identity of the Secondary Bus?
Clearly the reason that I want to obtain the secondary bus identity is to
know which secondary devices are associated with which primary bus PCI
bridge. This seems to be an area which PnP does not tidily map onto. I
would like to have one device object for my board. However, it appears
that PnP would like me to create a device object for every PCI device that
it finds and I am having difficulty (as above) grouping these devices
together. Can anyone suggest the most appropriate way to handle PCI boards
with a secondary PCI bus (i.e. multiple PCI devices)?
I would be most grateful for any help that anyone can provide.
Thanks,
Richard
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com