From: Jan Damborsky <jan.damborsky@devcom.cz>
To: Dan Malek <dan@embeddededge.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: mpc8241/8245 floating point unit
Date: Thu, 06 Mar 2003 17:59:13 +0100 [thread overview]
Message-ID: <3E677E61.6010801@devcom.cz> (raw)
In-Reply-To: 3E6633D0.8080307@embeddededge.com
>
>
>> Does 8260 really have full FPU support ?.
>
>
> Yes.
>
Thank for this information. It is new for me
and important as well.
We are developing new board with 8260,
but we have thought there is only part of FPU
working properly.
Thanks again, HANYS
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-03-06 16:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00018963.C22236@avantwave.com>
2003-03-04 11:40 ` mpc8241/8245 floating point unit Jerry Van Baren
2003-03-05 11:23 ` Jan Damborsky
2003-03-05 17:28 ` Dan Malek
2003-03-06 16:59 ` Jan Damborsky [this message]
2003-03-06 20:12 ` Dan Malek
[not found] <00019598.C22236@devcom.cz>
2003-03-05 18:12 ` Jerry Van Baren
2003-03-05 18:53 ` Dan Malek
2003-03-04 1:38 Ivan Cheng
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=3E677E61.6010801@devcom.cz \
--to=jan.damborsky@devcom.cz \
--cc=dan@embeddededge.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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).