Slashdot Mirror


The Ever So Unlikely Tale of How ARM Came To Rule the World

pacopico writes "About 24 years ago, a tiny chip company came to life in a Cambridge, England barn. It was called ARM, and it looked quite unlike any other chip company that had come before it. Businessweek has just published something of an oral history on the weird things that took place to let ARM end up dominating the mobile revolution and rivaling Coke and McDonald's as the most prolific consumer product company on the planet. The story also looks at what ARM's new CEO needs to do not to mess things up."

44 of 111 comments (clear)

  1. The future could be all in the fabs by mrspoonsi · · Score: 2, Interesting

    And Intel have the advantage there.

    1. Re:The future could be all in the fabs by BasilBrush · · Score: 2

      And some of Intel's fabs are manufacturing ARM chips. Intel doesn't have to lose for ARM to win.

    2. Re:The future could be all in the fabs by MachineShedFred · · Score: 2

      More than that, doesn't Intel has an ARM license from when they acquired the detritus left over from the Compaq / DEC merger? They made the StrongARM series, and XScale CPUs for some time. I don't know if they sold the license to Marvell, or if it was just the XScale designs.

      --
      Slashdot still doesnâ(TM)t support Unicode after it was added to the HTML standard in 1997.
    3. Re:The future could be all in the fabs by alen · · Score: 2

      that ARM license just means you can make the same chips ARM designs

      Apple and Qualcomm have architecture licenses where they can design their own ARM chips. this is why a 1 GHz A7 CPU performs just as well in real life as a 2GHz samsung CPU. that and designing the software for the instruction set helps too

    4. Re:The future could be all in the fabs by Tough+Love · · Score: 2

      And Intel have the advantage there.

      Physics has the advantage. Clock scaling already ended, now feature size shrinking is grinding to a halt. The action has now shifted to ballooning core counts and power management strategy, where Intel has no compelling advantage. Intel's feature size advantage has not got long to live.

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    5. Re:The future could be all in the fabs by timeOday · · Score: 4, Insightful
      Another possibility is there is no real future - nobody will reap the profits Intel did for the last 30 years.

      Intel's earnings last quarter were $2,630 M compared to $156 M for ARM holdings. So if ARM is "ruling the world" like this story claims, then ruling the world just ain't what it used to be. And I guess that is likely, if semiconductors stagnate as they seem to be.

    6. Re:The future could be all in the fabs by leathered · · Score: 3, Informative

      Not really, what matters most is cost, and at that ARM wins hands down. Most ARM chips cost less than $5, with some selling for pennies. Intel enjoys 60%+ margins on everything it sells and they will experience a lot of pain giving them up.

      The only way Intel can compete is if they sell their mobile chips at or below cost. Oh wait, they already are.

      --
      For all intensive porpoises your a bunch of rediculous loosers
    7. Re:The future could be all in the fabs by NapalmV · · Score: 5, Insightful

      You mean using a C compiler instead of a Java interpreter helps with speed and power consumption? Who could have thought?

    8. Re:The future could be all in the fabs by tlhIngan · · Score: 2

      Not really, what matters most is cost, and at that ARM wins hands down. Most ARM chips cost less than $5, with some selling for pennies. Intel enjoys 60%+ margins on everything it sells and they will experience a lot of pain giving them up.

      The only way Intel can compete is if they sell their mobile chips at or below cost. Oh wait, they already are.

      And not to terribly fast either - given how the Apple A7 is running rings around Intel's chips.

      Granted, different architectures and different OSes, but the benchmarks that run on both Android and iOS generally show the A7 being faster (and not by a little bit - by a lot).

      And when 64-bit ARMs come out on Android, expect the Intel offerings to fall further behind. The A7 is fast because of the optimizations that the ARMv8 and 64-bit architecture allow.

    9. Re:The future could be all in the fabs by blackraven14250 · · Score: 2

      Considering how Intel managed to go from NetBurst (massively power-hungry) to Haswell (very power efficient), I wouldn't doubt their ability to out-engineer the companies currently designing ARM chips.

    10. Re:The future could be all in the fabs by rev0lt · · Score: 3, Insightful

      I'm reading this and laughing. I've read the same kind of statement when they're using 300nm tech, 95nm tech, 65nm tech, and so on and so forth. Their public roadmap has 5nm tech around 2019-2022 (http://en.wikipedia.org/wiki/5_nanometer). And as x86 inheritance slowly fades away, they can actually produce way smaller chips without backwards compatibility if the market demands it (very few applications run 1978 instructions nowadays, same goes for all that 16-bit protected mode wazoo).

    11. Re:The future could be all in the fabs by jrumney · · Score: 2

      Not to nitpick, but it's likely that *most* ARM chips made actually sell for pennies

      Not to nitpick, but the cheapest chips with ARM cores inside are a couple of dollars. Your link mentions 8051 microcontrollers being found inside SD cards, but 8051 microcontrollers are not ARM chips. It also mentions a Samsung eMMC chip with an ARM instruction set, but that eMMC chip is likely to cost a few dollars.

    12. Re:The future could be all in the fabs by evilviper · · Score: 2

      Your claim is utterly ridiculous. CPU cache OVERWHELMINGLY dominates the x86/x64 die. Intel/Amd could eliminate ALL processor functions, entirely, and the die STILL wouldn't be "way smaller" (or "way cheaper" for that matter).

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    13. Re:The future could be all in the fabs by evilviper · · Score: 2

      if you can free an additional 20% of real estate in the chip

      ...which you can't.

      Cutting parts and shrinking the design would produce less defects, and it would probably have a direct impact on price. I know, utterly ridiculous.

      Not "ridiculous" so much as a minuscule difference that will not have a visible affect on price or performance.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    14. Re:The future could be all in the fabs by Alioth · · Score: 2

      That won't work with ARM though. The reason why so many people build ARM is that you can license the core and add whatever peripherals you want onto the die. Or you can license the whole architecture and design your own complete ASIC around it, like what Apple does.

      With Intel, you get what Intel makes. You can't make your own custom Atom. You can't license the Atom architecture and make it part of your ASIC. You get only what Intel decides it wants to put on the die. So they can't even compete even way below cost price because they aren't offering the hardware manufacturer the same thing.

  2. Acorn Risc Machine by Grindalf · · Score: 4, Informative

    The acorn risk processor was designed for the British "BBC Microcomputer" to be attached via the "Tube" second processor system as a software development system for schools and colleges. This experimental machine was so successful and fast that it became became the new Acorn Archimedes computer which was used by the British Schools to teach kids how to write computer programmes.

    --
    The purpose of existence is to make money.
    1. Re:Acorn Risc Machine by BasilBrush · · Score: 3, Informative

      Well, I think it's fair to say that the ARM was designed for use in a new computer which turned out to be the Archimedes. It was available first as second processor for the BBC Micro, but that was really just a step in development, not it's original goal.

      Creating the ARM simply as a second processor wouldn't have been economically viable. Few people/organisations bought second processors.

    2. Re:Acorn Risc Machine by OneAhead · · Score: 2

      The acorn risk processor was designed for the British "BBC Microcomputer" to be attached via the "Tube" second processor system

      Oooh then we can stream BBC classics such as Monty Python's Flying Cicrus over you"Tube"!

      ...golly look at the time - I'll get my coat.

    3. Re:Acorn Risc Machine by newcastlejon · · Score: 4, Interesting

      ...it became became the new Acorn Archimedes computer which was used by the British Schools to teach kids how to write computer programmes.

      Speaking as someone who was brought up with BBC Micros, pointy little A3000s and a single majestic "don't you dare touch that" RiscPC, this turned out not to be the case in many schools. Certainly there were often computers aplenty, some running quite good educational programmes but most didn't have anything in the way of programming tools, especially the ones with RiscOS. The Micros were much better as anything you wanted to do on them started with a command line (only a kick in the backside away from learning BASIC) but the later models didn't include any development tools whatever unless you count the hidden command line...

      ...a command line that was so rarely needed they hid it. Acorn were ahead of their time in so many ways; it's a shame they didn't manage to do better outside the UK.

      --
      If God forks the Universe every time you roll a die, he'd better have a damned good memory.
    4. Re:Acorn Risc Machine by AlterEager · · Score: 2

      Remember the old joke, why don't the Brits make computers? Because they haven't figured out a way to make them leak oil yet.

      How could that be an old joke? Please name me a time when the Brits didn't make computers.

    5. Re:Acorn Risc Machine by Alioth · · Score: 2

      Not quite accurate.

      Acorn needed to move off the 6502, and they explored several different architectures for the new computer they wanted to build. They wanted very low interrupt latency, and they wanted a chip that could use all of the memory bandwidth - back in 1986, the processors for a personal computer were generally much slower than memory and had no cache, for example, the MC68000 takes often 8 or more clock cycles per instruction and doesn't have a cache, the 6502 takes 3 to 4 clock cycles per instruction at 1MHz etc. In particular, Steve Furber (designer of the original ARM chip) was horrified by the Nat. Semi 32016 (if I remember right) that had some instructions that took over 100 clock cycles to execute - and instructions cannot be interrupted while they are executing, so this would result in unpredictable and possibly very poor interrupt latency.

      So they decided no one was making a chip they wanted for the price they wanted, so inspired by the simple design of the 6502, they decided to design the ARM. They wanted to make it cheap so it had to be in a plastic package, so it had to dissipate less than 1 watt. They had no tools to estimate power, so everything they did about the chip design was low power to make sure they hit their 1 watt target. When they got the first chips back from the fab (VLSI, if I remember right), they found they had massively overachieved, the ARM1 prototype dissipating only 0.1 watts.

      The early processors were tested in a BBC Micro second processor box, but the real goal was to put them in their new computer, the Archimedes.

  3. More like 34 years by doghouse41 · · Score: 2

    Strange - I can recall discussions of the ARM chip at university back in the early 80's. Either that makes be ten years younger than I though :-) - or someone has their dates wrong.

    As I recall (and correct me if I'm wrong) there was a company called Acorn Computer's which produced the BBC Micro - a 6502 based machine.
    The 6502 was long in the tooth even in those days (dating back at least to the Commodore Pet ca. 1976).
    RISC was flavour of the month in those days, so they set out to create their own RISC based architecture for the next generation of BBC Micro (the Archimedes).

    No doubt they had a little help from the local technical college (aka the Cambridge University computing department)

    1. Re:More like 34 years by mrbester · · Score: 3, Informative

      ARM themselves incorporated in 1990 (hence the 24 years). However, you are correct that Acorn chips predated the company.

      --
      "Wait. Something's happening. It's opening up! My God, it's full of apricots!"
    2. Re:More like 34 years by BasilBrush · · Score: 4, Interesting

      The 6502 was long in the tooth even in those days (dating back at least to the Commodore Pet ca. 1976).
      RISC was flavour of the month in those days, so they set out to create their own RISC based architecture for the next generation of BBC Micro (the Archimedes).

      It was still an odd decision to design their own CPU for the successor to the BBC Micro. A more obvious and less risky move would have been to use a 68000 series CPU as a successor to the 6502.

      I think it's because there were so many Cambridge academics at Acorn. They made a RISC processor because it was an interesting project which was then at the cutting edge of computer science.

    3. Re:More like 34 years by johnw · · Score: 2

      It was still an odd decision to design their own CPU for the successor to the BBC Micro. A more obvious and less risky move would have been to use a 68000 series CPU as a successor to the 6502.

      IIRC, they experimented with a chip called the 32016 (or 16032) as a possible successor to the 6502, before deciding to start again from scratch and design their own.

      All the 2nd processors for the Beeb - Z80, 6502, 32016 or ARM looked exactly the same from the outside, although when you opened them up the Z80 and 6502 were mostly air, whilst the ARM prototype was stuffed to the gunwales. It didn't even have go-faster stripes or a front air dam.

      The odd thing was, early ARMs seemed to manage to produce much more bang for your MHz than x86 chips. An 8 MHz ARM2 ran rings around a 25 MHz 80386. What let them down then was the lack of a floating point co-processor. Later on the relationship seemed to reverse.

    4. Re:More like 34 years by Anonymous Coward · · Score: 4, Informative

      They considered and rejected the 68000 option. The Atari ST and Commodore Amiga were already dominating the market. A 68000-based Acorn system would have no advantages over those while being "late to the game". They figured that they basically needed to leapfrog the 16-bit systems in order to survive.

      Unfortunately, by the time the Archimedes came out, the computing world was standardising around the IBM-compatible PC, and even the Archimedes' superior performance compared to PCs of that era (about the time the first 386 systems appeared) couldn't save it (Atari and Commodore didn't fare much better).

      The irony is that the (seemingly-harebrained) decision to design their own CPU (thus ensuring incompatibility with everything else on the planet) on a shoe-string budget ended up hitting the jackpot. The "sane" approach of using a popular chip (680x0, 80x86) would have relegated them to the history books, alongside 5.25" floppies and dBase III.

    5. Re:More like 34 years by Alioth · · Score: 2

      They did it because they couldn't find a satisfactory chip for the machine they wanted to make. They wanted low and reasonably predictable interrupt latency - and remember, these were the days when CPUs for personal computers took between 3 and 20 clock cycles per instruction, and no cache - they wanted to maximise the use of memory bandwidth. The 6502 for instance typically was in a computer with 150ns memory, but would at full speed in a BBC Micro only fetch something from memory every 1000ns (fastest instruction 2 cycles). They looked at the National Semi 32016, but that had a multiply instruction that would take a staggering number of clock cycles (over 100!) which couldn't be interrupted, which would lead to very bad memory bandwidth utilization, unpredictable and poor interrupt latency. Steve Furber said in one of his talks that the interrupt latency was so poor with the 32016 they would only be able to support single density floppy discs without needing additional hardware (i.e. added cost) to buffer the data.

      They were inspired by the simple design of the 6502 and decided they could do something similar but 32 bits. Hence the ARM. When the ARM came out most of its instructions would execute in a single CPU cycle (versus the 68000, which would often take 8 cycles or more), and had very low interrupt latency. I remember using a PC emulator on an original ARM system (an Archimedes) running at something like 8MHz. The emulator would run faster than the original IBM PC despite being on a computer with less than double the clock speed and having to emulate not just the CPU but the screen and other peripherals.

  4. The Little Chip That Could by spaceyhackerlady · · Score: 5, Interesting

    I've always thought ARM was a cool design. Simple, minimalist, sort of a latter-day PDP-11, one of those canonical architectures that just works. Simple chip, not many transistors, low power, good chip for mobile devices. It seems so obvious in retrospect. Especially since that's not what the designers had in mind. They were designing a simple chip because they only had a couple of people and that was all they could afford.

    In one of the later scenes in Micro Men there is a whiteboard in the background with the original ARM requirements, right down to the barrel shifter.

    ...laura

    1. Re:The Little Chip That Could by cold+fjord · · Score: 4, Interesting

      "Perfection is finally attained not when there is no longer anything to add but when there is no longer anything to take away..." -- Antoine de Saint Exupéry

      A similar point was made about the tight resource constraints of the early Macintosh, and how they created a strong incentive to make use of the toolbox, doing things "the Macintosh way." That paid many dividends over the years.

      --
      much of left-wing thought is a kind of playing with fire by people who don't even know that fire is hot - George Orwell
  5. Going back a little further... by flightmaker · · Score: 4, Informative

    A couple of years ago I donated my Acorn System 1 to the Museum of Computing in Swindon. It was on their Most Wanted list! I learned rather a lot with that machine, hand assembling machine code.

  6. Lesson by Tablizer · · Score: 2

    The lesson is to be a light-handed source of standards and building-block supplier instead an All-Encompassing Conglomerate who tries to rule standards from head to foot.

    Heed the warning, Google, Oracle, and Apple. (Too late for MS.)

  7. ARM also helped Apple survive by mveloso · · Score: 5, Informative

    As a note, back in the day Apple stayed afloat by selling its stake in ARM.

    1. Re:ARM also helped Apple survive by johnw · · Score: 2

      which was the reason ARM was founded.

      Hardly - the ARM had gone through several generations and been used in a number of other products before the Newton came along.

  8. Re:no wrong dates by Tough+Love · · Score: 2

    None of the dates are wrong. You're right that ARM was around in the 80s, but they weren't designing chips at the time.

    Nonsense. ARM started designing chips in 1983

    --
    When all you have is a hammer, every problem starts to look like a thumb.
  9. Good that someone's competing with Intel by Rising+Ape · · Score: 4, Insightful

    As someone who had a BBC Micro as his first computer (lovely machine for tinkering), it's nice to see the descendants of Acorn survive the juggernaut of the PC and x86. And long may it continue, the last thing we need is a vertically integrated colossus like Intel dominating everything, no matter how good their PC processors are.

  10. No mention of the Archimedes or RISC PC? by wonkey_monkey · · Score: 4, Interesting

    ARM architectures were already in use before ARM the company came into being and went into making mobile processors. They were the CPUs for the Acorn Archimedes and Risc PC.

    Ah, I still remember that heady day at Acorn World in 1996 (I think it was), riding the train back clutching my precious StrongARM (not made by ARM themselves, apparently) upgrade. The unimaginable pow-ah!

    Later upgrades put RAM on the CPU's daughterboard because the bus become the bottleneck.

    Somewhat sadly neglected, my Risc PC now gathers dust in a damp garage, but it made me the aspiring-to-efficiency programmer I am today.

    --
    systemd is Roko's Basilisk.
    1. Re:No mention of the Archimedes or RISC PC? by newcastlejon · · Score: 2

      Somewhat sadly neglected, my Risc PC now gathers dust in a damp garage, but it made me the aspiring-to-efficiency programmer I am today.

      And mine turned me into the vitriolic why-the-fuck-doesn't-this-modern-crap-work-as-well-as-that-twenty-year-old-Acorn-in-the-loft?! bastard I am today.

      Horses for courses, eh?

      --
      If God forks the Universe every time you roll a die, he'd better have a damned good memory.
  11. Inevitable... by sootman · · Score: 2

    ... once they became "powerful enough" and portability mattered. Same way that Intel won on the desktop, really -- compared to mainframes, they were small enough to fit into a useful spot (literally and figuratively) and became powerful enough to be REALLY useful, not just occasionally handy.

    But chips themselves don't sell devices -- Intel desktops sold more and more as the OSs and apps got better and better, and it's the same thing with the iPhone and similar devices. Would a 160x160 monochrome Palm Pilot (if it still existed today) sell in iPhone-esque numbers if it had a multicore, gigahertz-plus CPU? The chip makes the product possible, and better products make people want more chips.

    --
    Dear Slashdot: next time you want to mess with the site, add a rich-text editor for comments.
  12. And so where is the archimedes by sugar+and+acid · · Score: 4, Informative

    The article skipped over the whole development of the arm processor. It wasn't developed for the newton, the original architecture was for the acorn archimedes risc based computers, launched in 1987.

    The key difference that set Acorn apart from every desktop PC type computer manufacturer at the time, is they went down the road of actually designing their own processors for the PC market. This is instead of using one from Motorola or IBM

    I think what set the ARM apart going forward was they used modern for the time CPU design principles, but they aimed for a lower end consumer grade market instead of the higher end mainframe/server/workstation/supercomputer market. Because of this they were all about getting the most performance from cheaper slightly older chip fab technologies. All of these ultimately meant that the design constraints imposed early on translated well to mobile applications.

  13. theregister does it better by another_gopher · · Score: 3, Informative

    Tony Smith's articles on the history of micro-computers does this far better:
    http://www.theregister.co.uk/2012/06/01/acorn_archimedes_is_25_years_old/

  14. Most important part... MIPS didn't compete. by evilviper · · Score: 5, Interesting

    There's one simple reason ARM has a strangle-hold on smart phones and tablets... For years, when such devices were being developed, MIPS Technologies was in a shambles. They were reeling from losing SGI, going IPO, and going through the processes of getting acquired by a string of several different companies. They've basically be AWOL this whole time, handing the upstart new market to ARM on a plate.

    MIPS is still competitive. They've got extremely low power processors, multi-core 1GHz+ processors, and they've always been more efficient (higher DMIPS/MHz) than ARM. Despite their virtual absence, they're still used extensively in embedded systems... Your printer, WiFi AP/router, many set-top boxes, etc. They used-to have a dominant lead over ARM, selling something like 2/3rds of all embedded CPUs, but they simply fell apart and ceded the market to the competition. They're even the cheaper option... The first $100 Android ICS tablet found in China was MIPS (not ARM) based, and China's ministry of science keeps developing faster MIPS processors for domestic use, including supercomputers.

    If they had competed, it might be MIPS in every smart phone. Even now, if they get back on-course, they could pose a real challenge to ARM, and driving prices down, and dividing the market, as Intel is trying to do with little success.

    No story that claims to tell how ARM came to dominate is even remotely complete without a good paragraph about how MIPS, their biggest competitor, stopped competing and nearly GAVE them the market.

    --
    Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  15. Re:Fabs cost gazillions... by MouseTheLuckyDog · · Score: 4, Insightful

    Except when you include the pofits for making ARM chips from Qualcomn, Apple ( if Apple had actually seperated out their chip making division, ), Samsung, Allwinner etc. that number changes drastically.

    The only company making money off Intel chips is Intel there are many companies making ARM chips and you have to include the companies making the chip.

  16. Re:Most important part... MIPS didn't compete. by Darinbob · · Score: 2

    MIPS wasn't just failing to compete, it was in a very rough shape after its largest company left. For a long time MIPS product lines were about faster and faster chips. You can not just take a high performance chip and scale it down easily without a redesign. MIPS did scale down but it took it some time.

    Nokia went with ARM because it was tiny, cheap, and low power; perfect for a UI on a handheld and that's what saved ARM more than the Newton did.

    Both ARM and MIPS both cover low and high end embedded systems, but ARM started with low end and grew up, whereas MIPS started with higher end and grew down.

  17. You can get there from here by dbIII · · Score: 2

    Considering how Intel managed to go from NetBurst (massively power-hungry) to Haswell

    They didn't. It grew out of a different project. NetBurst was a dead end.