Article View: comp.os.msdos.programmer
Article #173386 SX Identification
From: aki
Date: Sat, 01 Aug 1992 01:42
Date: Sat, 01 Aug 1992 01:42
25 lines
1418 bytes
1418 bytes
I posted a question regarding the identification of a 386SX CPU versus a 386DX a couple of weeks ago. I finally talked to one of the designers and found that the hardest way is the only way: 1. Time a bunch of NOP's (don't loop'em) 2. Time a bunch of DWORD memory accesses (don't loop) The 386SX has a 2 clock penalty for DWORD moves (naturally, since the CPU has to move 2 words) versus the 386 which has no penalty. The default timing for a MOV [MEM], REG is 2 clocks, thus an SX should work about 4 times longer on the MOV's than on the NOP's. Of course timing should be done with the 8253 clock 2 and INT's should be disabled. This is only theory and I still need to put it to work. Unfortunately I can't release the code, 'cause it goes to commercial purposes. I hope this helps some of you who asked me for the solution in case I found one. Aki. -- / Phone: 408-662 9664 Fax: 662 9676 | "Aki" pronounced: Ah-Key. I know \ \ 125 Searidge Ct #D, Aptos, CA 95003 | what I'm doing most of the time. /
Technical Details
Message-ID:
<3981@cruzio.santa-cruz.ca.us>Path:
arc1-ca.pugleaf.net!sparky!uunet!sun-barr!olivea!decwrl!csus.edu!netcomsv!cruzio!akiShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!sun-barr!olivea!decwrl!csus.edu!netcomsv!cruzio!aki From: aki@cruzio.santa-cruz.ca.us Newsgroups: comp.os.msdos.programmer Subject: 386 SX Identification Keywords: 386 SX ID Solved Message-ID: <3981@cruzio.santa-cruz.ca.us> Date: 1 Aug 92 01:42:46 GMT Sender: aki@cruzio.santa-cruz.ca.us Reply-To: aki@cruzio.santa-cruz.ca.us Lines: 25