home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.os2.advocacy
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!howland.reston.ans.net!spool.mu.edu!torn!watserv2.uwaterloo.ca!watserv1!wes.on.ca!tomh
- From: tomh@wes.on.ca (Tom Haapanen)
- Subject: Re: The Cyrix Issue...
- Organization: Waterloo Engineering Software
- Date: Tue, 12 Jan 1993 22:49:31 GMT
- Message-ID: <1993Jan12.224931.26050@wes.on.ca>
- References: <1993Jan10.233443.7189@gw.wmich.edu> <1993Jan11.134151.12062@wam.umd.edu> <1993Jan11.224549.7206@gw.wmich.edu>
- Lines: 17
-
- 177wardell@gw.wmich.edu writes:
- > I still stand by my original post (except I agree, it is a 1K
- > cache, not 2K). I have read over and over again that Cyrix's 486SLC is
- > only called a 486 for marketting reasons and that it is still basically
- > a 386sx (16bit bus, 24bit address, tec) with a few added instructions.
-
- For what it's worth, a 486 is basically a faster 386 with a cache, a
- built-in coprocessor and a few added instructions. A 486SX? It's a
- faster 386 with a few added instructions.
-
- Hey, isn't that what the 486DLC is, too? (The speed argument is left to
- the reader...) In any case, the 486SLC and 486DLC do implement the entire
- 486 instruction set. So there.
-
- [ \tom haapanen "i don't even know what street canada is on" -- al capone ]
- [ tomh@wes.on.ca "trust the programmer" -- ansi c standard ]
- [ waterloo engineering software "to thine own self be true" -- polonius ]
-