From owner-freebsd-questions  Wed May 29 19:43:48 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id TAA18558
          for questions-outgoing; Wed, 29 May 1996 19:43:48 -0700 (PDT)
Received: from aeffle.Stanford.EDU (sequence.Stanford.EDU [171.65.76.7])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id TAA18469
          for <freebsd-questions@freebsd.org>; Wed, 29 May 1996 19:43:19 -0700 (PDT)
Received: by aeffle.Stanford.EDU; id AA18319; Wed, 29 May 1996 19:43:01 -0700
Date: Wed, 29 May 1996 19:43:00 -0700 (PDT)
From: Howard Lew <hlew@sequence.Stanford.EDU>
To: Brandon Gillespie <brandon@tombstone.sunrem.com>
Cc: freebsd-questions@freebsd.org
Subject: Re: [Cyrix chip] panic in FreeBSD-STABLE kernel..
In-Reply-To: <199605292028.OAA19802@tombstone.sunrem.com>
Message-Id: <Pine.OSF.3.91.960529193747.24515A-100000@aeffle.Stanford.EDU>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Wed, 29 May 1996, Brandon Gillespie wrote:

> I put back in the i486_CPU line and it works fine, seems the Cyrix reports
> itself as a 486 (I now recall a conversation in respect to this already).
> 
> What is involved in the 586 support?  Am I loosing on anything significant
> by registering it as a 486?  How would I go about getting it to register
> as a 586 (or even better a 686)
> 
> Enjoy;
> 
> -Brandon
> 

I am pretty sure there is a way to properly ID it, but I guess no one has
had the time to do so.  Cyrix should probably come out with some source
code to properly do that for their cpus.  I remember the NexGen folks
provided some source code to do that for their Nx586s. 

Hmmm.... I wonder what the AMD K5's which are finally out will ID as...