From owner-freebsd-hardware Thu Jun 20 09:10:26 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA21833 for hardware-outgoing; Thu, 20 Jun 1996 09:10:26 -0700 (PDT) Received: from portal.spi.net ([199.238.225.153]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA21827 for ; Thu, 20 Jun 1996 09:10:25 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@MindBender.HeadCandy.com [199.238.225.168]) by portal.spi.net (8.6.12/8.6.9) with ESMTP id JAA00314; Thu, 20 Jun 1996 09:10:13 -0700 Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.6.9) with SMTP id JAA28073; Thu, 20 Jun 1996 09:10:11 -0700 (PDT) Message-Id: <199606201610.JAA28073@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: "Andrew V. Stesin" cc: dutchman@spase.nl (Kees Jan Koster), hardware@freebsd.org Subject: Re: AMD 586 in P24T slot? -- No, P24"D" one In-reply-to: Your message of Thu, 20 Jun 96 14:35:45 +0300. <199606201135.OAA13309@office.elvisti.kiev.ua> Date: Thu, 20 Jun 1996 09:10:04 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ># > Try another CPU -- Intel or AMD (AMD 5x86 strongly recommended, ># > in case your motherboard supports it. If it doesn't, you ># > may try jumper settings for Intel P24D -- theyr'e Ok ># > for AMD 133 too) ># Ummmm. Now this sounds interesting. I lived under the assumption that I ># needed a special mainboard to sport an AMD 133. > You wasn't 100% correct. As about recent 486 boards, > they usually have AMD 133 explicitly listed in jumper > setting sheets. As about older ones, the things aren't > so simple -- you might be lucky with a guessed probability > of above 80%. To be more precise, the 5x86 is just a marketing name. It's really a 486DX4. The two things that make it different from "traditional" 486s are that it has 16K write-back cache (most 486s have 8K write-through cache; but even Intel makes their 486DX4s with 16K write-back cache these days), and it runs at a faster clock than any other "486" (AMD stops their 486DX4 line at 120MHz, and calls the chips above that 5x86, even though they're identical except for the clock speed [486DX4/100 is 3x33.3MHz, 486DX4/120 is 3x40MHz, and 5x86/133 is 4x33.3MHz]). > For a pity, attempts to use 5x133 in older boards might > cause the nessesity of motherboard's BIOS firmware upgrade :( My BIOS doesn't even know what a DX4 is, but my 5x86 is still working OK. The only thing is that it runs in write-through mode instead of write-back. But my L2 cache is write-back, so it's not a huge penalty. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@HeadCandy.com --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... Roll your own Internet access -- Seattle People's Internet cooperative. If you're in the Seattle area, ask me how. -----------------------------------------------------------------------------