From owner-freebsd-current Thu Apr 24 02:07:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA25589 for current-outgoing; Thu, 24 Apr 1997 02:07:30 -0700 (PDT) Received: from gneiss.eps.nagoya-u.ac.jp (gneiss.eps.nagoya-u.ac.jp [133.6.57.99]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA25581 for ; Thu, 24 Apr 1997 02:07:06 -0700 (PDT) Received: from marble.eps.nagoya-u.ac.jp (localhost [127.0.0.1]) by gneiss.eps.nagoya-u.ac.jp (8.8.5/3.4W4) with ESMTP id RAA03485; Thu, 24 Apr 1997 17:58:29 +0900 (JST) Message-Id: <199704240858.RAA03485@gneiss.eps.nagoya-u.ac.jp> To: rb@gid.co.uk Cc: freebsd-current@freebsd.org Subject: Cyrix DX2/4 In-Reply-To: Your message of "Thu, 24 Apr 1997 08:31:02 +0100" References: X-Mailer: Mew version 1.70 on Emacs 19.28.1 / Mule 2.3 X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 24 Apr 1997 17:58:27 +0900 From: KATO Takenori Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I don't forget PR/3292 :-), and I'm looking for information of Cyrix 486S/DX series CPUs. > The root of this problem appears to be that Cyrix 486 DX DX2 and DX4 (and > some equivalent TI-branded parts) are correctly identified, but are > misclassified as CPU_486DLC where they should be just plain CPU_486. The > following patch fixes the problem: Cyrix/Ti/IBM 486DX2/DX4 have special registers (CCR1, CCR2, CCR3 and SMAR), but they don't have CCR0 (from BIOS Writer's Guide). If neither CYRIX_CACHE_WORKS nor CYRIX_CACHE_REALLY_WORKS is not set, only CCR0 is modified. This operation should not have any effect on DX2 / DX4 because they doesn't have CCR0. Did you get any problem with initcpu.c revision 1.3? If problem still remains, I would summit following idea: init_486dlc() { u_long eflags; u_char ccr0; if ((cyrix_did & 0x00f0) == 0x00) { /* 486 like CPU with 386 like bus. */ ... /* same as revsion 1.3 */ } else { /* 486 like CPU with 486 like bus. */ /* Should I support write-back cache? */ } } I consider that `CPU_486' means Intel's 486, which does not have any special registers, and `CPU_486DLC' means Cyrix's 486, which has special registers. ---- KATO Takenori Dept. Earth Planet. Sci., Nagoya Univ., Nagoya, 464-01, Japan PGP public key: finger kato@eclogite.eps.nagoya-u.ac.jp ------------------- Powered by FreeBSD(98) -------------------