From: grundler@dsl2.external.hp.com (Grant Grundler)
To: Randolph Chung <randolph@tausq.org>
Cc: Jim Hull <jim.hull@hp.com>,
'John David Anglin' <dave@hiauly1.hia.nrc.ca>,
parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] Re: floating point exception error
Date: Sat, 11 Jan 2003 00:10:05 -0700 [thread overview]
Message-ID: <20030111071005.GA2326@dsl2.external.hp.com> (raw)
In-Reply-To: <20030111061638.GH31470@tausq.org>
On Fri, Jan 10, 2003 at 10:16:38PM -0800, Randolph Chung wrote:
> so, i wonder:
> 1) why those numbers? (where is it documented?)
no clue - PDC calls don't document that?
> 2) is there a special way to read that fpu type from the fpu?
yes. PDC can tell you the FPU model. I'll have to look up the call.
I had the impression it was better to use FP info to identify the CPU model
than the other PDC info - but what we have seems to work.
> or do we use boot_cpu_data.cpu_type?
Maybe the same call returns both CPU and FPU identifiers.
Don't recall offhand. If someone doesn't know offhand,
I'll look it up.
grant
next prev parent reply other threads:[~2003-01-11 7:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-11 21:13 [parisc-linux] ["CSA Test Drive" <TestDrive@compaq.com>] FW: Some issues Bdale Garbee
2002-12-11 22:03 ` John David Anglin
2002-12-11 22:44 ` Carlos O'Donell
2002-12-11 23:05 ` John David Anglin
2002-12-11 23:17 ` Carlos O'Donell
2002-12-12 6:50 ` Randolph Chung
2002-12-12 12:15 ` Matthew Wilcox
2003-01-10 7:54 ` [parisc-linux] Re: floating point exception error Randolph Chung
2003-01-10 18:08 ` Jim Hull
2003-01-10 18:35 ` Randolph Chung
2003-01-10 18:48 ` John David Anglin
2003-01-10 22:30 ` Jim Hull
2003-01-11 6:16 ` Randolph Chung
2003-01-11 7:10 ` Grant Grundler [this message]
2003-01-11 18:31 ` John David Anglin
2003-01-12 8:37 ` Randolph Chung
2003-01-13 15:58 ` jsoe0708
2003-01-13 16:57 ` Randolph Chung
2003-01-13 17:16 ` jsoe0708
2003-01-13 17:16 ` Randolph Chung
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=20030111071005.GA2326@dsl2.external.hp.com \
--to=grundler@dsl2.external.hp.com \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=jim.hull@hp.com \
--cc=parisc-linux@parisc-linux.org \
--cc=randolph@tausq.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