Slashdot Mirror


Microchips That Shook the World

wjousts writes "IEEE Spectrum has an interesting article on '25 Microchips That Shook the World,' including such classics as the Signetics NE555 Timer, MOS Technology 6502 Microprocessor (Apple II, Commodore PET and the brain of Bender) and the Intel 8088 Microprocessor. Quoting: 'Among the many great chips that have emerged from fabs during the half-century reign of the integrated circuit, a small group stands out. Their designs proved so cutting-edge, so out of the box, so ahead of their time, that we are left groping for more technology clichés to describe them. Suffice it to say that they gave us the technology that made our brief, otherwise tedious existence in this universe worth living.'"

185 comments

  1. Print Link, The 25 in a list by Anonymous Coward · · Score: 5, Informative

    PRINT ARTICLE (instead of the 5 separate pages):
    http://spectrum.ieee.org/print/8747

    The 25:
    1 - Signetics NE555 Timer (1971)
    2 - Texas Instruments TMC0281 Speech Synthesizer (1978)
    3 - MOS Technology 6502 Microprocessor (1975)
    4 - Texas Instruments TMS32010 Digital Signal Processor (1983)
    5 - Microchip Technology PIC 16C84 Microcontroller (1993)
    6 - Fairchild Semiconductor A741 Op-Amp (1968)
    7 - Intersil ICL8038 Waveform Generator (circa 1983*)
    8 - Western Digital WD1402A UART (1971)
    9 - Acorn Computers ARM1 Processor (1985)
    10 - Kodak KAF-1300 Image Sensor (1986)
    11 - IBM Deep Blue 2 Chess Chip (1997)
    12 - Transmeta Corp. Crusoe Processor (2000)
    13 - Texas Instruments Digital Micromirror Device (1987)
    14 - Intel 8088 Microprocessor (1979)
    15 - Micronas Semiconductor MAS3507 MP3 Decoder (1997)
    16 - Mostek MK4096 4-Kilobit DRAM (1973)
    17 - Xilinx XC2064 FPGA (1985)
    18 - Zilog Z80 Microprocessor (1976)
    19 - Sun Microsystems SPARC Processor (1987)
    20 - Tripath Technology TA2020 AudioAmplifier (1998)
    21 - Amati Communications Overture ADSL Chip Set (1994)
    22 - Motorola MC68000 Microprocessor (1979)
    23 - Chips & Technologies AT Chip Set (1985)
    24 - Computer Cowboys Sh-Boom Processor (1988)
    25 - Toshiba NAND Flash Memory (1989)

    ( mod me up so some karmawhore will find themselves FAIL'd )

    1. Re:Print Link, The 25 in a list by Jeff+DeMaagd · · Score: 3, Insightful

      Five pages really isn't bad though, there's a lot of reading per page, whereas a typical site might have one page or more for the explanation as to why each chip was considered significant.

      Also, just listing the "winners" doesn't do justice to the article.

    2. Re:Print Link, The 25 in a list by Anonymous Coward · · Score: 0

      I think they forgot something, not just a chip but a whole series... the 74XX TTLs.

    3. Re:Print Link, The 25 in a list by mustafap · · Score: 1

      Power hog! That should be 40XX

      --
      Open Source Drum Kit, LPLC deve board - mjhdesigns.com
    4. Re:Print Link, The 25 in a list by Anonymous Coward · · Score: 1, Informative

      PRINT ARTICLE (instead of the 5 separate pages):
      http://spectrum.ieee.org/print/8747

      The 25:
      1 - Signetics NE555 Timer (1971)
      2 - Texas Instruments TMC0281 Speech Synthesizer (1978)
      3 - MOS Technology 6502 Microprocessor (1975)
      4 - Texas Instruments TMS32010 Digital Signal Processor (1983)
      5 - Microchip Technology PIC 16C84 Microcontroller (1993)
      6 - Fairchild Semiconductor A741 Op-Amp (1968)
      7 - Intersil ICL8038 Waveform Generator (circa 1983*)
      8 - Western Digital WD1402A UART (1971)
      9 - Acorn Computers ARM1 Processor (1985)
      10 - Kodak KAF-1300 Image Sensor (1986)
      11 - IBM Deep Blue 2 Chess Chip (1997)
      12 - Transmeta Corp. Crusoe Processor (2000)
      13 - Texas Instruments Digital Micromirror Device (1987)
      14 - Intel 8088 Microprocessor (1979)
      15 - Micronas Semiconductor MAS3507 MP3 Decoder (1997)
      16 - Mostek MK4096 4-Kilobit DRAM (1973)
      17 - Xilinx XC2064 FPGA (1985)
      18 - Zilog Z80 Microprocessor (1976)
      19 - Sun Microsystems SPARC Processor (1987)
      20 - Tripath Technology TA2020 AudioAmplifier (1998)
      21 - Amati Communications Overture ADSL Chip Set (1994)
      22 - Motorola MC68000 Microprocessor (1979)
      23 - Chips & Technologies AT Chip Set (1985)
      24 - Computer Cowboys Sh-Boom Processor (1988)
      25 - Toshiba NAND Flash Memory (1989)

      ( mod me up so some karmawhore will find themselves FAIL'd )

      What about the IBM Cell Processor (2005). Bringing peta-flops to Folding@Home certain qualifies as an amazing contribution, even if the PS3 itself hasn't ruled the console market.

    5. Re:Print Link, The 25 in a list by jo42 · · Score: 4, Interesting

      They completely missed the 74XX series of chips. So much stuff was built with them back in the day...

    6. Re:Print Link, The 25 in a list by drissel · · Score: 1

      For this software guy, my two biggest were the Intel 8251 and the first Western Digital winchester drive controller.

      They ended the roll-your-own-but-do-it-wrong era.

      Regards,
          Bill Drissel

    7. Re:Print Link, The 25 in a list by marafa · · Score: 0

      so there has been no innovative microchip since 1989. is there a reason for that?

      --
      _ In Egypt Networks: Network Solutions with a Twist
    8. Re:Print Link, The 25 in a list by Mr+Z · · Score: 4, Interesting

      I'm not convinced. Some of these were just lucky, and rode the wave when the world shook, as opposed to shaking the world. The 555? Yes, truly sublime. The 741 op-amp? So fundamental, you couldn't imagine the world without it. But the 6502? A lucky near-clone of the 6800 that was popular not because it was particularly innovative, but because it was cheap. The 8088? The bastard stepchild of the 8086 which lucked out in getting picked over the 68000 in the IBM PC.

      Others are just interesting historical detours. Deep Blue and Transmeta Crusoe both were very interesting technologically, but they are in some sense interesting historical cul de sacs. The Explorer and related LISP machines, Intel's iAPX432, and the INMOS Transputer also hang out in this neighborhood.

      DMD? Ok... that one always felt as if it was a project that succeeded only by application of the principle that with sufficient thrust, any pig will fly.

      Anyway... I guess any list like this is subjective.

    9. Re:Print Link, The 25 in a list by labnet · · Score: 1

      Great list, but I would add a few old chips

      78 series voltage regs. (ie LM7805) All that logic needed sweet regulated power supplies, and 78 series of regulators are still a great choice for a cheap linear reg.
      4000 series logic. What made these chips great was you could operate them from 3v to 15v, thus a great choice for hobbiest battery powered projects.
      8051 Intels first mass microcontroller (also made by phillips/nxp)
      LM324 My old preffered cheap op-amp over the 741 as it was single supply and lower current.

      --
      46137
    10. Re:Print Link, The 25 in a list by Quothz · · Score: 2, Informative

      Also, just listing the "winners" doesn't do justice to the article.

      On the Internet, we have what are called "hyperlinks". They're typically colored differently from other text and underlined; when your mouse cursor passes over them, it will generally change. If, while your cursor is over the hyperlink, you press the left mouse button (called "clicking"), your browser will load a different page, to which the hyperlink points.

      A good example of this can be found in your parent's post, near the top. That poster included a colon after the first line of his or her post; this is a grammatical convention which denotes that the statement is more fully described by that which follows the colon. Try clicking on that hyperlink now, then use your browser's "back" button to return to this page. Wow! You found the complete text of the article on one page!

      I'm'a go out on a limb and suggest that the complete article does, in fact, do justice to the article. I don't think abstracting the list detracts from it, either.

      And today we've both learned lessons on the magic of the Internet and the magic of reading and the magic of me being a condescending bastard.

    11. Re:Print Link, The 25 in a list by Phoghat · · Score: 1

      2 - Texas Instruments TMC0281 Speech Synthesizer (1978) Still get the creeps when I hear that Speak and Spell

      --
      Think of how stupid the average person is, and realize half of them are stupider than that.
    12. Re:Print Link, The 25 in a list by Linker3000 · · Score: 1

      4017 FTW (and rows of flashing LEDs)

      --
      AT&ROFLMAO
    13. Re:Print Link, The 25 in a list by K.+S.+Kyosuke · · Score: 1

      What? Where is SID?

      --
      Ezekiel 23:20
    14. Re:Print Link, The 25 in a list by Jeff+DeMaagd · · Score: 1

      If you're trying to say I missed the point of the GP post, fine.

      But you had either twisted my words to mean what I clearly didn't say, missed the point of what I was trying to say or both.

    15. Re:Print Link, The 25 in a list by necronom426 · · Score: 1

      What? Where is SID?

      That's what I want to know. The SID chip has had as much impact on me as the 6502 (actually the 6510) and 68000 series.

      It's actually my favourite chip ever. Yes, I have a favourite computer chip :-)

  2. All of them great by Kell+Bengal · · Score: 4, Insightful

    Even as a modern EE/robotics guy I use some of those parts today (555 timers in particular). I can't imagine the pain you'd have to go to to do some of the things they were used for in their heyday with discrete transistors and passive components.

    --
    Scientists point out problems, engineers fix them
    altslashdot.org: The future of slashdot.
    1. Re:All of them great by Anonymous Coward · · Score: 1, Informative

      I can't imagine the pain you'd have to go to to do some of the things they were used for in their heyday with 555 timers...

      There, fixed that for you...

      Really though, an ATtiny AVR will replace the 555 with a lot more flexibility, fewer passives and better accuracy...
      Cost wise, about the same....
      The 555 does have a wider voltage range however...

      Long live the AVR....

    2. Re:All of them great by kbob88 · · Score: 4, Interesting

      I'm continually amazed at all the stuff people get the 555 to do. Just google '555 circuit', and be prepared for some major geek accomplishments.

    3. Re:All of them great by noidentity · · Score: 2, Interesting

      The chip gives you a set of building blocks, so there is great flexibility in how you can combine them. There's probably some similarity to good software API design here, where you provide orthogonal features that the user can combine however he likes, allowing a small API to provide lots of functionality.

    4. Re:All of them great by frieko · · Score: 3, Funny

      As a young whippersnapper I imagine the pain of reading the 555 datasheet whenever I flash a timer to an 8-pin microcontroller ;)

    5. Re:All of them great by NoMaster · · Score: 4, Informative

      As an old fart, I wonder why you'd rather use a microcontroller with all the attendant pickyness over I/O and supply voltage stability and noise and costing > $1 in bulk, over a 555 that'll work in fairly noisy conditions from 5~15v and costs a few cents in bulk.

      Horses for courses; just try getting your microcontroller to do something like flash an LED in a car without all the extra supply regulation and filtering. A 555 will do it with 6 additional components, including the LED, for less than $1 ;-)

      --
      What part of "a well regulated militia" do you not understand?
    6. Re:All of them great by NoMaster · · Score: 3, Interesting

      (Actually, you've just inspired me. Someday I'm gonna build a calculator, based on a 8 pin micro, to display the optimum R1, R2, & C for a given frequency on an LCD screen.

      I might even throw in calculation of values for monostable and bistable mode ;-)

      --
      What part of "a well regulated militia" do you not understand?
    7. Re:All of them great by frieko · · Score: 1

      PIC10F200, 41 cents
      5 volt regulator, 16 cents
      LED
      resistor
      Vdd capacitor

      To each his own; I was really just looking for an excuse to use the word 'whippersnapper'. (And as a coincidence I do have a uC in my car, it fools my crappy tape deck into thinking my iPod is the factory trunk-mount cd changer.)

    8. Re:All of them great by cibyr · · Score: 0, Redundant

      I was about to post something very similar - why would anyone bother with a 555 these days when you can get an ATtiny for under a dollar?

      --
      It's not exactly rocket surgery.
    9. Re:All of them great by evanbd · · Score: 1, Informative

      The PIC does it with three external components -- a regulator and a capacitor for power, and a resistor to help drive the LED. If you run at lower supply voltages you can omit the resistor and use the output impedance of the PIC instead, provided you don't care about tweaking the power consumption. Lower parts count and less board area is cheaper, and the PIC is only marginally more expensive than the 555.

      And not only is the PIC cheaper, it can do a better job for most circuits. It will operate a more accurate long-period timer without precision components, and do it at sub-microamp power consumption.

      At the extreme end, I can make a PIC blink an LED only when it's dark out, using only a CR2032 coin cell, a PIC, and LED. Let's see you get a 555 to do anything useful with two external components, including the battery.

      Of course, I say all that, but I prefer to build my circuits with op amps instead of PICs, and I debug them with a Tek 561A. Heck, in the right context a medium speed op amp or three has more compute power than a PIC...

    10. Re:All of them great by NoMaster · · Score: 4, Interesting

      Sorry, should have said AU$ ;-)

      A PIC 10F200 costs AU$1.24 in > 25 quantities, compared to an NE555 at AU$0.429 / unit, AU$0.351 > 10+, or AU$0.26 > 250+

      And yeah, I was just poking fun at whippersnappers who automatically put a micro into everything. Don't forget to amortise the cost of your programmer hardware & coding time ;-)

      You also forgot the Vcc cap - don't worry, so did I with my mental zener-based supply. Don't want your regulator latching up or self-destructing on +- supply spikes, do you? ;-)

      (Aside: I once built a set of Knightrider lights for my car (OK, OK - feel free to poke fun at me for that but, in my defence, it was the 80's ;-) based on a 555, a BCD up/down counter, and a BCD-decimal decoder. I didn't filter the supply well enough, but that had the advantage of when it started working erratically by skipping lights or suddenly reversing direction, I knew it was time to change the distributor points ;-)

      --
      What part of "a well regulated militia" do you not understand?
    11. Re:All of them great by evanbd · · Score: 2, Insightful

      The operational basics of the 555 are completely explained by a half-page functional block diagram. You can easily fit all the important max ratings and speeds and such on the other half of the page. Even the 10F200 has a 96 page data sheet (though to be fair, to be that thorough about the 555 would probably require 2 or 3 pages, not just one).

      The PIC has a lot going for it when compared to a 555, but simplicity is not one of those things.

    12. Re:All of them great by frieko · · Score: 2, Funny

      And in return I'm going to port MPLAB to the 555 ;)

    13. Re:All of them great by Anonymous Coward · · Score: 0

      "I can't imagine the pain you'd have to go to to do some of the things they were used for in their heyday with discrete transistors and passive components."

      Progress at times was slower back then, at least by todays standards, but at the time it didn't feel like it was slow as technology back then seemed just as exciting as it is today, because we could do things so much easier than previous decades and do so many new things that would have been extremely difficult to do decades before.

      In hindsight looking back, the speed work is done today highlights the ever increasing speed of technological change. For example, as an apprentice engineer I was once set the task of designing traffic lights using only 74xx series components. These days with one AVR its easy in a few hours to create something with a lot more complex functionality. These days its easy to create half a dozen prototype designs in the time it took to create one design back then, so new products are going to be created faster than before.

      But then I guess future generations will look back at us and think things like, wow how did they ever get anything done with *only* that technology. :)

    14. Re:All of them great by servodave · · Score: 2, Insightful

      TRUTH! I've used both AVR's and 555's extensively. 100's of circuits with each over the years. Micros have their place, but they are too picky about too many things. The 555 is bulletproof and listing it as #1 is very appropriate. All hail the lm555.

    15. Re:All of them great by mako1138 · · Score: 2, Informative

      The PIC requires some infrastructure, though: compiler/assembler, programmer. The 555 requires no external programming.

      That said, it's amazing what you can do with a dirt-cheap microcontroller these days.

    16. Re:All of them great by mikael · · Score: 2, Interesting

      My hardware engineering professor once told us this story.

      One time the air force were looking for a visual system to detect airmen who had parachuted into the ocean. The requirements were that the visual system should have a 180 field of view in order to detect a single point of orange to a distance of several miles, be able to work within a fixed temperature range, require the minimum of maintenance and be vibration resistant. Two solutions were proposed.

      The first system was a real-time video system with multiple processors and cameras. This would be built from industrial PC's and reinforced chassis with a power supply from the aircraft.

      The second system consisted of a couple of detachable cages on each side of the helicopter. Each cage was air-conditioned using the warm air from the engine, had a window and a row of pecking buttons. The pigeons were trained to peck the button whenever they saw a point of orange light. Whenever three or more pigeons started pecking, an alarm would go off in the cabin.

      During tests, the pigeon based system had a higher accuracy rate than the electronic system.

      --
      Vintage computer adverts: http://www.vintageadbrowser.com/computers-and-software-ads
    17. Re:All of them great by Temkin · · Score: 1

      I didn't filter the supply well enough, but that had the advantage of when it started working erratically by skipping lights or suddenly reversing direction, I knew it was time to change the distributor points ;-)

      I'll wager a 555 in 8 pin TO can that half of Slashdot knows nothing of distributors or points. ;-)

    18. Re:All of them great by tuxicle · · Score: 1

      And I'll wager, um, a 555 in a DIP or SOIC that more than half of Slashdot doesn't know what a TO can is :)

    19. Re:All of them great by aynoknman · · Score: 2, Insightful

      Yeah but cleaning the bottom of the cage under the real-time video system with multiple processors and cameras is easier.

      --
      We need a "+1 -- nice sig" moderation.
    20. Re:All of them great by Mr+Z · · Score: 1

      I started building such a thing myself, but I used a 4 bit binary counter, 74138 decoder and some XOR gates. The 4 bit counter always up-counted, and you just XOR the 4th bit with the other three to get the back/forth oscillation. The whole thing drove some super-bright LEDs. And, of course, a 555 provided the clock.

      I never finished them, though I do still have the parts somewhere. I breadboarded the digital section and verified it, and soldered together a few LEDs worth of the analog portion.

      Yes, I actually built an analog fade circuit for each LED based around a Darlington-pair PNP (yes, you read that right) driver for pull-down to light the LED, and then an RC circuit to give a lamp-like fade. The resistor had a diode across it to give it a fast charge time and slow discharge, so that the high-lumen LEDs looked like lamps coming on and fading slowly.

      If I were to do it again, I'd just use a microcontroller and apply PWM to the LEDs. I've written that code a dozen times over in other projects for status display on bar-graph LCDs.

      Oh, and to those who remind about "red lights are illegal on the front of a non-emergency vehicle", that's true on public motorways, but if you only light them on private property you're fine. Plus, mine were going to be concealed under the hood anyway.

    21. Re:All of them great by Mr+Z · · Score: 1

      What if I know what both are? Do I win a prize or something?

    22. Re:All of them great by lanswitch · · Score: 2, Insightful

      but does it run linux?

    23. Re:All of them great by NanoGradStudent · · Score: 1

      You learn something new every day! LED as (probably not great, but acceptable) light sensor. Heck, looks like there's even a Wikipedia page on it.

      Sucks that a lot of the lower-wavelength (blues, greens, whites) have such a high forward voltage, and really low reverse voltage tolerance.

      Maybe use one of these to charge up the internal A/D and sample briefly?

      --
      Just a little guy, y'know?
    24. Re:All of them great by Linker3000 · · Score: 2, Interesting

      LM3909?

      LM3909 Chip (sadly discontinued)
      LED
      Cap
      2 x Resistors for Vcc > 6v

      --
      AT&ROFLMAO
    25. Re:All of them great by evanbd · · Score: 1

      The simple way is to connect the LED anode to the PIC pin, and cathode to ground. Then drive the PIC pin to ground. Change the pin to a digital input and wait for it to trip high. The photodiode current combines with the diode capacitance and pin capacitance to determine the rate of charge, and the digital input makes an appropriate comparator. Time how long it takes the pin to go high, and you have your light measurement. The A/D might work, but it presents more load and is slower and more complicated to use. And of course, if you want you can then drive the pin high to turn on the LED.

      In this mode the LED is wired as a solar cell; it is always forward-biased. Normal photodiode sensors are usually run in a reverse-biased mode for increased sensitivity, but that isn't a requirement. In fact, if you get a largish LED, the solar cell current is large enough to measure directly on a multimeter -- a few hundred nA in moderate light.

      (Not my idea, and I don't remember where I first saw it.)

    26. Re:All of them great by berend+botje · · Score: 1

      Can't believe some third party didn't take over production of these excellent chips.

      They are still available (new old stock) but prices are rising steadily.

    27. Re:All of them great by Dan+East · · Score: 1

      Because a true geek would not just want the LED to flash on and off symmetrically, but instead flash their name in Morse code. Try doing that with a 555. ;)

      --
      Better known as 318230.
    28. Re:All of them great by Megane · · Score: 1

      It's in a plane. Over water. You don't need to clean under the cage, just leave a hole in the hull below it. You can't go high enough to need a compressed atmosphere, because then the pigeons wouldn't be able to see anything.

      --
      #naabhaprzrag, #sverubfr-000, #agi-fcbafberq, negvpyr[pynff*=' negvpyr-ary-'] { qvfcynl: abar !vzcbegnag; }
    29. Re:All of them great by Megane · · Score: 1

      Back in The Old Days, the data sheets to chips would be stapled to the backs of the hang cards in Radio Shack. I still have a 4-page 555 data sheet somewhere. And those are full 8.5x11 pages, not data book half-legal size pages.

      --
      #naabhaprzrag, #sverubfr-000, #agi-fcbafberq, negvpyr[pynff*=' negvpyr-ary-'] { qvfcynl: abar !vzcbegnag; }
    30. Re:All of them great by gillbates · · Score: 1

      I too, still use the 555, if for nothing more than convenience. However, I started with discrete transistors and RC networks, and things like timers, flip-flops, one-shot triggers, etc... are not at all difficult to replicate if you understand BJTs. The 555 did two things for engineers:

      1. It reduced the amount of analysis required for timer circuits with respect to their BJT counterparts. One can simply apply the datasheet formulas and forget about the rest.
      2. It reduced part count and cost for the design.

      The latter was probably the more important of the two.

      --
      The society for a thought-free internet welcomes you.
    31. Re:All of them great by Anonymous Coward · · Score: 0

      Tell that to The Hoff.

  3. Bender? is that you? by DudeFromMars · · Score: 3, Funny

    If the 6502 was good enough for Bender, why did they bother with anything else?

  4. 386? by Entropy98 · · Score: 1

    No 386? Protected Mode FTW

    1. Re:386? by noidentity · · Score: 5, Funny

      Protected mode was just the x86 architecture welcoming itself back to the reality most other processors already inhabited.

    2. Re:386? by NoMaster · · Score: 2, Informative

      I think you mean "No 286? Protected mode FTW".

      The 286 had protected mode; you just couldn't return to real mode (which is where everything ran in those days) without the nasty hardware hack IBM developed for the AT. The big advantage of the 386 over the 286 was that you could return to real mode from protected mode without resetting the CPU via the keyboard controller...

      --
      What part of "a well regulated militia" do you not understand?
    3. Re:386? by Mr+Z · · Score: 1

      Whaddaya mean? You could triple-fault a 286 to get back to real mode, so I hear. You didn't need to ask the keyboard controller to reset you.

    4. Re:386? by JamesP · · Score: 1

      Thank you

      Really, really insightful post

      It also has a lot to do with the difference between Win9x and Windows NT line (2000,XP, etc)

      One is 32bit from the ground up, one is a kludge

      --
      how long until /. fixes commenting on Chrome?
    5. Re:386? by Anonymous Coward · · Score: 0

      The 386 also broke out of 256 KByte segments which finally made a real flat mode available everyone else already had. Nobody had segments and nobody was happy with them only intel had, because it was a nasty hack to support bigger memory without bank switching!

  5. 6502 couldn't stop Sarah Connor? by billstewart · · Score: 1

    so they needed an upgrade?

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
    1. Re:6502 couldn't stop Sarah Connor? by Mr+Z · · Score: 1

      That wasn't the 6502's fault, it was Nibble Magazine's! They really shouldn't have been messing around with the DOS 3.3 disk catalog.

      (Yes, DOS 3.3 kept its "Volume Table of Contents" (TOC) on track 17 (aka, $11). You know, I never really looked closely at this code. This code seems to be doing something wacky with an extended 80-column card. It's moving 1K worth of stuff to "AUXMEM" (the ext 80 column card space). Why? I don't know. I do know that POKEing the right location can move the VTOC's sector, and is a fun and cheap way to "protect" a disk from amateur eyes. I have a few of those that I made myself.)

  6. Mmm.. now these are some sexy chips by Anonymous Coward · · Score: 0

    *fap* *fap* *fap*

    1. Re:Mmm.. now these are some sexy chips by binarylarry · · Score: 1

      I don't get it, are you a bat?

      --
      Mod me down, my New Earth Global Warmingist friends!
    2. Re:Mmm.. now these are some sexy chips by brackishboy · · Score: 1

      A masterbat, maybe.

  7. Re:What? by Snowblindeye · · Score: 3, Informative

    Agree totally about the 555 but what? No 741 (Op Amp) or 7400 (or any other TTL?) ? Those were the staples of most electronic projects as kits or in magazines etc.

    I know reading the FA is frowned upon on slashdot, but if you did, you could find the 741 as number 6.

  8. Re:What? by Anonymous Coward · · Score: 0

    The 741 is number 6 on the list.

  9. 6502 - C64 by Anonymous Coward · · Score: 0

    How can you list the PET but not the C64 as an application of the MOS 6502?

    1. Re:6502 - C64 by Anonymous Coward · · Score: 0

      The C64 used a 6510?

    2. Re:6502 - C64 by Mr+Z · · Score: 2, Informative

      ...which was basically just a 6502 with an extra I/O port. FWIW, most people think of the Atari 2600 as using the 6502, when really it used a 6507. All that was was the same die with fewer address lines pinned out.

      Can we stop splitting hairs now?

  10. Re:What? by NoMaster · · Score: 2, Interesting

    Yeah, the 741 is there (though I reckon it should be #2, or even #1 - you know you can make a 555-equivalent suitable for most purposes with a couple of 741's and some clever circuit design, right? ;-).

    But yeah, the lack of 7400 series (the original TTL versions, not that 74xxC crap ;-) is odd. Definately should be up there ~ #3 or higher. That stuff was the building blocks of computers before dedicated CPUs.

    --
    What part of "a well regulated militia" do you not understand?
  11. The 6502 - coulda, woulda, shoulda... by toejam13 · · Score: 5, Interesting

    Interestingly enough, when Bill Mensch and company designed the 6501 (and later lawsuit modified 6502), they purposely made it very easy to expand it for future use. Although the chip was original designed for use in embedded solutions, several reports suggest that Bill Mensch, as well as fellow designer Chuck Peddle, saw the possibilities of the personal computer. This was around the time that the Altair 8800 was just released.

    Bill Mensch attempted to push Commodore for features that might be useful for a personal computer. However, Commodore management rebuffed him. Supposedly frustrated that Commodore management was as short sighted as the Motorola management that he had fled from just a few years earlier, Bill Mensch went on to start his own company designing successors to the 6502.

    Over at Western Design Center, Mensch and his sister designed the WDC 65C02, a bugfixed and enhanced version of the MOS 6502, that found its way into the Apple IIc and "enhanced" IIe. They also designed the WDC 65816, an extremely feature enhanced version of the 65C02 that included 16-bit index registers, 24-bit addressing, movable stack and zero page locations, and a host of new ops that allowed for jump tables and position independent code (useful with multitasking OSes and shared libraries).

    Just imagine if Commodore had the 65816 in 1980 and released a 16-bit successor to the PET that could handle up to 16MB without the weirdness of bank swapping or segmentation. It would have been very popular with programmers. Smoking the "what if" crack pipe even more, imagine if they ported TRIPOS to the 65816. :)

    Too bad they probably would have ruined it by bundling it with a chicklet keyboard.

    1. Re:The 6502 - coulda, woulda, shoulda... by PhantomHarlock · · Score: 3, Insightful

      There's a pretty good write up of those days at MOS in the Rise and Fall of Commodore book that was reviewed here on Slashdot some time ago.

      I'm glad the 6502 made the list, along with the 68000 that the Amiga used so well along with Paula, Agnes, Denise etc and its successors the 68020, 040 etc. 8088 of course, and the 555 still in use today as others have mentioned. SPARC was pretty big in its day. Z80. ARM1. Those are the ones that stick out in my head the most.

      And yea the Crusoe, I dunno about that.

      It's amazing how most of these names are not much more than a word or phrase in the eyes of most people born in the 1990s or late 1980s. To us older chickens they were almost breathing, anthropomorphic beings because of how tightly you could weave assembly code around them and take advantage of their physical properties, bugs and nuances to perform hacks. When computers stopped being quaint hobby machines, they lost their soul. Early steam engines were similar, with highly polished brass, brightwork and victorian scroll work, imbued with the personality of their creators. When the railroads got real big, they became commodities, were painted black and weren't assigned a crew for life, so there was no pride of ownership. Now we are in the the era of the Dell box...I don't build my own machines anymore because it doesn't make any financial sense.

      Good times to remember.

    2. Re:The 6502 - coulda, woulda, shoulda... by uassholes · · Score: 1

      In the late '70s I lusted after an Ohio Scientific 6502 based computer (http://oldcomputers.net/osi-600.html), but had to settle for a used Poly88 8080 based system (http://www.digibarn.com/collections/systems/Poly88/index.html). They were probably equally capable but the OSI seemed sexier. When the IBM PC came out, I lost interest in microcomputers because they had become appliances, like toasters.

    3. Re:The 6502 - coulda, woulda, shoulda... by Tablizer · · Score: 2, Interesting

      Just imagine if Commodore had the 65816 in 1980 and released a 16-bit successor to the PET that could...

      According a quote from Chuck Peddle in "Rise and Fall of Commodore", he didn't see much of a demand or need for 16-bit processors. Commodore kicked around the idea of a 16-bit chip, but there didn't seem to be much enthusiasm for it, so it languished. What they saw was pressure for more peripheral features for less cost: cheaper floppies, harddrives, printers, color monitors, etc. And companies were finding ways to address more RAM under 8-bit chips. He suspected that IBM's success with 16-bit was based largely on marketing hype (16 is bigger than 8) and IBM's name.
         

    4. Re:The 6502 - coulda, woulda, shoulda... by toejam13 · · Score: 1

      According a quote from Chuck Peddle in "Rise and Fall of Commodore", he didn't see much of a demand or need for 16-bit processors.

      I could see where a 16-bit data bus, such as found on the 68000 and 8086, might have been seen as overkill in 1980. You could even argue that a 16-bit index register was overkill in 1980. However, a flat memory model that could access more than 64KB of data was something that was starting to be important by that point. Commodore's own SuperPET, released in 1981, came with 96KB of RAM and 48KB worth of ROMs. You could also get RAM expansion and ROM expansion kits for the earlier PET 4000 line that pushed memory sizes well above 64KB. By 1982, you had the C64 that couldn't even access all of its RAM without bank switching. It was even worse with the CBM-II series and later C128.

      The handwriting was not only on the wall, it was on the ceiling and the floor. The 64KB limit had to go, and bank switching was an evil way to do it. Yet Commodore hung onto bank switching for an obscene amount of time. Even as late as 1989, the unreleased Commodore 65 used a modified 65CE02 core as opposed to a 65816 core. Imagine working on a 1280×200 16 color screen using bank switching.

      Next to that stupid zero page boundary bug, nothing annoyed me more as a 650x programmer than bank switching. Several people that I've talked to have agreed with me. It really blew chunks, especially when you were working with large data sets.

    5. Re:The 6502 - coulda, woulda, shoulda... by metamatic · · Score: 1

      Just imagine if Commodore had the 65816 in 1980 and released a 16-bit successor to the PET that could handle up to 16MB without the weirdness of bank swapping or segmentation.

      You mean like the Apple IIgs?

      --
      GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
    6. Re:The 6502 - coulda, woulda, shoulda... by Tablizer · · Score: 1

      A higher-level language could hide the process of bank-switching from the programmer, as long as the chip runs faster to compensate.

    7. Re:The 6502 - coulda, woulda, shoulda... by toejam13 · · Score: 1

      True. However, thunking between banks to keep data in a common area can be a fairly resource intensive job. What could be done with a single long call has to be replaced with a number of moves to select and then bring data from a high bank in the REU into bank 0.

      Running the processor at a faster speed essentially negates the cost savings of leaving 8 extra address lines off the bus. All of your support chips now need to run at the faster speed, and that adds expense. And as shown with the VIC-II in the C128, that is not always possible.

      Lastly, high-level languages in 1980 kind of sucked. To be honest, they still suck today. I think you'd end up with a lot more bank sloshing than with hand tuned assembly. And the overall code would be of lower quality, given the poor level of optimization that compilers and interpreters did back then. Heck, even cc65, a modern ISO C compiler for the 65xx series, doesn't do any code optimization. And it is a program that I would have killed for twenty years ago.

    8. Re:The 6502 - coulda, woulda, shoulda... by Albert+Sandberg · · Score: 1

      I'm just going to randomly suggest everybody to take a look at "the 386 business case" from computer history museum hosted on youtube. Good stuff :)

    9. Re:The 6502 - coulda, woulda, shoulda... by omz13 · · Score: 1

      When I started programming many, many years ago, it was for teh Acorn Atom, and later the BBC Micro... both of which had a 6502 at their heart. I remember earning assembler for it, and having oodles of fun once I grokked it. Its a shame that the processor didn't go further, but I guess you could say the Acorn ARM was its natural successor, since many people migrated from the BBC MIcro into the Acron Archimedes and its ARM CPU (which then disappeared into the embedded world).

    10. Re:The 6502 - coulda, woulda, shoulda... by eison · · Score: 1

      I like the current times better, because I can't afford a steam engine, and it's truly amazing what happens when every tom, dick and harry can afford to make stuff.

      --
      is competition good, or is duplication of effort bad?
    11. Re:The 6502 - coulda, woulda, shoulda... by Tablizer · · Score: 1

      In 1980 very few were buying anything more than 8-megs, maybe 16 at the end of the year for high-end. When hardware costs control, then convenience of the programmers is secondary. True, hardware designers may not fully appreciate the issues of programming for a given chip, and thus not care enough, but it could also be the other way around to some extent: that programmers didn't understand the issues of hardware costs. Early microcomputer programmers were generally expected to jump thru hoops. For example, the programmers for the first release of VisiCalc had to write their own keyboard controller/poller because they found Apple's not adequate.

  12. The 8088? Oh, please! by Anonymous Coward · · Score: 5, Insightful

    FTFA:
    Among the many great chips that have emerged from fabs during the half-century reign of the integrated circuit...Intel's 8088

    Wrong. The 8088 was a technical nightmare with a crappy architecture . It just got lucky. IBM's justifiable preference was Motorola's infinitely superior 68000. Unfortunately, the 68000 was 9 months to a year away form production and the 8088 was in production 'now'. IBM felt that it had do it 'now' or miss the market window, so they (reluctantly) went with the 8088. A combination of perfect timing, luck, great marketing form IBM and Intel then and superb marketing strategy from Intel (the best selling sow's ear ever) sealed its place in history as a marketing success, but by no means a technical marvel.

    1. Re:The 8088? Oh, please! by x2A · · Score: 5, Funny

      "The 8088 was a technical nightmare with a crappy architecture . It just got lucky. IBM's justifiable preference was Motorola's infinitely superior 68000. Unfortunately, the 68000 was 9 months to a year away"

      Yeah, I hear ya, the architecture of a chip is much more important than whether it exists or not.

      --
      The revolution will not be televised... but it will have a page on Wikipedia
    2. Re:The 8088? Oh, please! by Anonymous Coward · · Score: 0

      Then it should have been the 4004, the first CPU evar.

    3. Re:The 8088? Oh, please! by Thomasje · · Score: 5, Interesting

      The 8088 was a technical nightmare with a crappy architecture . It just got lucky. IBM's justifiable preference was Motorola's infinitely superior 68000. Unfortunately, the 68000 was 9 months to a year away form production and the 8088 was in production 'now'. IBM felt that it had do it 'now' or miss the market window, so they (reluctantly) went with the 8088.

      The 8088 was a big step forward compared to the 8080, 8085, and Z80, which were the dominant CPUs for "personal computers" in the late '70s and early '80s. The 8088 could address one megabyte of memory without needing any external bank-switching hardware, and it had 16-bit registers throughout, and it could run at higher clocks than the aforementioned 8-bit CPUs of the time. Compared to the 64 kilobyte address space of the 8080/8085/Z80 and the 6502, this was a big improvement, and, as lame as it may sound today, a CPU with 16-bit registers and a 4.77 MHz clock was pretty fast compared to what existed in personal computers at the time.

      The 8088 really was a significant improvement. Yes, the 68000 was better, but it wasn't available in quantity yet, but perhaps even more importantly, choosing the x86 for the PC meant that software like WordStar and DBase and others, which was written in 8080 assembly language, could be ported to the new platform relatively easily. Porting 8080 code to the 68000 means rewriting everything; porting that same code to the x86 at least makes it possible to reuse some code -- because the x86 assembler can grok 8080 assembly language. Yes, you have to deal with the x86 segmented memory model, and with the differences between the CP/M system calls and those of MS-DOS, but those chores are still a lot less onerous than having to rewrite *everything*.

      Neither Intel nor Microsoft "got lucky" when IBM defined the PC architecture. Those were the technologies that made the most sense at the time.

    4. Re:The 8088? Oh, please! by Sanat · · Score: 5, Interesting

      I will never forget that it was in 1972 and I was troubleshooting a logic board for Wang Laboratories' 1200 Word Processor and I encountered a 4004 chip for the first time in a schematic. I realized at that instant that the whole computer paradigm would shift with the new types of chips and that the old computer methodologies would then become extinct.

      I never dreamed how quickly or how convincingly this would occur. Up to that time a computer for me consisted of a whole room full of a CPU and memory and now it all was on a small board with high density chips.

      That is when I realized that becoming a Cobol, Fortran and C programmer would be a way of extending my talents. Of course everyone who worked on a main frame knew the associated assembler code so the Intel assembler was just another assembler technique and it was taken pretty much in stride.

      Back then we did not even have ROM chips and so we used a wire laced through 44 coils and by strobing the wire,a 44 bit readout was produced which included the next wire to strobe. Depending on whether the wire was laced through the coil or around it would determine if the value was a 1 or 0. Doctor Wang was a genius when it came to those early designs.

      --
      And in the end, the love you take is equal to the love you make
    5. Re:The 8088? Oh, please! by geirnord · · Score: 1

      Thanks for sharing!

      Finally some good and true /. insights.

      Belivable also due to a 3 digit! user ID!

    6. Re:The 8088? Oh, please! by ChrisMaple · · Score: 3, Interesting

      Nice tale, but a Z80 at 4 MHz would routinely outpace the 8088 at 4.77 MHz unless the code was heavy with multiplies. The Z80's second register set and some of its extended (beyond 8080) instructions gave it the additional power to beat the higher-clocked 8088.

      --
      Contribute to civilization: ari.aynrand.org/donate
    7. Re:The 8088? Oh, please! by Anonymous Coward · · Score: 0

      Actually it could address a big range of memory, but compared to all other architectures out there the 8088 was a simple nightmare just designed to be compatibel to the 8080. I personally think not even Intel thought it would survive a few years, it just should give them time to design a decent architecture!

    8. Re:The 8088? Oh, please! by Anonymous Coward · · Score: 0

      "Compared to the 64 kilobyte address space of the 8080/8085/Z80 and the 6502, this was a big improvement, "

                Not a BIG improvement -- it used 64KB segments with a segment register. With segmentation, it supported 1MB of RAM, but it did NOT support a flat 1MB of address space.

    9. Re:The 8088? Oh, please! by Anonymous Coward · · Score: 0

      Didn't the 2Mhz 6502 regularly outpace a 4MHz Z80 ?

      What about the 6809 ??

  13. Crusoe was a failure by YesIAmAScript · · Score: 4, Interesting

    It was nothing special at all and it definitely didn't shake the world. It didn't lead to a bunch of devices using it and it didn't lead to a new path for computing

    The presence of this chip on here makes no sense to me.

    Oh wait, I just got to where they talk about a Micronas MP3 decoding chip. So I guess this list is a little hit or miss.

    I could hardly agree more with the Chips & Technologies AT chipset being on this list. It may have been more important to the success of the 8088 than the 8088 itself was. All of a sudden making a PC clone was easy, and inevitably it became the standard, so standard that now even Macs use the PC architecture.

    --
    http://lkml.org/lkml/2005/8/20/95
    1. Re:Crusoe was a failure by bhtooefr · · Score: 3, Insightful

      Well, the Crusoe did enable x86 to push into the handheld computing market. Although, MIDs and UMPCs haven't exactly taken off, but the Crusoe got the market open for long enough for Intel to bring their entries into the market (the Intel A100 and A110 (underclocked Dothan Pentium Ms,) and later the Atom.)

  14. Re:What? by dr2chase · · Score: 3, Interesting

    What's amazing to me is how the op-amps have been improved. I checked out of analog chips for about 25 years, then had occasion to use them. LM258 -- runs on 3 to 32 volts, rail-to-rail inputs and outputs, uses a whole milliamp to run.

    Or the LMC6462 -- 3 to 15 volts, rail-to-rail in and out, 50 microamps supply, and an input resistance of 10 TeraOhms.

  15. Re:Bender? is that you? by aliquis · · Score: 1

    Maybe the wanted some more fuel efficient chips?

  16. Motorola 68k by newcastlejon · · Score: 5, Insightful

    Seriously! How many of us learned assembly with a 68k? How many are in service today. It's like the Mini/Beetle/Model T of the chip world: cheap, simple and with a practically cosmopolitan distribution.

    --
    If God forks the Universe every time you roll a die, he'd better have a damned good memory.
    1. Re:Motorola 68k by Anonymous Coward · · Score: 0

      For me assembly was learned on 6502 - Apple, Atari, Commodore.. I learned a lot of C on the 68k(Amiga and AT&T UnixPC) but not as much assembly.

    2. Re:Motorola 68k by Anonymous Coward · · Score: 0

      Man I was there and I am still in service :) but maybe not the 68K which, IMHO, has a better architecture than the x86.

    3. Re:Motorola 68k by Anonymous Coward · · Score: 0

      The 68000 wasn't exactly the only popular Motorola chip either. I've seen TONS of stuff use 6805 and 6809's (for example TRS-80's).

      An awful lot of embedded stuff these days still use a superset of the 6805 instruction set (including Atmel's AVR series, ST Micro's ST7 series and so on).

      So I still get to use Motorola-style assembly I learned more than 20 years ago to this day.

    4. Re:Motorola 68k by Anonymous Coward · · Score: 0

      +1 for learning assembly with 68k - Atari ST uber alles!!

    5. Re:Motorola 68k by Anonymous Coward · · Score: 0

      Right now (and maybe as early as the late '80s) it may seem like a VW Beetle but not when it was released. The fact is, the 68K got off to a slow start because of a certain short-sightedness that was widespread in the industry at that time. Companies that had been selling large systems with high profit margins at low volumes weren't ready to give up those profit margins by selling single-user PCs / micros instead. The 68000 was at first deemed "too powerful" for small systems and Motorola would rather have used it only as a cheap building block for $10K Exormac systems. Apple thought the 68K was so good that they could get away with writing the OS in interpretted Pascal, resulting in the poorly performing Lisa. A bunch of other early 68K systems shipped with Unix. It took several years before the 68K began to displace 8-bitters in mass market applications.

    6. Re:Motorola 68k by jonwil · · Score: 1

      If only IBM hadn't been so short sighted and gone with the 68000 for the PC, a lot of the crap that still clutters up the PC architecture to this day may not have ever come into being.

    7. Re:Motorola 68k by stevey · · Score: 1

      I started programming assembly on the z80 circa 1984.

      I dabbled with other processors at school, but mostly I was z80/x86. The fact that Zilog designers were ex-Intel was lost on me at the time, but I remember being pleased that the x86 processor wasn't too dissimilar to the z80 I'd started with.

    8. Re:Motorola 68k by CarpetShark · · Score: 1

      I learned 68k, for one. On the 68k, it was easy and a natural progression from C. By contrast, I've always avoided the horror story that x86 seems to be.

  17. A plug for Hans Camendzind's book by Man+On+Pink+Corner · · Score: 3, Interesting

    Too awkward to compose a URL at the moment, but if you're a pro or more-advanced hobbyist you should google the 555 chip's designer, Hans Camendzind . He released a nifty book on basic analog IC design that never got the attention it deserved IMHO. I believe it's downloadable as a PDF from his site.

    1. Re:A plug for Hans Camendzind's book by BikeHelmet · · Score: 3, Informative
    2. Re:A plug for Hans Camendzind's book by Man+On+Pink+Corner · · Score: 1

      Yep, and I also misspelled his name with an extra 'd'.

  18. 8088 - Gakk! by swm · · Score: 4, Interesting

    The 8088 is a twisted, flawed architecture.

    In true QWERTY fashion, it got a lock on the market by solving an immediate problem: the need to get beyond a 16-bit address space in a single-chip microprocessor. We are hamstrung by its limitations to this day.

    See

    Limitations of the IBM PC Architecture

                            or

            The Curse of Segments

    http://world.std.com/~swmcd/steven/rants/pc.html

    1. Re:8088 - Gakk! by Thomasje · · Score: 4, Informative

      What rock have you been living under? The linked rant/article is from 1992! Contrary to what it says, the limitations of the 8088 architecture *were* overcome by the 386, but that article was written before DOS extenders allowing protected-mode applications became common, never mind Windows adding protected-mode support. The Windows world has had a flat address space for many years now, and the segmented aspects of x86 are only supported for non-performance-critical legacy code.

    2. Re:8088 - Gakk! by Anonymous Coward · · Score: 1, Informative

      We've moved past those limitations. Yes, they still exist in the modern Core-class Intel CPUs (and the AMD equivalents). However, as soon as you boot into Windows XP, Windows Vista, Linux, Mac OS X, or just about any other OS on the market today, you're put into 386 protected mode. This includes support for a 32 bit flat memory addressing model, which just happens to be the addressing model used by these operating systems.

      Long mode (in x86-64) extends that further, into a 64 bit flat addressing model.

      So while segments were a bad design choice, looking back with the benefit of hindsight, it is not the case that it's hamstringing us today.

      That rant was written in 1992. 17 years ago. Newsflash: technology has moved on since then, and the x86 flaws are just a speck on the side of the instruction set decoder nowadays.

    3. Re:8088 - Gakk! by Anonymous Coward · · Score: 1, Informative

      I feel compelled to point out the fact that your QWERTY "example" is an urban legend:

      http://www.straightdope.com/columns/read/221/was-the-qwerty-keyboard-purposely-designed-to-slow-typists

    4. Re:8088 - Gakk! by Anonymous Coward · · Score: 0

      That leaves us now with a junk operation set and way to few general purpose registers...
      But at least with a flat address space.
      If it wasnt for AMD we probably still would have 1/3 less general purpose registers than we now at least have in 64 bit mode!

    5. Re:8088 - Gakk! by sjames · · Score: 1

      Nobody uses segments that way anymore. The limitation he was talking about for the 80386 was that DOS didn't use the protected mode capabilities. All modern OSes on x86 do use protected mode, so that's a long dead issue.

  19. 386, agreed by schwit1 · · Score: 1
    The article is "Microchips That Shook the World", not "Great microchips"

    The 80386 along with the C&T chipset ignited the IBM PC clone industry.

    1. Re:386, agreed by NoMaster · · Score: 1

      The C&T chipset certainly gave it a bump-along, but there were IBM PC clones around well before the 80386. Sales of original 8086/8088 genuine IBM PCs were dwarfed by sales of 8086/8088/V20-based clones, well before the 80386 was even developed.

      --
      What part of "a well regulated militia" do you not understand?
  20. where's the i486? by drfool · · Score: 1

    grumble grumble

  21. Re:What? by szark · · Score: 1

    Yeah, the 741 is there (though I reckon it should be #2, or even #1

    They aren't ranked, so the numbers don't mean anything. It's just a list of 25 chips in no particular order.

  22. G4, G5? by PollyAnna · · Score: 1, Interesting

    I remember when the Apple G4 and G5 were not allowed in some countries because they were considered "supercomputers". I think that qualifies as "shaking the world".

    1. Re:G4, G5? by dafing · · Score: 1
      agreed, typing this on my Dual G5 Power Mac G5 :)

      Also, the Playstation 2 was classed as a supercomputer, its a marketing gimmick right? The thing with the PS2 was, you couldnt ship it overseas, or else "the tur-rusts will use it to steer cruise missiles".

      Good for you , bringing up the G4 and G5.

      --
      --- ...or a new slashdot signature. Dear aunt, let's set so double the killer delete select all
  23. 4000 Series CMOS by GrahamCox · · Score: 1

    OK, not a chip but a chip family - but surely one that, perhaps even more than the 7400 series, influenced an entire generation of engineers and circuit designs. It really was the first major series that allowed you to pretty much bolt together designs, lego-fashion, from building blocks without really worrying about interfacing too much. In comparison the 7400 series was much fussier with limited fanout and fan-in, and a fixed 5v supply. CMOS was BASIC to the 7400's COBOL.

  24. Missed a couple by nurb432 · · Score: 1

    LIke the ix432 ( check my nick.. you will understand ), AMD 29xx. Video chip sets too, like the ET4000 which brought 'accelerated vga' to the masses. Eproms.. .

    That is the problem with any list, its YOUR list.

    But i agree with most of it.

    --
    ---- Booth was a patriot ----
    1. Re:Missed a couple by TheRaven64 · · Score: 1

      Yup, it's a pretty good list but a little short on details. The ARM1 only merits a single paragraph, which is a shame because the story behind it is one filled with some typical British arrogance which turned out to be justified. They looked at the RISC designs coming out of UCB and decided that, if a bunch of American students could design a CPU, so could a handful of British engineers.

      They tangentially mention the Newton, but miss the part this played in the existence of ARM as it is today. Apple wanted a chip for the Newton, and were interested in the ARM1 prototype that Acorn produced (it was very fast and low power), but they didn't want to be dependent on a competitor (Acorn and Apple both made computers for similar markets) for a CPU. Advanced RISC Machines was spun out from Acorn, with some investment from Apple, as an independent company that would supply both. There are some interesting parallels here with Symbian, spun out by Psion to continue to develop their operating system (EPOC32) and license it to third parties as well as to Psion. As with ARM, Symbian survived the parent company's demise and went on to become a major player in the mobile market.

      Oh, and Sophie Wilson was called Roger Wilson back then.

      --
      I am TheRaven on Soylent News
  25. Zilog Z80 by TW+Burger · · Score: 2, Interesting

    I wrote an operating system and hardware drivers for a Z80 based embedded system in 1986. It was and still is a great processor as long as you only need 8 bits.

    1. Re:Zilog Z80 by EkriirkE · · Score: 1

      The Z80 really ought to be ranked higher. TI calcs, gameboy, synthesizers +++

      --
      from 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
      to 45 2F 6E 40 3C DF 10 71 4E 41 DF AA 25 7D 31 3F
    2. Re:Zilog Z80 by Anonymous Coward · · Score: 0

      The chips aren't ranked. They're in random order.

    3. Re:Zilog Z80 by Anonymous Coward · · Score: 0

      You can also add a LOT of arcade games to the list of Z80-powered machines.

  26. 555 survivor by mapuche · · Score: 1

    Chips usually have a short manufacture life. It's amazing the 555 timer is still in use, even after 556 (two 555 in one chip).

  27. Missing categories of chips by MagikSlinger · · Score: 1

    For example, the video chips that launched a revolution. From SGI's original graphics accelerators through the Amiga's "fat agnes" to the early nVidia and ATI cards.

    But I do admit I like the fact they included the 555 and 701. Such fond memories breadboarding with those things...

    --
    The bitter lessons of a veteran coder: http://bitterprogrammer.blogspot.com
  28. Where is the DARPA RISC-I? Standford MIPS? by toejam13 · · Score: 3, Informative

    For as groundbreaking that the ARM processor series, it was beat to the punch by DARPA. Not only did they help give us the Internet, they also helped with the evolution of chips that power your PDAs and smart phones that use the Internet.

    Now for a trip back in time... supposedly during the late 1970s, processor design was starting to hit the limits of manual design. These were still the days of designing a microprocessor on paper. The military, a huge consumer of microchips at the time, decided to sponsor research into the creation of standardized processes for microprocessor design. The result was DARPA's VLSI Project. Standford, UNC/Chapel Hill, Berkeley and others were involved.

    Numerous products and organizations came out of the VLSI Project. The BSD fork of AT&T's System-V saw major use and evolution. Networked CAD systems matured, specifically using the Stanford University Network (SUN) workstation, which was commercialized by Sun Microsystems.

    Most relevant to the article, though, was the advancement of the "RISC" design. During the 1970s, researchers noted that highly orthogonal processors (where every type of operation, such as ADD, SUB, SHIFT, XOR, etc..., can be used with any kind of memory operator, such as direct, indirect, indexed, etc...) were somewhat wasteful. The vast majority of operations were rarely used. If you restricted those operations to register-only ops, you could really simplify the processor.

    RISC architectures are less memory efficient than CISC architectures, something that was important in the 1970s, a time when dinosaurs roamed and 4KB Altairs roamed the world. They are also more tedious to program using assembly languages, also an issue during the 1970s when higher-level language compilers were rather unoptimized. However, by the time that the VLSI Project came around, these limitations were going away.

    Since RISC processors are so much easier to design than CISC processors, researchers used their groovy new tools to design one. So in 1982, the DARPA RISC-1 was born, which had less than half the number of transistors as the Motorola 68000. It also ran circles around the 68000. A year later, the RISC-II was released. It was three times as fast as its predecessor.

    The RISC design was also a huge advancement for researchers over at Standford. John Hennessy over there was trying to design a new processor that exploited the concept of pipelining. The problem, however, is that CISC instructions have variable (and often long) execution time. This can cause the pipeline to stall since the processor runs dry on data to execute. RISC design solves that problem because most of the operations, with exception of memory load/store ops, are short and quick. Hennessy borrowed these "new" concepts and came up with the MIPS architecture, one of the first popular RISC designs.

    Not much later, Acorn Computer, looking to replace the MOS 6502 processor but dissatisfied with the Motorola 68000, National Semiconductor 32016 and others, went looking for a new chip in 1983. They traveled to the States and visited Western Design Center. Seeing how "simple" it was to design a processor, they brainstormed up the concept of the ARM1.

    The ARM probably would never have been designed without the advances that came out of the VLSI Project. The ARM2, the first production unit, only contained some 30K transistors. The DARPA RISC-I was 44K while the RISC-II was reduced to 40K. The 68000 was a whopping 70K transistors.

  29. 6502 and 680x0 both! by Slur · · Score: 4, Insightful

    Yep, I learned my first Assembly Language on the 6502 back in 1983 or so, and had just started writing cool, fast game and utility software on the Atari 800 around 1985 using the very nice Atari Macro Assembler, when *boom* the era of Atari was over.

    So I moved to the Amiga and programmed that lovely machine in 680x0 assembler using the slick "DevPac" programming environment by HiSoft. Bad geek that I was, I never learned Intuition or any of the Amiga system calls, but went straight to the hardware for the titles I worked on, namely "Dino Wars" and "Bill 'n' Ted's Excellent Adventure" (apologies for both). Then *boom* the Amiga was dead.

    After a long hiatus from programming I got a PowerMac. On the Mac the first software I bought was the fringe macro assembler "Fantasm" by Lightsoft, thinking I'd be a Mac Assembler guru, but alas, Apple had moved from 680x0 to the PowerPC by that time, and only insane maniacs program that chip directly in Assembler.

    So finally, in 1995 I finally learned C, and a few years later C++.

    Of course nowadays I learn a new programming language every year and an entirely new framework or API every couple of months.

    --
    -- thinkyhead software and media
    1. Re:6502 and 680x0 both! by _merlin · · Score: 3, Interesting

      LOL, I must be an insane maniac, as I like programming in PPC assembler (SPARC, too, FWIW). I get to do a bit of assembly language at work for synchronisation primitives and such, but never whole applications any more. I miss being able to use more assembler.

    2. Re:6502 and 680x0 both! by rockmuelle · · Score: 1

      Shameless plug:

      If you love PPC assembler, check out CorePy (www.corepy.org). Full support for the PPC/VMX ISAs using Python as the "assembler".

      We're doing our best with CorePy to make assembly programming fun and accessible to a new generation of coders. There's also support for the Cell SPU ISA (e.g., Playstation 3) and x86/SSE with support for AMD/ATI's CAL GPU ISA coming soon.

      -Chris

    3. Re:6502 and 680x0 both! by Megane · · Score: 1

      I learned Z-80 assembly language back in 1979... from Bill Gates himself, in the form of TRS-80 Level II BASIC. There was 12K of well written (if mostly 8080-style plus relative jumps) assembly code in there, just the right size to study and learn from.

      Then I became one of the first "Switchers" and went to Mac. The 68000 is really nice to program in assembly language. And I still dabble in it a bit, by trying my hand at Sega Genesis programming. However, I have gotten tired of writing new code in assembly language and got a GCC cross-compiler built. But like always, I've learned how things work under the hood before doing it the "easy way".

      --
      #naabhaprzrag, #sverubfr-000, #agi-fcbafberq, negvpyr[pynff*=' negvpyr-ary-'] { qvfcynl: abar !vzcbegnag; }
  30. Re:What? by evanbd · · Score: 3, Interesting

    The low-power, low-voltage op amps are impressive -- I'll see your LMC6462 and raise you an LT6003: 1.6 to 16 volts, 1uA supply, though the input resistance is slightly worse at 10GOhm (differential) to 2TOhm (common mode).

    In some ways more impressive, imho, are the high speed precision op amps. Take a look at the LT1468, for example -- 90MHz, 75uV offset, and settles to 150uV in under a microsecond.

    On the other hand, most of my breadboards still begin life with a uA741 or LM324 -- I'd much rather let the smoke out of a cheap op amp than an expensive one. Once the smoke stays in, I'll swap it for the one that will actually act as a precision part.

  31. Not so great! by Anonymous Coward · · Score: 0

    > PIC10F200, 41 cents
    > 5 volt regulator, 16 cents
    > LED
    > resistor
    > Vdd capacitor

    This Bill of Materials is not gonna land your thingamajig in the dollar store!

    Better:

    NC7S14P (Single gate '14 Schmitt trigger inverter in sc70) : 4 Cents
    2 R's: 2x 0.5 cent
    2 C's: 2x 1 cent
    Led: you get what you pay for

    Runs from 2 to 6 Volts directly off your battery

  32. Re:What? by dr2chase · · Score: 1

    I ended up with the LM258 because it fit my application -- controlling BuckPuck output on a hub dynamo-driven bike light. It needs to be making sense of its inputs with as little as 7.5 volts of power (when the LEDs begin to light) and not catch fire till 32V. But boy howdy, I used a bunch of LM324s in a theater lightboard almost 30 years ago.

  33. Shook the World? I'd rather just find out about... by BikeHelmet · · Score: 3, Interesting

    I'd rather find out about interesting and unique chips, rather than ones that "shook the world".

    Like the Propellar, with its interesting interrupt handling, and non-stamped design.

  34. Re:What? by Anonymous Coward · · Score: 0

    ...you know you can make a 555-equivalent suitable for most purposes with a couple of 741's and some clever circuit design, right?

    Yes, it's called an airport.

  35. Re:Shook the World? I'd rather just find out about by BikeHelmet · · Score: 2, Interesting

    Damnit, I clicked Submit rather than Continue Editing!

    This isn't so much impressive hardware, as impressive software:

    http://video.google.com/videoplay?docid=-5885351342753379583&q=8088

    FMV on an 8088!

    Okay, I admit, the quality/resolution isn't that good, but it's still fascinating. :P

  36. No Opteron???! by warrior · · Score: 1

    While it's relatively new compared to everything on this list, the AMD Opteron, which came out in 2003, will be the face of computing for the foreseeable future. Even now in 2009 AMD's archival Intel is just coming out with integrated memory controllers and high-speed serial direct interconnects. The Opteron also forced Intel to give everyone 64-bit memory addressing in x86 (which Intel wanted to stay in the realm of high-end RISC/Itanium machines).

    Opteron wasn't the first chip to have any of these features, but it was the first _x86_ chip to have all of them - making it an affordable "high-end" processor for small businesses and tech junkies. It really was a "world-shaking" product that put AMD on the map. No one expected little AMD to make a splash so big with Opteron (except Intel, which paid off companies to not release Opteron-based products, a55holes!).

    --
    Intel transfer the difficult from Hadware to software, for get more power, programmer need more technology. -- chinaitn
  37. The Motorola 6800 (not the 68000) by awfar · · Score: 1

    They could not include every processor, of course, but this was a nice piece of hardware at the time. The Heathkit microprocessor trainers used it (programmed it to play Anchor's Away! as extra credit for retired Navy prof), had accum A, B, and an index register/addressing (the first uP to do so?), 16 bit regs, flat memory space and memory mapped I/O. Preceded the later 6502 which had a similar programming model. It was clean and fun to learn; the Intel architecture has always been foreign to me; was there separate I/O bus instructions? dunno...

  38. Hmm, I would add the 80386 and the 3dfx Voodoo by tjstork · · Score: 1

    I would make the argument that if you were going to pick an Intel CPU, that "shook the world", it would be the 80386 more than the 8088. Dubbed, the mainframe on the chip, it more or less lived up to its hype. Following in the wake of the 80386 came Linux and Windows NT... essentially server operating systems running on a desktop.

    The 8088, conversely, was just another personal computer chip. It had some advantages but didn't really change the sorts of operating systems you could make with it. Atari, Apple and IBM DOS's were all single program, single user.

    The reason was hardware. It was the 80386 that made it possible to do mainframe type things on a PC.

    1) It had access to theoretically gobs of memory, introduced a flat memory model that eliminated once and for all the need to worry about 64k boundaries (this was even an issue with the 68000 - performance reasons),

    2) all allowed for hardware based memory protection so that applications wouldn't trounce each other.

    3) provided hardware support for virtual memory.

    --
    This is my sig.
    1. Re:Hmm, I would add the 80386 and the 3dfx Voodoo by GrahamCox · · Score: 1

      Nah. The 386 was only Intel getting its act together - finally - after the debacle of its earlier efforts and finally waking up to the far cleaner design that was the 68000 family. The 68000 was truly a "mainframe on a chip", it was designed precisely to look like the architecture of a PDP-11, and its design began in 1976. Intel took nearly twenty years to catch up.

      Atari, Mac, Amiga? They all used the 68000 family, because you could write a GUI-based OS to run on it. By contrast, the Intel chip held back that approach on the IBM-PC platform, just look at the travesty that was Windows 1.0 and 2.0 compared with its 68000-based contemporaries. It did take the 386 to change that for the PC platform, but only because Intel copied the 68000. That then allowed Windows 95 to run reasonably well and the rest is history.

      If IBM had chosen the 68000 for its PC project, things may have turned out very, very differently.

    2. Re:Hmm, I would add the 80386 and the 3dfx Voodoo by tjstork · · Score: 1

      If IBM had chosen the 68000 for its PC project, things may have turned out very, very differently.

      Yeah, it would have and it could have. But then, it would have undermined what could have been achieved with the Amiga, ST and Mac....

      The reason I gave the 386 the plug was I felt the memory management and hardware paging were more central to having a multiuser OS than more registers... Amiga was cool but I've had enough GURU MEDITATION ERRORS for one lifetime. The system was just not stable.

      --
      This is my sig.
    3. Re:Hmm, I would add the 80386 and the 3dfx Voodoo by the_lesser_gatsby · · Score: 1

      The 68000 didn't have virtual memory so can't be compared with the (later) 80386. The 68010 (which I programmed on in the 80s in a Torch XXX) had virtual memory and was the 'mainframe on a chip'. Also I question this idea of IBM considering the 68000 for the IBM PC. The 68k had a 16-bit data bus so would have meant a more expensive mainboard design than the (8-bit bus) 8088. The Motorola chip to compare with the 8088 is the 68008 (Sinclair QL anybody?).

    4. Re:Hmm, I would add the 80386 and the 3dfx Voodoo by mdwh2 · · Score: 1

      Amiga was cool but I've had enough GURU MEDITATION ERRORS for one lifetime. The system was just not stable.

      Few systems of the time were stable - the Amiga lacked memory protection, so any buggy program could take down the OS, just like many other OSs of the time such as MacOS and DOS. So unless you were running Linux or NT on your 386, this isn't a relevant factor.

      "Guru Meditation" was just an early example of how seeing the effect of a crash would give a popular system a bad name even if it wasn't any less stable. People get annoyed at the crash, yet they don't ever have experience of how stable less popular systems are. Just like happened with Windows and the BSOD years later, even now with the NT line that is just as stable as Linux or OS X (indeed, I predicted that this would happen when I saw Windows replacing Amiga in home computing - the token Windows fan poked fun claiming the Amiga was unstable, but I knew the same would happen to Windows as more people used it at home).

  39. Re:Shook the World? I'd rather just find out about by evanbd · · Score: 1

    The Propeller looks really interesting. I might get one to play with, but I'm disappointed by the lack of Linux support.

    I'm also surprised they don't have *any* hardware peripherals on-chip. I'm used to working with the PIC microcontrollers, which give me tons of things like UARTs, USB interface, SPI controller, CAN bus, A/D converters, timers, PWM output, comparators, etc. Obviously some of that can be implemented with one of the cogs, but some of it would be hard or impossible. The lack of hardware multiply and divide support is also annoying.

    Most of my projects involve interfacing with the outside world in some non-trivial fashion; the Propeller doesn't do much to make that easy, which is disappointing. I do appreciate that they have a DIP package, though -- most high-performance microcontrollers these days are surface-mount only, which makes breadboards somewhat tricky.

  40. Once could say we don't have enough segments... by tjstork · · Score: 2, Insightful

    Actually, one could make the argument that we do not have enough segments. Were there more segments available within an application, you could have theoretically eliminated some sorts of attacks caused by buffer overruns.

    Looking back at the time, going from segments to flat was a godsend. However, going from segments to selectors would have been probably better from a security standpoint, although computers would be slower.

    --
    This is my sig.
    1. Re:Once could say we don't have enough segments... by TheRaven64 · · Score: 2, Interesting

      Mod parent right up. With the 8086, segments were actually useful, they were just (effectively) start addresses in memory and you had direct access to the next 64KB with 16-bit pointers. The 386 kept segments, but made them useless. You get 8192 global ones and 8192 local (per-process) ones. This is enough for some tricks, for example putting the stack and heap in separate segments so that they can grow independently, but not enough for anything really fun. With a bigger LDT you could put every object / structure and every array in its own segment and get bounds checking done for free in the hardware. The 80386 model of layering segments on top of paging is great because it lets the OS deal with pages (fixed size, easy to swap) but lets the userspace code play with segments (variable size, fit them to data structures).

      If you've ever programmed in PL/M 86, you know how powerful segments can be (sadly C, being designed for machines without an MMU, does not have any way of exposing this, and therefore neither do languages built on top of C). For embedded systems where you don't have much RAM and only a single process, you can use all 65536 segments on a 386 and get hardware range checking on all of your complex data types.

      --
      I am TheRaven on Soylent News
    2. Re:Once could say we don't have enough segments... by tjstork · · Score: 1

      Just imagine a world where a PC's computer hardware had the same range checking and memory security as what is done in Java and C# today. That would completely kick ass.

      With the amount of memory that is out there today, you could have really giant LDTs...

      --
      This is my sig.
    3. Re:Once could say we don't have enough segments... by owlstead · · Score: 1

      IMHO segments and/or write protection (no execute bit) for data are just patches. Buffer overruns should be managed by the software or, if possible, by a virtual machine - managed code.

      The reason is simple: if you can have a buffer overrun, you can write over other parts of the data. If you do this you can change values, so that the program gets into invalid states.

      Now you can do tricks like re-ordering data each run, but the problem of getting into an invalid state will stay. To cut the story short, you need to check your bounds one way or another instead of relying on memory protection (within an application).

    4. Re:Once could say we don't have enough segments... by Megane · · Score: 1

      Indeed. The problem with the 8086/8088 wasn't the segments, it was the 16-bit offsets. Segments had potential, but they were mainly used as an excuse to stay with 16-bit registers. This was definitely not an example of a "future-proof" architecture. While the 8088 was an 16-bit computer in an 8-bit body, in contrast, the 68000 was a 32-bit computer in a 16-bit body. The 8086/8088 architecture had to be re-designed to be 32-bit, but the 68000 never had to be re-designed to be 32-bit.

      The worst part was the 80286. I still find it hard to believe that someone thought that 16-bit offsets were okay for a "next generation" CPU, after the way that the 8086 got used. By the time the 386 came out, people were pretty damn tired of the segment registers and went completely linear.

      --
      #naabhaprzrag, #sverubfr-000, #agi-fcbafberq, negvpyr[pynff*=' negvpyr-ary-'] { qvfcynl: abar !vzcbegnag; }
  41. 6502 FTMFW by Anonymous Coward · · Score: 0

    .org $8000
            ldx #0
    - lda msg,x
            beq +
            jsr $fded
            inx
            bra -
    + bra +
     
    msg .db "NMOS FUCK YEAH!", $0d, $0a
    .db $00

    Will make sense to everyone, but $FDED only to Apple II buffs. :-) And screw Slashdot for messing up the formatting + not supporting PRE.

  42. No 7400? by tubepwn · · Score: 1

    I doubt many of those would exist without the venerable 7400.

  43. 1982 Siberian explosion - care with what you steal by Anonymous Coward · · Score: 0

    Now that was a chip that shook the world.
    The Soviets shopped around for automated pipeline software.
    The US gov provided just what they needed.
    Computer chips would be designed to pass Soviet quality tests and then to fail in operation.
    "to reset pump speeds and valve settings to produce pressures far beyond those acceptable to the pipeline joints and welds. The result was the most monumental non-nuclear explosion and fire ever seen from space."
    http://news.zdnet.co.uk/software/0,1000000121,39147917,00.htm

  44. How can I learn electronic design by Anonymous Coward · · Score: 0

    For a number of years now I've worked as a programmer, and I've always wondered about electronics design. I took a few college classes in analogue and digital electronics, but they always seemed to focus mainly on the analysis of circuits or other peripheral issues such as semiconductor physics rather than the design process. As such I still have no idea about electronic design.

    Reading this article I wonder how one can develop skills in designing basic circuits that utilize these and other chips? Can anyone recommend some books / courses that offer a relatively painless introduction to how one goes about actually designing and building circuits? Although I have a degree in mathematics / comp sci when I start reading books that are full of theorems and proofs I start to wonder do people in the real world actually use this as a basis of circuit design?

    Also is there any open source software for circuit design?

    Unfortunately the circuit designer seems to be a relatively rare breed compared to other technology professionals such as programmer.

    1. Re:How can I learn electronic design by Anonymous Coward · · Score: 0

      Have a look at this one:

      ahref=http://www.amazon.com/Digital-Design-Principles-Practices-Package/dp/0131733494/ref=pd_bbs_sr_3?ie=UTF8&s=books&qid=1241244504&sr=8-3rel=url2html-26747http://www.amazon.com/Digital-Design-Principles-Practices-Package/dp/0131733494/ref=pd_bbs_sr_3?ie=UTF8&s=books&qid=1241244504&sr=8-3>

      Man, textbook prices are insane these days.

    2. Re:How can I learn electronic design by downix · · Score: 1

      Also the BeBop series of IC design books by Clive Maxfield I can highly recommend. A very good breakdown of the hows and whys.

      --
      Karma Whoring for Fun and Profit.
    3. Re:How can I learn electronic design by ChrisMaple · · Score: 1

      1. "Radio Amateur's Handbook"
      2. old, but "Wave Generation and Shaping" by Leonard Strauss
      Generally, you want to consider something that you'd like to build, then write out a circuit on paper. Fill in component values, do the math to see if it will work. Look up characteristics of devices you'd like to use on manufacturer's data sheets, check again more carefully to see if it'll still work. Change what needs to be changed. Build it and try to figure out why it doesn't work; fix it.
      You'll need to buy parts and breadboards, and buy/build power supplies. Solder, wire, soldering iron. Multimeter, oscilloscope. Unless you are doing only digital design, you need hardware experience to be a good designer.
      SPICE is free and open-source, but you only need be concerned that it is free.

      --
      Contribute to civilization: ari.aynrand.org/donate
    4. Re:How can I learn electronic design by Fyzzler · · Score: 1

      Here are two sources to give you a start.
      The Art of Electronics
      Neets

      --
      I have one question. If the Japanese Ministry of Agriculture is not in charge of Gundam, then who is?
  45. What about the 8051? by Anonymous Coward · · Score: 0

    The 8-bit Intel 8051 (descendant of the 8048) should have definitely been on the list. It's got great longevity and has had countless variants from dozens (hundreds?) of chip design companies. Name an embedded application and there's an 8051 variant for it (within the realm of 8/16-bit computing power). I'm not sure why there are so many variants, but I would think it'll be around long after every other architecture has died (including the x86).

  46. PowerPC by GrahamCox · · Score: 2, Insightful

    The PowerPC should really be there. Not so much for its use in the Mac, but because it's so widespread in the embedded world. In fact, I think it's the most used embedded architecture by far. You might not think of your car or washing machine as "world-changing", at least not for their electronics, but actually the reliability of modern devices is largely down to this. The PPC must be one of the most common "invisible" bits of technology that most people actually use.

    1. Re:PowerPC by Anonymous Coward · · Score: 0

      Dunno what planet you're living on, but on Earth the 32-bit embedded market is divided up between ARM, MIPS and AVR32.

  47. errr....TI TMS1000? by Anonymous Coward · · Score: 0

    The first? (I know Intel 4004, arguably second.) Or The TI TMS9900. First single chip 16 bit architecture? Maybe they thought it was unfair. TI pretty much dominates the list anyway...

  48. Hey, OP! by Jane+Q.+Public · · Score: 1

    It's "outside the box", not "out of the box".

    "Out of the box" is pretty much synonymous with "off the shelf."

    1. Re:Hey, OP! by owlstead · · Score: 1

      That was a quote, so you'll have to contact the editors of the original article instead. /. can't change the summary, or it won't be a direct quote. Maybe /. can use a [ed: that should be "outside the box"], but that's probably taking it a bit too far.

  49. Only 1 chip from the 21st century makes the list. by upuv · · Score: 1

    12 - Transmeta Corp. Crusoe Processor (2000)

    Yah OK technically not the 21st century. :)

    But that's it? We haven't managed to come up with some new weirdo bizzaro way of adding numbers since 2000?

    29 years 25 cips. 9 years nothing.

    Are we at our limit? Or has comp sci evolved to some new level where the instruction set doesn't matter?

  50. Re:What? by Linker3000 · · Score: 1

    Any list is subjective, mine would include some 'fun' items from my hobbyist days - for example:

    ZN414 TRF radio
    SN76477 Sound generator
    78xxx Three terminal regulators
    27xx EPROM
    4017 Decade counter

    --
    AT&ROFLMAO
  51. Re:Only 1 chip from the 21st century makes the lis by inasity_rules · · Score: 2, Insightful

    Nah, you no longer need to be extremely inovative to produce awesome chips. These are the days of cheap transistors on nm manufacturing scales. We have gotten to the point where a clever way of doing something is obsolete, because its faster and cheaper to throw more transistors at our designs and resuse all our existing "cleverness".

    There is something about limited resources that encourages amazing innovation. When we have "enough", why innovate?

    --
    I have determined that my sig is indeterminate.
  52. Re:Shook the World? I'd rather just find out about by BikeHelmet · · Score: 1

    I don't know if it's fast enough for linux. It really is a microcontroller - not a full fledged CPU or SoC. It only has something like 32KB of RAM built-in. You might get one of those DOS-style assembly operating systems to run on it, but probably not linux.

    I'd rate it somewhere up there with all those AVR CPUs used in projects like the Arduino - except with different capabilities.

    Their website has a lot of downloadable code on it. Do some research and see if anyone has written code for what you need. :)

  53. The Callisto... by Genda · · Score: 1

    In 1997, a company in Sunnyvale, named Silicon Spice, created an amazing device. It had over 80,000,000 transistors, and replaced one or more huge (over 4 foot square) motherboards manufactured by ATT. The chip had a hundred simple cores, and massive amounts of peripheral network management and computing power.

    It was called Callisto, and it was bought by Broadcom. Three genius, genius engineers from MIT created it, and it allowed high performance signal processors to be implemented in software. In fact it allowed multiple communication applications to run simultaneously, making dirt cheap large scale VOIP possible. Dynamic application switching allowed software for operating VOIP, to be swapped out with network management, modem operation, DSL, virtually anything you might want to throw over copper or fiber. A significant number of concepts in this device revolutionized telecommunications.

  54. Re:Where is the DARPA RISC-I? Standford MIPS? by downix · · Score: 1

    They have the RISC-I in there, it's called the SPARC.

    --
    Karma Whoring for Fun and Profit.
  55. Which company was that? by jonaskoelker · · Score: 1

    Bill Mensch went on to start his own company designing successors to the 6502.

    Cyberdyne Systems?

  56. Re:Where is the DARPA RISC-I? Standford MIPS? by TheRaven64 · · Score: 1

    There are some major differences between SPARC and RISC I. SPARC has a variable number of register windows arranged in a circle. This is where the 'scalable' in the name comes from. Simple SPARC chips for embedded applications typically only have 2-3 register windows, while high-end workstation chips have 8 or more. Because they are arranged in a circle, programmers can assume there are an infinite number and just handle the fault when you try to use one more than there really is. RISC I and RISC II both had static register files and the programmer (or, more commonly, compiler writer) had to be aware of the exact number.

    --
    I am TheRaven on Soylent News
  57. Re:Shook the World? I'd rather just find out about by TheRaven64 · · Score: 1

    The interrupt-handling design on the propeller isn't particularly novel, unless you restrict yourself to PC hardware. Mainframes and supercomputers often handle interrupts like this, on a separate, dedicated, interrupt controller. A typical IBM supercomputer, for example, has one or two PowerPC 4xx series chips for handling I/O without the need to interrupt the main CPU. The Wikipedia article is also slightly misleading, when it talks about saving state and then restoring it to handle an interrupt. A lot of chips have some special registers which are only visible in privileged mode (e.g. in ISRs) and will have ISRs written specifically to only touch these, making the switch to and from an ISR much faster than a typical function call.

    --
    I am TheRaven on Soylent News
  58. Re:Shook the World? I'd rather just find out about by evanbd · · Score: 1

    I meant Linux development support -- it would need a lot more memory and an MMU to get Linux running on it.

    As a 32-bit device at 20 MIPS per core and 8 cores, it has significantly more performance than the 8-bit AVRs (40 MIPS max, I believe) and PICs (12 MIPS) in most applications. The PICs will outperform it if you need a lot of multiplies -- hardware multiply of 8 by 8 to 16 bit result in a single cycle; that can do a 16x16 to 32 in about 2us, iirc. A single propeller core looks like it would be a bit slower at that, but if you can get several cores working on the problem, it might do better.

    For performance in a hobbyist-friendly DIP package, though, the real competitor is the 16-bit dsPIC line. Those have a pair of 40-bit accumulators and a DSP engine that can do a single cycle A += B*C, where B and C are 16 bit variables in memory and A is the accumulator. And it will increment the registers that store the pointers, so you really can do an n-element 16-bit dot product in n cycles, running at 40 MIPS.

    If you're interfacing purely with other digital hardware, I suspect that in many cases you could replace the hardware peripherals of a PIC with a cog, at a cost in software complexity. The end result is that you have one main thread talking to several peripherals, much like in a PIC.

  59. Dr. Wang by Anonymous Coward · · Score: 0

    Thats not the only thing Doctor 'Wang' was good at.

  60. Re:1972 by TaoPhoenix · · Score: 1

    Oh my word, that was amazing.

    Can I cut your lawn now?

    --
    My first Journal Entry ever, in 8 years! http://slashdot.org/journal/365947/aphelion-scifi-fantasy-horror-poetry-webzine
  61. Re:Shook the World? I'd rather just find out about by BikeHelmet · · Score: 1

    Most of that is completely over my head, but it does sound interesting.

    Today I stumbled on yet another Propeller project - A wiki reader.

    http://hackaday.com/2009/05/02/wikibrowser/

    The project homepage is linked in the comments. I think the reader would be better with some formatting, but still quite neat!

  62. They've missed the 3 1/2 digit A/D by Kupfernigk · · Score: 1
    Although there were numerous models from different suppliers, the basic count up and count down 3 1/2 digit A/D architecture revolutionised instruments. It basically killed the analog meter, and also got us used to accurate electrical measurements for routine use. The best you could do with a mirrored AVO dial and careful zeroing was maybe 1%, while a cheap LED or LCD meter could be accurate to 1 part in 1000 as was far more portable. Nowadays, LCD meters typically consume only 250 microamps - more than the AVO, but you can run them from a single lithium cell for a long time - nearly a year of continuous use.

    Before they came out, at one company I worked for, I replaced a measuring system using a storage oscilloscope with a box containing an RCA microprocessor, a precision comparator, and a D/A converter which drew the output on a screen for as long as you wanted, and then digitised the measurement sweep on demand. The entire thing including a monitor cost less than a single replacement tube for the scopes, and had infinite persistence without fading. That was when I realised how revolutionary A/A and A/D conversion were going to be. Nowadays you can do the entire thing with a single embedded microcontroller. But the 3 1/2 digit A/D is still much more accurate for single point measurements.

    --
    From scarped cliff or quarried stone she cries "A thousand types are gone, I care for nothing, no not one."
  63. They left out the Amiga's Agnes? by Sxooter · · Score: 1

    Seriously, it was the first commercially produced blitter! It allowed the Amiga to multitask smoothly and reliably with only 256k of ram. It had a huge impact on gfx chipsets to come after it.

    --

    --- It is not the things we do which we regret the most, but the things which we don't do.
  64. Deep Crack by Anonymous Coward · · Score: 0

    What, no Deep Crack? http://en.wikipedia.org/wiki/Deep_crack

  65. Influential chips -- not innovative ones by DragonHawk · · Score: 2, Insightful

    "But the 6502? A lucky near-clone of the 6800 that was popular not because it was particularly innovative, but because it was cheap. The 8088? The bastard stepchild of the 8086 which lucked out in getting picked over the 68000 in the IBM PC."

    The article is entitled, "25 Microchips That Shook the World". The criteria is chips which were influential in their impact. That doesn't necessarily mean they had clean or clever designs, or were particularly innovative, or even "good" by any objective measure. It means that they mattered in the course of industry.

    You dismiss the 6502 because it's only innovation was low cost. That still counts, and arguably more than most other distinctions. The Ford Model T, the Apple II, the IBM-PC clones, even books printed on the Gutenberg printing press -- their big difference was that they were cheap enough to bring their products to a much wider market. Legions of people who couldn't afford technology before suddenly could .

    The 8088's big feature was being in the right place at the right time, no doubt about it. But it still went on to propel the x86 in to being the dominant architecture for general-purpose computers today. Wintel uses it. Apple Mac uses it. Most free *nix boxes use it. Sun uses it in many of their products. Even supercomputers use it. Quite simply, x86 is everywhere. That's "world shaking" by any definition I can think of.

    There's a lesson here, too. Many times engineers and geeks favor technically sophisticated or clean designs, and reject designs which don't meet those criteria, and loose big time when their theoretically "better" design loose out to a cheaper or more practical alternative. Call it "worst is better" if you like, but putting all your money on a horse that loses the race isn't good, either.

    --

    dragonhawk@iname.microsoft.com
    I do not like Microsoft. Remove them from my email address.
  66. Disappointed about the 1802 by LionMage · · Score: 1

    The article only briefly touches on the 1802, which was a ground-breaking chip that found its way into satellites and control systems for just about every kind of military gear you could think of.

    I built a Cosmac Elf as a science fair project in high school, and it was a blast. The heart was an 1802 processor -- I didn't get the rad-hardened version in the ceramic package, which would have cost far more than my shoestring budget could afford, but the plastic package version instead. The design was already old when I started wire wrapping this thing, so some parts had to be replaced with improvised versions (e.g., the hexadecimal display chips that had dot-matrix LEDs on the top face, and took a nybble as input -- had to replace those with 8 discrete LEDs and read output in straight binary).

    One of the things I liked about the 1802 is that it had TTL outputs with enough juice to drive certain control circuits without a bunch of extra coupling hardware. (Some low power devices could be driven directly, and everything else just needed a cheap transistor. I drove relays with this thing.) There were also inputs to which you could directly attach some analog domain sensors, such as a photoresistor.

    Sorry to see the 1802 didn't make the list, but at least they included the 555 and the 741.

    Surprised they didn't mention that the 68000 was one of the few CPUs to use a nanocode architecture to decode microcode operations, in order to reduce the chip real-estate used for storing decode logic -- in my grad level CPU architecture class, the technique was likened to using two smaller ROMs and a bit of clever logic to replace one huge ROM. (And when I took 6.004 as an undergrad, we actually built a discrete component computer using this exact same technique -- one EPROM was for the nanocode interpreter, and two served the microcode interpreter. Oddly enough, we were told by our professor, "This technique would never be used in the real world." Maybe not in 1993, but the 68000 has an older pedigree, and was apparently one of the last few chips to be designed by hand. If I were those guys, I too would be using every trick and cheat to reduce transistor count.)