Our PCI card needs 64MB and asks for it (and gets it) during its PCI config
cycles.
In our Windows 2000 driver :
(1) the IRP_MN_FILTER_RESOURCE_REQUIREMENTS gets invoked and the system
gives us a 64 MB range.
(2) The IRP_MN_START_DEVICE never gets invoked.
(3) The Device Manager reports that “This device cannot find enough free
resources that it can use. (Code 12)”.
Does anybody know of a way to get around this problem?
thanks very much,
meher
>Our PCI card needs 64MB and asks for it (and gets it) during its PCI config
cycles.
In our Windows 2000 driver :
(1) the IRP_MN_FILTER_RESOURCE_REQUIREMENTS gets invoked and the system
gives us a 64 MB range.
(2) The IRP_MN_START_DEVICE never gets invoked.
(3) The Device Manager reports that “This device cannot find enough free
resources that it can use. (Code 12)”.Does anybody know of a way to get around this problem?
Seems like there are video cards with 64MB of memory, I assume these get
fully mapped. As I remember, I’ve seen devices say their used resources are
like 0xC0000000 to 0xCfffffff, which would be 256 MB of mapped space.
Is you device behind a PCI bridge? I’m not sure how W2K handles bridge
programming. Often, bridges get programmed with a window to pass addresses
between the busses, and this window may be rather less than 64 MB. For W2K
to reprogram a bridge may required it to stop and rebalance resources on
other devices.
I’ve also noticed W2K seems to insist PCMCIA mapping windows be below 1 MB,
even on PCI PCMCIA adapters that are fully capable of mapping the whole 64
MB card address space.
Have you experimented with smaller mapping ranges, to find where the
failure boundary is?