Email or username:

Password:

Forgot your password?
Top-level
Ken Shirriff

The chip I photographed is the i486 SX, which is the version of the 486 without a floating point unit. But you can see from the photo that it has a floating point unit on the die. It's unclear if Intel deliberately disabled the floating point unit to segment the market between the low-end SX and the high-end DX, or if chips with an FPU fault were sold as the SX.

13 comments
Ken Shirriff

One of the engineers on the 486 was Pat Gelsinger, who is now CEO of Intel. You can see his initials on the die.

Ken Shirriff

The 486 processor uses microcode. Here's a closeup of the microcode ROM; you can see the bits.

[DATA EXPUNGED]
Ken Shirriff

@awoodland The Pentium Pro was the first x86 processor with microcode that could be updated. Intel originally implemented that for testing purposes, but realized after the expensive Pentium FDIV bug that microcode updates were an important feature.

Darryl Ramm

@kenshirriff I remember some beyond useless support person at Intel telling us at VMware that the Pentium did not use microcode when we were trying to find out about a bug that appeared to have a microcode fix that some but not all OEMs had released. OK well we've reversed engineered part of the update for the microcode your processors don't have, so maybe we could talk to somebody more senior?... (eventually got to senior engineering folks who were helpful)

Ken Shirriff

Here's the 486 chip copyright, above a block of circuitry that holds the cache tags.

Ken Shirriff

A closeup of the edge of the 486 showing bond pads with bond wires attached. Note the complex I/O driver block next to each bond pad. The pads in the center (without drivers) are two of the power and ground supplies. Note the thick vertical lines distributing power/ground to the chip.

Ken Shirriff

Here's a Google Drive link to a higher resolution version: drive.google.com/file/d/1nQMtD
(I posted on Mastodon, but the resolution got crunched.)

Ken Shirriff

@gsuberland It was supposed to be 7155x10870 :(
I edited the post to add a Google Drive link; hopefully that's better.

Graham Spookyland🎃/Polynomial

@kenshirriff ah yeah your server will have resized it then. weird final resolution though, I guess it limited based on compressed JPEG size?

`Da Elf

@kenshirriff @drwho
I miss my 486DX/4 120 (94 ish?). VLB SCSI and video. Ran SCO Enterprise real good.

Go Up