The main issue with cPCI is that you usually have an additional PCI-PCI
bridge before your cPCI bus devices. The PMC will usually add an additional
bridge. If your device or driver is sensitive to the additional bridging
(and I don’t recall all of the ramifications) this may be part of your
problem. I understand that the device and driver functioned normally under
NT4, but was that on a cPCI system with NT4? There may be some issues with
W2K regarding the additional bridge programming/mapping that exposes the
sensitivities in your device. This is just a guess. The only cPCI driver
work I have done is under Windows CE, not NT/W2K.
Greg
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Gary Little
Sent: Tuesday, January 23, 2001 9:57 AM
To: NT Developers Interest List
Subject: [ntdev] Re: [NTDEV] Legacy drivers, 2000, and a Compact PCIMiguel,
Primarily the NT4 version of the driver installed on 2000 is a
stop-gap, to
simply provide a driver for the hardware until the 2000 driver has been
completed. This driver does work, and works within specs, on other 2000
platforms, it is not working on the Compact PCI with a PMC bus mastering
card on a Compact PCI carrier. My gut feeling is that you are right – a
PnP driver that properly dances with the PnP manager will most likely be
alright. But it sure would be nice to feel warm and fuzzy that this is
indeed the case before I go committing such to the customer.The question, restated, is “Are there any known problems using bus
mastering, PMC boards in CPCI carriers on CPCI systems running
Windows 2000,
SP1?”.
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