From: Grant Likely <grant.likely@secretlab.ca>
To: Shanyuan Gao <sygao.research@gmail.com>
Cc: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: Back port Virtex5 FPU to Virtex4?
Date: Wed, 17 Sep 2008 10:35:55 -0700 [thread overview]
Message-ID: <20080917173555.GA7913@secretlab.ca> (raw)
In-Reply-To: <3C87E4F8-3DA2-41E8-BE33-979A7869FD2D@gmail.com>
On Tue, Aug 26, 2008 at 04:00:42PM -0400, Shanyuan Gao wrote:
> I am working with ML410 and have FPU (single precision) working.
> However, the FPU for V5 looks more attractive because it's double
> precision. So is it possible to back port the double precision FPU to
> V4?
As far as I understand there are limitations in the V4 APU interface
that makes the full double precision FPU unfeasible. The Xilinx folks
can correct me if I'm wrong.
g.
next prev parent reply other threads:[~2008-09-17 17:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-26 20:00 Back port Virtex5 FPU to Virtex4? Shanyuan Gao
2008-09-17 17:35 ` Grant Likely [this message]
2008-09-17 18:03 ` Stephen Neuendorffer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080917173555.GA7913@secretlab.ca \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-embedded@ozlabs.org \
--cc=sygao.research@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).