From: Grant Grundler <grundler@cup.hp.com>
To: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] commit FP coproc enable code?
Date: Fri, 01 Oct 1999 13:52:53 -0700 [thread overview]
Message-ID: <199910012052.NAA13364@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Fri, 01 Oct 1999 20:56:25 PDT." <19991001205625.J16533@suse.de>
Philipp Rumpf wrote:
> > o FP enable via writing cr10 (CCR) register. Not doing this the "right"
> > way - which is to use PDC_COPROC but it will work for all PA1.1
> > platforms.
>
> 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.
>
> > ===================================================================
> > RCS file: /home/cvs/parisc/linux/arch/parisc/kernel/head.S,v
> > retrieving revision 1.32
> > diff -u -r1.32 head.S
> > --- head.S 1999/08/31 19:25:23 1.32
> > +++ head.S 1999/09/30 22:43:03
>
> I would prefer to do this somewhere after the kernel is loaded, in C,
> surrounded
> by a pair of printks, so we know whether it is this that hangs the machine.
Agreed...I'll do that....thanks!
grant
Grant Grundler
Communications Infrastructure Computer Operations
+1.408.447.7253
next prev parent reply other threads:[~1999-10-01 20: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 [this message]
1999-10-02 6:03 ` Jeffrey A Law
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=199910012052.NAA13364@milano.cup.hp.com \
--to=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