From: Jeffrey A Law <law@cygnus.com>
To: Grant Grundler <grundler@cup.hp.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] commit FP coproc enable code?
Date: Sat, 02 Oct 1999 00:03:57 -0600 [thread overview]
Message-ID: <24837.938844237@upchuck.cygnus.com> (raw)
In-Reply-To: Your message of Fri, 01 Oct 1999 13:52:53 PDT. <199910012052.NAA13364@milano.cup.hp.com>
In message <199910012052.NAA13364@milano.cup.hp.com>you write:
> > Why is not using PDC_COPROC not the right way ?
> > It should do exactly the same
> > thing, modulo machines without FPU (for which we do not provide emulation
> > anyway) and firmware bugs ...
>
> You are right.
> But I'm lazy and I don't care right now about machines older than PA 1.1.
> Someone who cares about PA 1.0 can implement that.
I would recommend ignoring PA1.0 -- the only machines with PA1.0 processors
are radically different than the machines y'all are targeting. The effort
would be spent on PA2.0 :-)
jeff
prev parent reply other threads:[~1999-10-02 6:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-01 19:12 [parisc-linux] [grundler@puffin.external.hp.com: commit FP coproc enable code?] Phil Schwan
1999-10-01 18:56 ` [parisc-linux] commit FP coproc enable code? Philipp Rumpf
1999-10-01 20:52 ` Grant Grundler
1999-10-02 6:03 ` Jeffrey A Law [this message]
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=24837.938844237@upchuck.cygnus.com \
--to=law@cygnus.com \
--cc=grundler@cup.hp.com \
--cc=parisc-linux@thepuffingroup.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