home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.ibm.pc.hardware:23885 comp.arch:9329
- Path: sparky!uunet!usc!rpi!crdgw1!rdsunx.crd.ge.com!ariel!davidsen
- From: davidsen@ariel.crd.GE.COM (william E Davidsen)
- Newsgroups: comp.sys.ibm.pc.hardware,comp.arch
- Subject: Re: Does a 487sx shut down the 486sx??
- Message-ID: <1992Sep10.134414.1607@crd.ge.com>
- Date: 10 Sep 92 13:44:14 GMT
- References: <1992Aug26.173519.22421@unislc.uucp> <1992Aug27.183804.8605@tandon.com> <GLEW.92Sep9195211@pdx007.intel.com>
- Sender: usenet@crd.ge.com (Required for NNTP)
- Reply-To: davidsen@crd.ge.com (bill davidsen)
- Organization: GE Corporate R&D Center, Schenectady NY
- Lines: 25
- Nntp-Posting-Host: ariel.crd.ge.com
-
- In article <GLEW.92Sep9195211@pdx007.intel.com>, glew@pdx007.intel.com (Andy Glew) writes:
-
- | I am not 100% certain, but I am reasonably sure that the original
- | i486sx was *not* a CPU that passed integer tests but failed FP tests.
- |
- | The present i486sx, of course, doesn't need to pass FP tests because
- | it has no FP on chip.
- |
- | There would be far too much risk involved in chips that failed any
- | part of their functionality tests. Imagine that FP tests failed
- | because of an intermittent short in the FP side - a short that would
- | eventually close, even with integer only use...
-
- This brings up a good technical point, how do you properly test a chip
- with a castrated FPU? If you test with the FPU enabled and then disable
- it you might cause a problem in the disable process (unless you do it by
- mounting with a pin tied high of some such). If you disable and then
- test, you might miss a problem such as you describe above.
-
- If you test before and after the cost of manufacture goes up on the
- chip you seel for less (that wouldn't astonish me from intel).
-
- --
- bill davidsen, GE Corp. R&D Center; Box 8; Schenectady NY 12345
- I admit that when I was in school I wrote COBOL. But I didn't compile.
-