From: Jun Sun <jsun@mvista.com>
To: Florian Lohoff <flo@rfc822.org>
Cc: linux-mips@oss.sgi.com, ralf@oss.sgi.com
Subject: Re: NON FPU cpus - way to go
Date: Wed, 07 Feb 2001 11:01:20 -0800 [thread overview]
Message-ID: <3A819B80.7946F866@mvista.com> (raw)
In-Reply-To: 20010207144857.B24485@paradigm.rfc822.org
Florian Lohoff wrote:
>
> Hi,
> i would like to know the way to go for NON-FPU cpus - Currently its
> partly an Compile Time thing and partly run time config.
>
Flo,
My vote is to use config option.
Moving forward I see MIPS mainly used in embedded systems. I think need of
using the same kernel binary for multiple CPUs is rare, especially for the
"same" CPU with or without FPU. Therefore having run-time detection is a
waste of effort. Half-config-half-runtime solution is pretty messy too.
For CPUs with the same PrID that may or may not have a FPU, we can add an
optional FPU selection in the config.in file.
To be complete, I probably would add a check for the existence of FPU, if we
can infer from PrID, when FPU config option is enabled.
Jun
next prev parent reply other threads:[~2001-02-07 19:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-07 13:48 NON FPU cpus - way to go Florian Lohoff
2001-02-07 16:36 ` Maciej W. Rozycki
2001-02-07 16:59 ` Florian Lohoff
2001-02-07 18:19 ` Maciej W. Rozycki
2001-02-07 18:53 ` Alan Cox
2001-02-07 18:53 ` Alan Cox
2001-02-07 19:37 ` Jun Sun
2001-02-07 20:43 ` Joe deBlaquiere
2001-02-08 8:45 ` Geert Uytterhoeven
2001-02-08 10:13 ` Maciej W. Rozycki
2001-02-08 10:52 ` Kevin D. Kissell
2001-02-08 10:52 ` Kevin D. Kissell
2001-02-08 11:19 ` Maciej W. Rozycki
2001-02-08 11:38 ` Kevin D. Kissell
2001-02-08 11:38 ` Kevin D. Kissell
2001-02-08 12:05 ` Maciej W. Rozycki
2001-02-08 10:42 ` Maciej W. Rozycki
2001-02-08 10:53 ` Geert Uytterhoeven
2001-02-08 10:58 ` Alan Cox
2001-02-08 10:58 ` Alan Cox
2001-02-08 11:05 ` Geert Uytterhoeven
2001-02-08 11:22 ` Maciej W. Rozycki
2001-02-07 19:01 ` Jun Sun [this message]
2001-02-07 22:51 ` Kevin D. Kissell
2001-02-07 22:51 ` Kevin D. Kissell
2001-02-08 10:54 ` Maciej W. Rozycki
2001-02-08 10:24 ` Maciej W. Rozycki
2001-09-20 3:13 ` NON FPU cpus (again) Atsushi Nemoto
2001-09-20 3:16 ` Ralf Baechle
2001-09-20 4:02 ` Atsushi Nemoto
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=3A819B80.7946F866@mvista.com \
--to=jsun@mvista.com \
--cc=flo@rfc822.org \
--cc=linux-mips@oss.sgi.com \
--cc=ralf@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.