|
Message
From: Brian Korsedal<BKorsedal@b...>
Date: Tue Aug 10 19:32:55 CEST 2004
Subject: [openrisc] FPGA compile server wanted
Hi,here is a copy of a message I just sent out to a bunch of vendors. I dawned on me that many of you might know about this also. Here is a copy of what I sent out, if you do any of this or know someone who does, let me know. " Hi,
We want to setup a server on our network to rum some specific tasks. We want to run Matlab 7.0 with simulink, Synplify Pro, Xilinx ISE (any version) and Modelsim all on the same server. We want to use a two processor server with 4Gig of ram running Linux. I think we will use Redhat RHEL 3.0. It would be nice if we could take advantage of the AMD64 architecture, but I doubt that all the software will support it. Also, it would be nice if there is good support for the 2.6 kernel.
I would like your help in deciding what server to buy and how to set it up. We need to know in great detail what is required to support your software and what to look out for. If the support is not very good for our proposed architecture, tell us what is well supported. We would like to squeeze the most performance out of this server, but we do not want to be beta testers for semi-supported software. We really need bug free operation.
It would be real nice if we could find someone in San Diego who has experience setting up enviroments like this. If we can't find this, then maybe a company that has experince setting up these enviroments that can ship us a unit ready to go. We are open to suggestions and I would really like feedback so that we can make a good choice.
If it helps, we tend to compile large Xilinx FPGA designs. We write our designs in a mix of VHDL code and Sysgen auto compiled code (Sysgen is Xilinx software which operates inside of simulink). Sysgen creates VHDL code, so all of our designs will be in VHDL. We usually use Xilinx FPGA's rated between 2 million and 4 million gates (XC2VP20, XC2VP40, XC3S2000, XC3S4000). Our designs usually operate at between 60 and 120 MHz.
Thank you,
Brian "
|
 |