From owner-freebsd-hackers Fri Oct 3 03:45:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA06337 for hackers-outgoing; Fri, 3 Oct 1997 03:45:09 -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.7/8.8.7) with ESMTP id DAA06303; Fri, 3 Oct 1997 03:44:05 -0700 (PDT) Received: from marble.eps.nagoya-u.ac.jp (localhost [127.0.0.1]) by gneiss.eps.nagoya-u.ac.jp (8.8.7/3.4W4) with ESMTP id TAA05088; Fri, 3 Oct 1997 19:43:45 +0900 (JST) Message-Id: <199710031043.TAA05088@gneiss.eps.nagoya-u.ac.jp> To: asami@cs.berkeley.edu Cc: jkh@time.cdrom.com, bde@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Ever looked at this page? From: KATO Takenori In-Reply-To: Your message of "Fri, 3 Oct 1997 01:54:11 -0700 (PDT)" References: <199710030854.BAA13885@silvia.HIP.Berkeley.EDU> 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: Fri, 03 Oct 1997 19:43:45 +0900 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I don't subscribe hackers@freebsd.org, so please CC'ed to me if you consider I should read your follow-ups. > * http://wauug.erols.com/~balsa/linux/cyrix/ > * > * Looks like it might be interesting for Cyrix users. > > Didn't Kato-san already do this stuff a while ago? Yes, I did. But, I would like to know whether FreeBSD can recognize Cyrix 6x86MX cpu. If there is any problem, I will try to fix. Kernel configuration options of FreeBSD (c.f. LINT) and Linux-patch are as follows: FreeBSD Linux ------------------------------------------------------------------ (5x86 options) CPU_BTB_EN (1) N.A. (5) CPU_DISABLE_5X86_LSSER N.A. (5) CPU_FASTER_5X86_FPU N.A. (5) CPU_RSTK_EN (1) N.A. (5) (6x86 option) CPU_CACHE_REASLLY_WORKS N.A. N.A. (2) CONFIG_CYRIX_6X86_NOLOCK N.A. (2) CONFIG_CYRIX_6X86_WTALLOC N.A. (2) CONFIG_CYRIX_6X86_BTB N.A. (2) CONFIG_CYRIX_6X86_BTB_RISKEY N.A. (3) CONFIG_CYRIX_6X86_VSPM N.A. (3) CONFIG_CYRIX_6X86_VSPM_NOTRADPAGE (both 5x86 and 6x86 options) CPU_SUSP_HLT CONFIG_CYRIX_SUSP_HLT CPU_IORT (4) CYRIX_FAST_IO (6) ------------------------------------------------------------------ N.A.: not available. Note: (1) Should not be used because of CPU bug. (2) I consider they should be controled by BIOS. (3) I don't know how to implement these options without problem. (4) Should not used on Cyrix 5x86 box. Default is fasttest (no clock delay). Because of cpu bug, IORT of Cyrix 5x86 should be 0. (5) Linux-patch does not have any problem about these options. (6) Linux-patch modifies IORT only when this option is set. Unsafe! IORT should be 0 if CPU is Cyrix 5x86. If IORT is not 0, system automagically becomes unstable. PS: Linux-patch might recognize IBM BlueLightning CPU as Cyrix 486. (I'm not tested.) Of course, FreeBSD can recoginize it correctly. PPS: There are many CPU related initialization routines in /sys/i386/i386/initcpu.c. If we should add new feature, it is not so difficult. ---- 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) -------------------