Hi Gabor,
Gabor Kerenyi wrote:
> [email protected] wrote:
> > As I remember the serial eeprom from which the PLX-9050 is
> > configured needs to be programmed differently according to
> > the type of interrupt.
>
> I think the device is configured properly because a windows
> driver exists and it's working correctly. But what do I have
> to do on the driver side according to the type of the interrupt?
> Is there any difference from the driver's point of view?
I was thinking about driver programming of a device on the board that sends
interrupt requests to the PLX-9050. I got bit by a UART that powered on to
an
interrupt signaling mode that caused the 9050 to continuously assert an
interrupt request on the PCI bus. This was not a 9050 setup issue. I hope
that your board does not have any issues like that.
> > But more important, I do not believe your company wants to
> > use the 9050 in a cPCI system. This chip does not support
> > hot swappability. I believe there is an almost identical part,
> > the PLX 9051 (or perhaps the 9052) that does. You might have
> > the hardware engineer check the issue out.
>
> The company uses the 9050 in a C-PCI system. The card is designed
> in 98 or 99.
When we updated our 9050 based card for hot-swap, we selected the PLX-9030
which is a compatible, but newer, part. It incorporates all of the CPCI
hot-swap infrastructure, even small stuff like ejector switch debouncing.
Regards,
Ed
----------------------------------------------------------------
Ed Vance [email protected]
Macrolink, Inc. 1500 N. Kellogg Dr Anaheim, CA 92807
----------------------------------------------------------------