Hi Nimish: 

We have been using Scientific Linux for a while. It
have been working well so far basically. But we never compiled 8K point
FFT, and we experienced strange behavior at the very beginning. 

cheers


homin jiang of ASIAA 

On Mon, 01 Oct 2012 12:18:21 -0700,
[email protected] wrote: 

> Send casper mailing list
submissions to
> [email protected] [1]
> 
> To subscribe or
unsubscribe via the World Wide Web, visit
>
https://calmail.berkeley.edu/manage/list/listinfo/[email protected]
[2]
> 
> or, via email, send a message with subject or body 'help' to
>
[email protected] [3]
> 
> You can reach the person
managing the list at
> [email protected] [4]
> 
> When
replying, please edit your Subject line so it is more specific
> than
"Re: Contents of casper digest..."
> 
> Today's Topics:
> 
> 1.
Scientific Linux vs CentOS (Nimish Sane)
> 2. Re: Scientific Linux vs
CentOS (Dan Werthimer)
> 
>
----------------------------------------------------------------------
>

> Message: 1
> Date: Mon, 1 Oct 2012 12:11:33 -0400
> From: Nimish Sane

> Subject: [casper] Scientific Linux vs CentOS
> To: casper list 
>
Message-ID:
> 
> Content-Type: text/plain; charset="utf-8"
> 
> Hi
all,
> 
> I have tried to search documentation and email archive without
any
> convincing answer, so my apologies if I am repeating an already
settled
> question.
> 
> We currently use CentOS on our machine that we
use for running CASPER
> toolflow for Roach 2. We are in the process of
procuring a new machine and
> our institute recommends using Scientific
Linux (SL) instead of CentOS. I
> understand that they are clones of RHE
and SL is a closer clone than
> CentOS. I am also told that anything
that runs on CentOS will run on SL.
> 
> I want to know if anyone has
been using the CAPSER toolflow successfully on
> SL or ran into any
problems? We need to make this decision soon and it
> would be very
helpful to know of others' experience.
> 
> Many thanks,
> 
> Nimish
>
-------------- next part --------------
> An HTML attachment scrubbed
and removed.
> HTML attachments are only available in MIME digests.
> 
>
------------------------------
> 
> Message: 2
> Date: Mon, 1 Oct 2012
09:51:23 -0700
> From: Dan Werthimer 
> Subject: Re: [casper] Scientific
Linux vs CentOS
> To: Nimish Sane 
> Cc: casper list 
> Message-ID:
> 
>
Content-Type: text/plain; charset="iso-8859-1"
> 
> hi nimish,
> 
> we
haven't run SL, but we have run into some strange
> problems with linux
operating systems that are not
> supported by xilinx. for instance,
fft's that are longer
> than 8K points don't work correctly on some
non-supported
> operating systems. and you don't get an error message
during compilation
> - you just see flaky results from your fft. when we
contacted xilinx
> about it, they said they wouldn't research our
problem unless we used a
> supported
> operating system. when we
switched to RHEL5, the problem
> went away.
> 
> best wishes,
> 
> dan
>

> On Mon, Oct 1, 2012 at 9:11 AM, Nimish Sane wrote:
> 
>> Hi all, I
have tried to search documentation and email archive without any
convincing answer, so my apologies if I am repeating an already settled
question. We currently use CentOS on our machine that we use for running
CASPER toolflow for Roach 2. We are in the process of procuring a new
machine and our institute recommends using Scientific Linux (SL) instead
of CentOS. I understand that they are clones of RHE and SL is a closer
clone than CentOS. I am also told that anything that runs on CentOS will
run on SL. I want to know if anyone has been using the CAPSER toolflow
successfully on SL or ran into any problems? We need to make this
decision soon and it would be very helpful to know of others'
experience. Many thanks, Nimish
> 
> -------------- next part
--------------
> An HTML attachment scrubbed and removed.
> HTML
attachments are only available in MIME digests.
> 
> End of casper
Digest, Vol 59, Issue 1
> *************************************

 


Links:
------
[1] mailto:[email protected]
[2]
https://calmail.berkeley.edu/manage/list/listinfo/[email protected]
[3]
mailto:[email protected]
[4]
mailto:[email protected]
[5]
mailto:[email protected]
[6] mailto:[email protected]
[7]
mailto:CA+VQD=quheduva8d448jnvebaswjbs_4xcshtsgqcc6dwse...@mail.gmail.com
[8]
mailto:[email protected]
[9] mailto:[email protected]
[10]
mailto:[email protected]
[11]
mailto:CAGHS_vG_qM=dm6p8hxakjsho8p7vuamq7etpnykxabuecqg...@mail.gmail.com
[12]
mailto:[email protected]

Reply via email to