[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
cpu model code (fwd)
- Date: Mon, 2 Aug 1999 13:11:45 -0500 (CDT)
- From: joel at OARcorp.com (joel at OARcorp.com)
- Subject: cpu model code (fwd)
If someone knows of an independently and actively maintained cpuModel
determination routine, it would be nice to know about it. It would
certainly let someone else keep up with the awful pace of change. :)
This is the email which triggered this chain of thought.
---------- Forwarded message ----------
Date: Thu, 29 Jul 1999 10:41:46 -0700
From: D. V. Henkel-Wallace <gumby at zembu.com>
To: joel at oarcorp.com
Subject: Re: pc386 on 386sx
At 09:58 29-07-99 -0500, joel at oarcorp.com wrote:
>On Wed, 28 Jul 1999, erik.ivanenko wrote:
>The assumption behind fninit being used there is based on the circa 1986
>version of the original 80386 manual (before it was even a DX). It is
>quite likely given the haphazard way in which the x86 architecture has
>evolved, that the assumption made that fninit (no-wait version) would be
>safe to use when there was not a coprocessor is a bogus one.
I suspect that there's somebody on the net who maintains a bit of code that
will identify _any_ x86 version, variant, or clone (in excruciating
detail). The van Gilluwe book has such code in it, but of course it gets
out of date quickly.
Perhaps it would be easiest just to look on likely places like x86.org and
just use whatever conventions are already available, just as RTEMS includes
and tracks newlib and now the BSD stack.
Then of course we can argue about how to use the options, whatever they are.