[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: PLX 9050
- To: Mailing List Recipients <pci-sig-request@znyx.com>
- Subject: Re: PLX 9050
- From: "chefren" <chefren@pi.net>
- Date: Wed, 21 May 1997 03:03:10 +0100
- Comments: Authenticated sender is <hagens@[145.220.3.9]>
- In-Reply-To: <13B8053301D40200@smtp.barrsys.com>
- Posted-Date: Wed, 21 May 1997 03:02:43 +0200 (MET DST)
- Priority: normal
- Reply-To: chefren@pi.net
- Resent-Date: Wed, 21 May 1997 03:02:43 +0200 (MET DST)
- Resent-From: pci-sig-request@znyx.com
- Resent-Message-Id: <"EJBFC1.0.kw4.meaWp"@dart>
- Resent-Sender: pci-sig-request@znyx.com
On 20 May 97 at 13:17, Gabe Fitch wrote:
>
> Greetings,
>
> I am looking at using the PLX 9050 to port
> an existing ISA design to PCI for a communications
> card. Does any one have any feedback on the
> use of the PLX 9050? Are you using the PLX now?
> Was it easy to set up, etc? What about PLX in
> general? How much additional logic is necessary?
>
> Has anyone used AMCC as a slave only?
>
> Any input would be appretiated.
>
> Gabe Fitch
> Engineer
> Barr Systems, Inc.
Hello we had about the same idea (2 Mbit ISDN interface) we
opted for a protype based on an industrial IP module with
2Mbit ISDN that could be connected to a 4 IP module to PCI
card from GreenSpring with the PLX 9060.
We need to connect this to an application under
Windows-NT. GreenSpring supplies sample C-code based on
the WinRT devicedriver "kit" from Bluewater Systems that's
also available for the Digital Alpha NT systems we use.
They have just started so unfortunately so there isn't
much more to tell about it.
+++chefren
p.s. Maybe I can tell something else I heard from the
software guys: An installed WinRT kit seems a big hole in
NT-security since basic "hardware security" is moved from
the NT-kernel to the registry. They told me some simple
editing in the registry allows programs to take full
control of the system hardware.
Ž ¸ ¥
- References:
- PLX 9050
- From: Gabe Fitch <gfitch@barrsys.com>