Slashdot Mirror


ARM Launches Cortex-A5 Processor, To Take On Atom

bigwophh writes "ARM launched its new Cortex-A5 processor (codenamed Sparrow) this week, and while it's not targeted at the top end of the mobile market, it is a significant launch nonetheless. The Cortex-A5, which will likely battle future iterations of Intel's Atom for market share, is an important step forward for ARM for several reasons. First, it's significantly more efficient to build than the company's older ARM1176JZ(F)-S, while simultaneously outperforming the ARM926EJ-S. The Cortex-A5, however, is more than just a faster ARM processor. Architecturally, it's identical to the more advanced Cortex-A9, and it supports the same features as that part as well. This flexibility is designed to give product developers and manufacturers access to a fully backwards-compatible processor with better thermal and performance characteristics than the previous generation."

176 comments

  1. Press Release by Anonymous Coward · · Score: 0

    The summary reads like a press release. Still, it's good to see that Intel is facing competition, be it from AMD or ARM.

    1. Re:Press Release by Paladin128 · · Score: 4, Informative

      And it's full of misinformation:

      1) The A5 is not meant to take on Atom. The A9 is.
      2) The A5 is not architecturally identical to the A9. The A9 is an in-order, multi-issue core. The A5 is an out-of-order, single-issue core. The only thing similar is it has the Cortex A-series ISA.

      What the A5 is is a CPU that completely obliterates the ARM11-derived cores, used in everything from NVIDIA Tegra to the Nintendo DS. It's an update of the ISA, and a more capable core, with better thermals. That's it. Whereas every low-end smartphone now has the same damn QualComm ARM11-based core, in a year, they'll all have the A5.

      --
      Lex orandi, lex credendi.
    2. Re:Press Release by Hal_Porter · · Score: 2, Informative

      Actually if Qualcomm has their way all the smartphones will be running a Qualcomm Snapdragon with a Qualcomm Scorpion CPU, their superpipelined version of the Cortex A9.

      A Snapdragon should run at 1 GHz (Cortext A9 is 600 MHz on a comparable process), from what I've read the A5 will be 480 MHz on a 40nm process.

      So the A5 is aimed at cheaper devices than the Snapdragon. Of course the A5/A9 are presumably available to all ARM licensees whereas the Snapdragon is as far as I can tell only going to be manufactured by Qualcomm.

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
    3. Re:Press Release by Hal_Porter · · Score: 1

      Oops. The Snapdragon is a superpipeline Cortex A8. It's not really clear how an Cortex A9 would compare against a Snapdragon.

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
    4. Re:Press Release by TheRaven64 · · Score: 1

      If you look at the ARM press wibble, then you'll see that they make a distinction between 'smartphones,' which are things like the iPhone, Palm Pre, N900, and so on, and 'feature phones' which are what everyone else thinks of as smartphone (smaller screens, but capable of running user-installed apps, come with a web browser, may support WiFi + SIP, and so on). The A5 is aimed at the feature phone and 'dumb phone' markets, the A8 and A9 are aimed higher.

      The big advantage of the A5 over the ARM9 and ARM11 cores used in these phones currently is that it supports exactly the same instruction set as the A8 and A9. That means that you can run the same OS on your entire phone lineup and same basic suite of userspace programs, just adding extra ones on the ones with the faster CPUs. The big advantage that the A5 has over the A8 and A9 (including the Snapdragon) is that it is under half the price. A $40 A8 SoC is not much in something like an iPhone, but at the (much larger) lower end of the market that is getting on for half of the sale price of the phone.

      Oh, and the A8 goes up to 1GHz. Things like Freescale's i.MX515 ship at this speed. The A9 is designed to scale up to 2GHz. The Snapdraggon is quite a nice A8 implementation, but it's not particularly exceptional.

      --
      I am TheRaven on Soylent News
    5. Re:Press Release by Hal_Porter · · Score: 1

      Oh, and the A8 goes up to 1GHz. Things like Freescale's i.MX515 ship at this speed. The A9 is designed to scale up to 2GHz. The Snapdraggon is quite a nice A8 implementation, but it's not particularly exceptional.

      The Snapdragon is not an A8 implementation - it's a custom implementation of the ARMv7 instruction set. Implemented on the same process as n A8 it will run at a 50% faster clock speed and running at the same clock speed it will consume 50% less power.

      http://www.insidedsp.com/Articles/tabid/64/articleType/ArticleView/articleId/238/Qualcomm-Reveals-Details-on-Scorpion-Core.aspx

      Back in 2005, Qualcomm announced that it had licensed the ARMv7 instruction set architecture and was working with ARM to create its own high-performance core based on that architecture. The new core was dubbed "Scorpion," and at the time it was announced, Qualcomm didn't disclose much about it except that it would run at 1 GHz in a 65 nm process and would be customized to provide a high level of performance and energy efficiency in its target mobile applications. Exactly how this combination would be achieved was not revealed, which is typical of Qualcomm; historically, the company has disclosed few details about the processor cores that live inside its chips.

      Then in 2006, Qualcomm announced a new chip platform, "Snapdragon," in which the Scorpion core would be used alongside several other processors and co-processors. According to Qualcomm, Snapdragon will serve a range of high-performance mobile applications, such as high-end smartphones and mobile internet devices. Still, there was little information about the Scorpion core itself.

      In conference presentations this year, however, Qualcomm popped the hood on the Scorpion core and presented a detailed description of the core's microarchitecture and implementation. The Scorpion core is similar to ARM’s Cortex-A8, which also implements the ARMv7 architecture. Like the Cortex-A8, Scorpion is a superscalar, dual-issue machine, and supports the powerful, signal-processing-oriented NEON instruction set extensions and VFPv3 floating-point extensions (referred to collectively on Scorpion as the "VeNum" media processing engine). Scorpion will be supported by ARM's standard software development tools, and Qualcomm expects to offer off-the-shelf multimedia codec software that uses VeNum.

      Although Scorpion and Cortex-A8 have many similarities, based on the information released by Qualcomm, the two cores differ in a number of interesting ways. For example, while the Scorpion and Cortex-A8 NEON implementations execute the same SIMD-style instructions, Scorpion's implementation can process128 bits of data in parallel, compared to 64 bits on Cortex-A8. Half of Scorpion's SIMD data path can be shut down to conserve power. Scorpion's pipeline is deeper: It has a 13-stage load/store pipeline and two integer pipelines—one of which is 10 stages and can perform simple arithmetic operations (such as adds and subtracts) while the other is 12 stages and can perform both simple and more complex arithmetic, like MACs. Scorpion also has a 23-stage floating-point/SIMD pipeline, and unlike on Cortex-A8, VFPv3 operations are pipelined. Scorpion uses a number of other microarchitectural tweaks that are intended to either boost speed or reduce power consumption. (Scorpion's architects previously designed low-power, high-performance processors for IBM.) The core supports multiple clock and voltage domains to enable additional power savings.

      In addition to developing a custom microarchitecture, Qualcomm also customized the core's circuit design and layout in an effort to improve energy efficiency.

      Overall, Qualcomm has made a huge investment in creating a custom implementation of the ARMv7 architecture. By way of comparison, Texas Instruments customized just the

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
    6. Re:Press Release by Goaway · · Score: 1

      The DS does not use ARM11, it uses one ARM9 and one ARM7.

    7. Re:Press Release by Anonymous Coward · · Score: 0

      2) The A5 is not architecturally identical to the A9. The A9 is an in-order, multi-issue core. The A5 is an out-of-order, single-issue core. The only thing similar is it has the Cortex A-series ISA.

      In ARM terminology architecture refers to instruction set, programming model (Machine specific registers, exception model, ...). So yes, both use same architecture (v7). But their u-archictecture - implementation - differs.

      Sorry but A9 is an OoO machine, multi-issue core... don't know what your sources are.

      In fact A5 core is what ARM management was aiming at when they initially started the A9 program : an 11EJ replacement (A8 was still under development at this time). But by unleashing the u-arch, they ended up with a core faster than A8, and they decided to call it A9.

  2. Summary is misleading by fnj · · Score: 5, Informative

    The Cortex-A5 is aimed at phones. The Cortext-A9 is the one aimed at netbooks. The article referenced in the summary makes this clear.

    1. Re:Summary is misleading by BikeHelmet · · Score: 3, Interesting

      I agree - the summary is bad.

      But it's worth noting that according to previous articles, Intel "envisioned" Atoms one day making it into high end phones. This latest move from Arm will prevent that, solidifying their lead.

    2. Re:Summary is misleading by fnj · · Score: 1

      I don't think there was ever any danger of the Atom ever coming close to being efficient enough for a phone; maybe some other hypothetical fantasy in Intel's mind though.

    3. Re:Summary is misleading by rsmith-mac · · Score: 1

      It's on Intel's roadmaps, but bear in mind it's 2+ generations down. You'd be looking at a 22nm Atom at the earliest.

      The A5 will be outdated and replaced by the time Intel gets the Atom in to phones. So the A5 doesn't really change anything.

  3. Love to have one by quantumphaze · · Score: 1

    I would love to have one of these in a "smartbook". Even though it won't run x86 binaries (I use linux anyway) it would be useful enough to let me leave my big arse laptop at home. With hours of battery life I wouldn't need to take a power supply with me.

    So far though the only ARM smartbooks currently available have very limited RAM and disk space. I will have to wait and see what comes out in the next few months.

    1. Re:Love to have one by ozmanjusri · · Score: 3, Interesting
      I would love to have one of these in a "smartbook".

      MIPS rather than ARM, but these things are cheap and look pretty useful.

      EMTEC Gdium Liberty 1000

      • 900 MHz, 64 bits, Loongson 2F CPU by STMicroelectronics
      • 512MB DDR2 RAM
      • 16 GB G-Key removable storage. Up to 4 Hours of Battery Life.
      • 10-inch LCD screen with 1024 x 600 resolution. Slim, soft-touch keyboard, multi-finger touchpad and lightweight at 2.6 lbs
      • Linux Operating System with over 50 Open Source applications including Open Office, Evince, Firefox, Thunderbird, MSN and more
      --
      "I've got more toys than Teruhisa Kitahara."
    2. Re:Love to have one by dwater · · Score: 1

      If battery life is what you want, you might consider one of these :

      http://europe.nokia.com/find-products/mini-laptop

      but I wouldn't put it in the 'cheap' category. They're not available yet, but the battery is supposed to last for a long time...but it uses the Intel Atom :

      CPU and chipset

                      * Intel® Atom(TM) Z530, 1.6 GHz
                      * Intel® Poulsbo US15W

      --
      Max.
    3. Re:Love to have one by quantumphaze · · Score: 1

      That looks nice, though the battery life could be better though.

      Found more info on it. Looks like it uses a modded version of Mandriva. The USB flash as a hard drive replacement is interesting. Only problem is that you will have to buy the special G-key USB flash drives to have them fit nicely in the slot.

      Not bad at all.

    4. Re:Love to have one by Anonymous Coward · · Score: 0

      > * Intel® Poulsbo US15W

      Has Intel actually released working drivers for this thing yet? I don't care if it's Intel's fault or PowerVR's, but having all this *nice* (albeit expensive) hardware with a giant "no Linux here" stamp on it is getting on my nerves.

      The only other options on the horizon or ARM's Mali gpu or Nvidia's Tegra setup. I'm just hoping one of them goes for the non-binary-blob approach.

    5. Re:Love to have one by im_thatoneguy · · Score: 2, Interesting

      Why would you buy that when you can get a 10" Dell mini which runs every x86 app in existence through Windows, Ubuntu Preinstalled or Hackintosh?

      For almost the same price it has:

      Twice as much RAM.
      Twice as fast of a processor.
      Exponentially more software available.
      Twice as much battery life.
      And weighs exactly the same amount.

    6. Re:Love to have one by BikeHelmet · · Score: 3, Interesting

      http://www.alwaysinnovating.com/touchbook/
      http://promos.asus.com/US/1000HE/ASUS/index.html

      Two netbooks with long battery lives.

      There are smaller devices available, which might be nice for lugging around - but keep in mind that the screen and Wifi are still big power draws, so the bigger the batteries the better.

    7. Re:Love to have one by TheRaven64 · · Score: 1

      The Loongson CPU is quite nice, but the 2F is closer to Atom in terms of power usage than an ARM chip (and a bit higher than even Atom). Note the 4 hour battery life, which is pretty poor for a machine in this class.

      --
      I am TheRaven on Soylent News
    8. Re:Love to have one by evilviper · · Score: 1

      Why would you buy that when you can get a 10" Dell mini

      Well, 2X the price would be one good reason... Once you upgrade to the larger battery, solid-state HDD, and including shipping and taxes, you're paying almost 2X the price, most certainly NOT "almost the same price"

      which runs every x86 app in existence through Windows, Ubuntu Preinstalled or Hackintosh?

      If you want Windows, go for the Dell. If you want Linux, you'll barely even notice you're on a different architecture... All the same apps will work. The only big one many people use being Flash, and there are some alternatives for that.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  4. No, it's not... by Anonymous Coward · · Score: 4, Interesting

    The Cortex-A5 is a slight improvement over the MPCore/Arm11/Arm9. That's nice for those who need it, but it's miles away from the speed of a Cortex-A9, which is really what's going to be needed to battle Atom.

    And since the A9 has announced by ARM quite some time ago, this posting should have been written then not now.

    In reality, it's not clear which niche the A5 is going to occupy. It's probably going to be useful in lower end smartphones only, since current higher end models are already using the faster A8.

    1. Re:No, it's not... by Locutus · · Score: 4, Interesting

      the Cortex-A8 is out now on the 65nm process as are all the other low power device CPU's except Atom. Atom is currently on 45nm to get in the ballpark as the others but power usage is still pretty high. Cortex-A8 on 45nm should be in the pipeline soon and along with it, Cortex-A9. Those are going to shack the Atom up on price/watt and performance/watt. This is why Intel is moving Atom to 32nm ASAP but it's very expensive for them because they have to price the Atom low while at the same time use very expensive 32nm process space which they normally use for high profit desktop/server CPUs. So in 2011, along comes Cortex-A5 on 40nm so Intel would have to start looking at 2?nm processes to keep competing. I believe the ARM dude talks about this somewhat.

      Size is a big deal and right now, Cortex-A8 on 65nm is rather large for smart phones. they pack some decent power for netbooks so I'm not sure what the delay is on that front. Cortex-A9 on netbooks would be very nice but I think they are just sampling now so it won't happen til next year( 2010 ).

      ARM is a thorn in both Microsoft and Intel's sides and there is probably massive amounts of pressure on OEMs and manufacturers to stay away from it. Atleast on the netbook side. Remember, the head of the Thai Manufacturers Association said they fear Microsoft when talking about Linux on netbooks. ARM is an enabler for Linux so it too is a threat to Microsoft. But I sure hope the market gets to make the choice some how, some way.

      LoB

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
    2. Re:No, it's not... by svirre · · Score: 1

      ARM builds even its high-end cores as softcores these days. It is the implementor, not ARM who decides which process node to use.

    3. Re:No, it's not... by TheRaven64 · · Score: 1

      ARM does not make chips, they design them. The process technology is up to the licensees. Some are using 45nm now, and have been sampling 32nm for a few months with plans to ramp up production in early 2010.

      --
      I am TheRaven on Soylent News
    4. Re:No, it's not... by ndogg · · Score: 1

      And since the A9 has announced by ARM quite some time ago, this posting should have been written then not now

      Yeah, it has. This article is a dupe.

      --
      // file: mice.h
      #include "frickin_lasers.h"
    5. Re:No, it's not... by Locutus · · Score: 1

      did I say that ARM inc made the chips somewhere? I was speaking more to the fact that ARM inc's designs are doing well on larger die processes, there's room for even better performance and power sipping along with Intel being forced to use die shrinkage to even play in the game.

      After reading the story on the A5, it sounds like the design documents for the design also relate to what process size is used. The A5 was said to be designed for 40nm process. So while the implementors may have a choice, they might have more work to do if they want to use a different process than the delivered design docs cover. That's what it sounds like from the A5 article.

      LoB

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
    6. Re:No, it's not... by Locutus · · Score: 1

      I was talking more about the "ARM" platform than the company so yes, if people don't know, ARM inc doesn't build the chips but only sell the design to companies who produce chips from those designs. Saying that, I think that ARM inc's design documents somewhat tie it to a process size or that's what I got from the Cortex-A5 article.

      As far as some ARM based chips on 45nm now goes, which ones and who's using them? I thought TI was still 65nm and only read that Samsung was eventually to release a 45nm Cortex-A8 but haven't seen it anywhere yet. Freescale is on 65nm too. Any 45nm Cortex-A8 and A9 chips would be great for smartphones, smartbooks, and netbooks. 32nm would really be fantastic. Got anything we'll be seeing this year?

      LoB

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
  5. Good news for future iphone by not-enough-info · · Score: 4, Interesting

    Looks like the Cortex-A5 has 50% more performance while using 1/3rd the power of the current generation ARM11 found in the iPhone. As a game developer this makes me hopeful that we'll see cellphones as a gaming platform without sacrificing useful battery life.

    --
    ---k--
    </stupid>
    1. Re:Good news for future iphone by Anonymous Coward · · Score: 2, Informative

      Be careful not to buy marketing bullshit.

      Most figures you find in the TFA are in terms of DMips, which is an awful metric to measure general CPU performance. Imagine how easy it is to optimize a loop which contains 100 instructions, which is 100% branch predicted and 100% cache hit at L1 D/I. This does not translate at all to web browsing performance which is thrashing (at least) your L2.

      In term on u-architecture, we are looking at something similar to ARM11 on newer processes.
      TFA talks about:
      +80% DMips compared to ARM9,
      +20% DMips compared to ARM11.
      But this metric clearly factors frequency: ARM9 was 1.1 DMips/MHz and ARM11 1.25 DMips/MHz

    2. Re:Good news for future iphone by dwater · · Score: 1

      The phone I have - Nokia N900 - uses the ARM Cortex A8. I wonder how the processors compare...

      --
      Max.
    3. Re:Good news for future iphone by AndyS · · Score: 1

      The 3GS is a Cortex A-8, which would be faster than the A-5.

      It's clocked at 600Mhz and is dual issue. As well as that they have a beefier 3d chip as well.

      The A-9 is more exciting as it is multi-core and out of order.

    4. Re:Good news for future iphone by TheRaven64 · · Score: 2, Informative
      The A5 is, from a marketing standpoint, a cut down A8. It supports all of the new instruction set extensions introduced with the A8, and is intended to be binary-compatible, but is a lot slower. It is also a lot cheaper. A decent A8 SoC costs around $40, but you can expect A5-based cores to sell for well under $20.

      From a technical standpoint, it's quite a different design. The A8 is an in-order superscalar design, with a 13-stage pipeline (and a 10-stage SIMD pipeline). The A5 is an in-order single-issue design with an 8-stage pipeline. While the A8 comes with NEON (SIMD) and floating point support as standard, they are optional in the A5 (which lowers costs, but cripples floating point performance if you choose not to build them; for some applications, the cost is the more important factor because most float-heavy workloads will run on a separate DSP core anyway). It looks like the A5 has the A8's branch predictor, which is much better than the ones in the ARM11 and earlier cores, but with some minor tweaks to adjust for the pipeline differences. The A5 supports 4KB to 64KB of on-die L2 cache, while the A8 supports up to 1MB. I'm not sure how much L2 cache the OMAP3430 in the N900 comes with - TI's documentation is oddly silent on that topic - but reducing the cache can reduce the die size (and, therefore, cost) considerably at the expense of performance.

      Basically, the point of the A5 is to allow you to run the same software on much cheaper devices that you do on devices with A8 or A9 cores, just much slower. A phone with an A5 would probably have a smaller screen and little expectation of running apps in the background, but would run one application reasonably, while its big brother with an A8 could happily multitask a few, but they would both use the same binary (and the same OS kernel).

      --
      I am TheRaven on Soylent News
    5. Re:Good news for future iphone by drinkypoo · · Score: 1

      It looks like the A5 has the A8's branch predictor,

      If it's not superscalar, why does it need a branch predictor? It only needs to know when the first instruction fails a cache hit, so that any results can be held.

      Basically, the point of the A5 is to allow you to run the same software on much cheaper devices that you do on devices with A8 or A9 cores, just much slower.

      It doesn't sound like it is necessarily slower, either, since you can get the same functions as the A8.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    6. Re:Good news for future iphone by TheRaven64 · · Score: 4, Informative

      If it's not superscalar, why does it need a branch predictor? It only needs to know when the first instruction fails a cache hit, so that any results can be held.

      Uh, what? You need a branch predictor because it's pipelined. It has an 8-stage pipeline, which means that it doesn't know the result of an instruction until eight cycles after it was issued. If you come to a conditional branch, you need to decide whether to take it or not. For example, if you have some C code saying something like 'if (a == 12)' then you can't decide whether to jump to the else block until you've computed the value of a, which will be 8 cycles in the future. Without a branch predictor, you just stall for 8 cycles and do nothing. Given that compiled code averages about one branch every 7 instructions, that means that you would be spending most of your time doing nothing.

      The branch predictor makes a guess about which branch to follow, i.e. whether to continue to the body of the if statement or jump to the else block. It then starts executing whichever branch if guesses. If it guesses correctly, then the pipeline stays full. If it guesses incorrectly, the pipeline is flushed and none of the results of the instructions after the branch missprediction are committed. The processor resets itself to the branch and continues down the right track.

      The branch predictor in the A5 gets about a 95% hit rate, so on average you have to flush the pipeline every 20 branches, which isn't too bad in terms of overhead. Superscalar makes no difference to the need for branch predictors. A superscalar chip is one that can issue more than one instruction per cycle. That means that independent instructions can be run side by side. This is quite nice on ARM chips, where a lot of instructions are predicated, as you can run both versions in parallel and only commit the one that was meant to be taken, but it's completely independent of the branch predictor.

      It doesn't sound like it is necessarily slower, either, since you can get the same functions as the A8.

      Nonsense. By that logic Atom is as fast as a Core 2 because you have the same instruction set on both. The A5 and A8/9, due to massive implementation differences, will execute different numbers of instructions per clock and not run at the same clock speed. The A5 will execute far fewer and runs at a lower frequency.

      --
      I am TheRaven on Soylent News
    7. Re:Good news for future iphone by Anonymous Coward · · Score: 0

      I'm not sure how much L2 cache the OMAP3430 in the N900 comes with - TI's documentation is oddly silent on that topic

      16K L1 I-cache, 16K L1 D-cache, 256K L2

      http://focus.ti.com/docs/prod/folders/print/omap3530.html
      http://focus.ti.com/paramsearch/docs/parametricsearch.tsp?family=dsp&sectionId=2&tabId=2218&familyId=1525&paramCriteria=no

    8. Re:Good news for future iphone by drinkypoo · · Score: 1

      The A5 and A8/9, due to massive implementation differences, will execute different numbers of instructions per clock and not run at the same clock speed. The A5 will execute far fewer and runs at a lower frequency.

      For now. But if they do implement it in 40nm they might get the clocks way up to compensate for the inability to retire as many instructions per cycle.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    9. Re:Good news for future iphone by TheRaven64 · · Score: 1

      Not really. People are already shipping A8 cores on 45nm and ARM has deals with IBM and Global Foundries for 32nm and 28nm processes. But it's irrelevant, because you won't run an A5 at a high clock frequency if you need speed, you'll use an A8 or A9, because it will consume less power for the same throughput.

      --
      I am TheRaven on Soylent News
    10. Re:Good news for future iphone by jelle · · Score: 1

      "If it's not superscalar, why does it need a branch predictor?"

      Because it has a pipeline and without a predictor a branch means a pipeline stall until the branch comes out the execution stage. With a predictor, even a simple one, it means a pipeline flush only when the predictor is wrong, which means you can gain a lot of cycles with even a very simple predictor.

      --
      --- Hindsight is 20/20, but walking backwards is not the answer.
    11. Re:Good news for future iphone by raddan · · Score: 1

      Are opcodes still hardwired in ARM, or are they using microcode now? I know a little ARM assembly from hacking my ARM7TDMI (iPod mini), and found that ARM was really and interesting and weird (coming from MASM on IA-32) architecture, and quite a bit easier to use. But I remember seeing product documentation claiming that hardwired instructions were one of the reasons why they were able to keep their transistor counts (and thus price) down.

    12. Re:Good news for future iphone by TheRaven64 · · Score: 1

      I honestly don't know. It wouldn't surprise me, given the attention to detail that goes in to an ARM core design. It was certainly true of the ARM 2, but I can't find anything definitive one way or the other. The StrongARM, I believe, had microcode, but that was designed by Digital, not by ARM (then acquired by Intel, who managed to turn it from the highest-performance ARM variant to the lowest in a couple of years).

      Modern ARM cores have a series of pluggable instruction decoders, which helps keep the power consumption down. The decoder in an x86 chip is very complex, because it has to handle variable length instructions in a variety of formats, and support everything from the 8086 onwards. With an ARM chip, you have, for example, the Jazelle decoder, which handles Java bytecode as its instruction format, the Thumb 2 decoder, which handles a dense 16/32-bit instruction set (variable length, but with only two choices for length), and the 'native' ARM instruction set. You need an instruction or an interrupt to trigger the switch between them, and when that happens the core will power down the old decoder and start up the new one. Given that, traditionally, the decoder is the one bit of the core that you can't power down, that helps a lot in terms of performance. This design also helps in terms of keeping the decoders simple. While Intel and AMD have just added new instructions to their ISA, ARM has opted instead to define completely new instruction sets. This means that the decoders for the new instruction sets can be completely modular. It's much easier to decode two simple instruction sets than one very complex one.

      --
      I am TheRaven on Soylent News
    13. Re:Good news for future iphone by BOFHelsinki · · Score: 1

      Good post. I'd like to add one detail where A5 may be categorically "better" than A9: the new L2 cache controller with multiple outstanding transactions. It's a boon for real-world apps that need to rapid fire to large essentially random datasets (like Web browsers do), especially when used in an in-order core.

    14. Re:Good news for future iphone by Anonymous Coward · · Score: 0

      The A5 supports arbitrarily sized L2 caches. It supports up to 64 kB of L1 cache per core. More is not feasable in current technology nodes anyway at these frequencies.

      Most of what is written about the A5 from a technical point of view in the slashdot comments is quite wrong.

    15. Re:Good news for future iphone by hattig · · Score: 1

      iPhone 3GS uses an ARM Cortex A8 at 600MHz.

      It's the older iPhones that use ARM11 at 412MHz.

      As the A5 is a lesser CPU than the A8, I expect the iPhone to never utilise it, but to migrate to the A9, and potentially dual-core A9, with the next release in July next year.

  6. too late? by Anonymous Coward · · Score: 0

    The Cortex-A5-based devices will be here in 2011 (according to the charts).
    Now, devices with Atoms are already here for a good year.
    How do current ARM CPUs stack up against wimpy Atoms?

    1. Re:too late? by Narishma · · Score: 1

      The A5 isn't competing with the Atoms. It's meant to replace the ARM9s and ARM11s found in a lot of devices from phones to the Nintendo DS.

      --
      Mada mada dane.
  7. So this is why ARM and Global Foundries... by freak132 · · Score: 2, Informative

    So this is why ARM and Global Foundries recently made a deal. ARM's Cortex-A5 is going to be built on a 40nm and Global Foundries already has that equipment, with AMD working hard to advance to the next node that frees up a lot of manufacturing power for ARM to use. Officially it was for Cortex-A9 at 28nm but what's to stop other stuff from being done in the shadow of the deal?

    1. Re:So this is why ARM and Global Foundries... by TheRaven64 · · Score: 1
      Probably not. The A5 is designed to be cheap, and you don't produce your cheapest chips at the most expensive process technology you have. ARM's marketing stuff currently suggests producing it on a 40nm technology.

      Remember, ARM doesn't make chips. The deal with Global Foundaries was to allow ARM to sell designs and fab space in the same bundle (they do this with IBM and a few other chip manufacturers too), so when you want to make a custom SoC you go to ARM and say 'I want to make 10,000 custom chips based on the Cortex A8.' They then give you a single contract to sign and a load of HDL code. You integrate your custom components (DSPs or whatever) and send it back, and an ARM partner manufactures your chips. Bigger licensees, like TI or Freescale, just get the designs and produce the chips themselves.

      At 40nm, the chip runs at a little under 480MHz. This will be quite a bit slower than a Cortex A8 at this speed, but it should be much faster than an ARM9 and a bit faster than an ARM11 core at this speed. My current phone is right at the bottom of the market for what would be called a smartphone and comes with a 220MHz ARM9 core (on a 180nm process, I think, possibly 130nm). This is the kind of device that the A5 is aimed at. You won't see it in a Netbook or a high-end Smartphone, but it's more powerful than the core in the Nokia 770 and about the price of the CPU in things like the N70 family, so you'll see a lot more features on low-end phones.

      --
      I am TheRaven on Soylent News
    2. Re:So this is why ARM and Global Foundries... by drinkypoo · · Score: 1

      Probably not. The A5 is designed to be cheap, and you don't produce your cheapest chips at the most expensive process technology you have.

      Shrinking the process can improve yields, since there's more dies per wafer. If you're chasing low power consumption, you use the smallest process technology you have.

      My current phone is right at the bottom of the market for what would be called a smartphone and comes with a 220MHz ARM9 core (on a 180nm process,

      That pretty much drives the point home, don't you think?

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    3. Re:So this is why ARM and Global Foundries... by freak132 · · Score: 1

      As it stated in the article I linked, ARM signed the deal with GlobalFoundries (GF) to allow GF to access ARM's architecture and process patents so that other companies could use GF to make ARM SoCs. AMD is trying to move to a smaller process as we speak, so in 2011 when the A5 is slated to come out ARM will be able to use a 40nm process when AMD has long since stopped using that equipment (as stated in the second graphic in the original article).

  8. Wifi + LCD, not the CPU by Gothmolly · · Score: 5, Insightful

    Its the Wifi/WWAN chips, and LCD screen which suck up the power, not the CPU. ARM is cool and all (pun intended) but if you make an ARM based Dell Mini 9, you're not going to end up with uber battery life, when you're on Wifi and running the screen bright.

    --
    I want to delete my account but Slashdot doesn't allow it.
    1. Re:Wifi + LCD, not the CPU by Anonymous Coward · · Score: 1, Insightful

      This is talking about smart phones, where the CPU is a significant chunk of the power consumed. And in those cases, the wireless features are relatively efficient (though not great, but they're not normally active 100% of the time), and the backlight and CPU make up the bulk of the power consumed. The more efficient the processor, the happier your battery will be.

    2. Re:Wifi + LCD, not the CPU by Anonymous Coward · · Score: 0

      Are you on crack? Most of the time the expensive chunk is the display or radios. If the display is off, the CPU is most likely in idle or about to go idle. If the radios are on at all (like they usually are for a cellphone), even if you are not using them, they have to periodically wake-up to keep communication alive with the cell towers. If you are using them, then anything the CPU is drawing, while slightly noticeable, will be overshadowed by the radios.

      Now of course, that's not to say that a more power-efficient CPU isn't welcome - it sure is.

    3. Re:Wifi + LCD, not the CPU by mrmeval · · Score: 1
      --
      I'd go on a Vegan diet but the delivery time from Vega is too long. --brownkitty
    4. Re:Wifi + LCD, not the CPU by MemoryDragon · · Score: 2, Insightful

      The main reason why the CPU does not suck power is because most if not all mobile phones use ARM CPU cores. Imagine a mobile phone with an ATOM, shudder...
      You would gain some speed but your mobile phone would need fans :-(

    5. Re:Wifi + LCD, not the CPU by Idbar · · Score: 1

      I know what I'm about to say may not happen, but may make people consider moving to those mobile platforms: While you may be right about power comsumption, the fact that the couldd perform better and even add more core or better video cards using the same power comsumption of current devices makes me hopeful. I'd go for something faster or more powerfull than my current MSi Wind if it cosumes similar battery and I can run several programs at once or faster.

    6. Re:Wifi + LCD, not the CPU by Anonymous Coward · · Score: 0

      Not only fans, but a battery pack larger than the phone itself.

    7. Re:Wifi + LCD, not the CPU by Anonymous Coward · · Score: 0

      so if the cpu uses less power, the screen anf wifi will have MORE TO USE, and last longer, is that not better?

  9. MS by marjancek · · Score: 1

    It's said that Intel has the edge on this fight due to x86 compatibility, but Microsoft can really change things around if they decided to port Win7 to ARM, instead of offering only Windows CE. But considering monopolies, I wouldn't expect that any time soon.

    1. Re:MS by 0123456 · · Score: 5, Insightful

      Microsoft can really change things around if they decided to port Win7 to ARM, instead of offering only Windows CE.

      But considering monopolies, I wouldn't expect that any time soon.

      People generally use Windows on PCs because they have x86 Windows software they need to run.

      How many people have a stack of ARM software to run on ARM Windows? If you're going to need new software anyway, why would anyone in their right mind pick Windows to run it on?

    2. Re:MS by quantumphaze · · Score: 3, Insightful

      It would be best for Microsoft if ARM on the laptop/desktop was a complete flop. Sure, if what others say is true about the portability of Windows internals, Microsoft could release a version of Windows 7 for ARM. But really, what would be the point?

      The biggest strength of Windows is running Win32 apps, and they are all compiled for Win/x86. Microsoft would have to provide development tools that encourage developers to make ARM binaries along side x86 binaries to even have a chance at making it happen.
      Look at the average computer user's software catalogue, you will find many apps (and games) that were bought long ago and would cost money to upgrade to a potential ARM port if the company that made them are sill even in business. Those programs are never going to be ported to Win/ARM. Then there are all the drivers for last years peripheral hardware (assuming that the laptop's hardware is supported) that won't work.

      I don't believe they can do what Apple did either. Apple was able to move to x86 from PPC because the control the hardware and moved their whole product line to it (killing PPC market). Any developers that wanted to stay in business had to port to x86. MS would be introducing a side product that would have a very small fraction of the bigger x86 customer base.

      In the end all that Win/ARM has left is the few open source apps that choose to build an installer for it and the familiarity of the Windows desktop environment.

      It would be in their interest to do everything in their power to make sure this doesn't ever get off the ground. We will have to wait and see what their next move will be.

    3. Re:MS by Zouden · · Score: 1

      How many people have a stack of ARM software to run on ARM Windows?

      It's relatively easy to recompile software for a different architecture, as long as the API is the same. Of course there's no ARM Windows software now, but that would change pretty quickly.

      --
      "A week in the lab saves an hour in the library"
    4. Re:MS by dwater · · Score: 1

      > Apple was able to move to x86 from PPC because the control the hardware and moved their whole product line to it (killing PPC market)

      and losing me as a customer in the process, albeit slowly as s/w became more and more incompatible with PPC. Of course, that wasn't the only reason, but still.

      --
      Max.
    5. Re:MS by marjancek · · Score: 1

      > How many people have a stack of ARM software to run on ARM Windows? If MS ports not only Windows but also Visual Studio then software developers could just [cross-]compile for ARM, Photoshop included.

    6. Re:MS by Anonymous Coward · · Score: 0

      See also the release of Windows NT on the Alpha platform...

    7. Re:MS by Anonymous Coward · · Score: 1, Interesting

      So it took Autodesk years and years to make a 64 bit version of Autocad, because Microsoft forgot to make a Visual studio that could compile a 64 bit program? or Autodesk didn't have the money to upgrade there Visual Studio?

      With open source software it indeed depends on the availability of a compiler, but with closed source software it seems preferable to slap new version numbers onto prehistoric piles of 32-bit code.

    8. Re:MS by jabjoe · · Score: 1

      Ok,
      1) you don't have the source to recompile. It's not like you just have a repository to recompile. It lots of different companies that must work together, and they are only going to do what they see will be profitable. So only a selection defined by what the owners see as profitable will be ported.
      2) the first port of software is the hardest and most Windows software has never been ported. Much of Windows software is written to just one implimentation of the API, so problems go hidden. You'll find old Windows software which should run on a different version of Windows but won't because the API has been reimplimented and isn't 100% the same. Porting would be a nightmare. How ever portable software is more reliable because it's run in a wider range of setup so problems have less places to hide.
      3) The bulk of windows users aren't technical and will never understand why the can't install the software they have and must buy it again.

      Windows for ARM won't happen and Wintel doesn't have the bully power anymore. ARM and other architectures and creeping in with Linux. My bet is with the other architectures Windows loosing its grip with accelerate. Smartbooks might just be the start. Servers are often Linux already, but what if you could have ARM Linux servers, you get massive power savings at lower costs. Windows will stop even being an option. As a Linux and ARM fan it's all very exciting.

    9. Re:MS by bertok · · Score: 2, Insightful

      Microsoft can really change things around if they decided to port Win7 to ARM, instead of offering only Windows CE.

      But considering monopolies, I wouldn't expect that any time soon.

      People generally use Windows on PCs because they have x86 Windows software they need to run.

      How many people have a stack of ARM software to run on ARM Windows? If you're going to need new software anyway, why would anyone in their right mind pick Windows to run it on?

      Because 6 months before you can even buy "Windows 8 - ARM Edition", Microsoft will have released a Visual Studio patch that enables "ARM" as a target alongside the existing x86/x64/Itanium platforms. Both .NET and Java will have runtimes ported as well. Converting 32-bit code from one CPU to another is much easier than going from 32-bit to 64-bit, so it wouldn't take very long for vendors to update their software for it. Also, Microsoft strongarms ISVs into compatibility. For example, it's often hard (or harder) to get "Windows Logo" certifications for software unless it works on various platforms.

      By the time an ARM-compatible Windows is released, there would be thousands of titles compatible with it.

    10. Re:MS by melted · · Score: 1

      >> Microsoft can really change things around if they decided to port Win7 to ARM

      Heard it through the grapevine that this is EXACTLY what they're doing, albeit not in a context you mentioned. A subset of full blown Windows kernel is being ported to ARM (a-la iPhone Mach) as a foundation for their "next" next gen mobile OS.

    11. Re:MS by Anonymous Coward · · Score: 0

      What the fuck are you going on about?

    12. Re:MS by Anonymous Coward · · Score: 0

      Sure there would.

      Firefox, OpenOffice, Apache...

      You think they are going to port thousands of big software, which never were meant to be ported, to ARM in 6 months? Yeah right.

      Photoshop, Autocad and most of the software Winpeople whine about are so large, they possibly cannot be reliably ported in just 6 months.

    13. Re:MS by marjancek · · Score: 1

      That didn't stop Windows from having MIPS, Alpha and IA-64 versions in the past. Plus, it could even take advantage of the enormous number of open source programs that could be compiled for ARM Windows before commercial titles get ported. Don't tell me they won't because wouldn't not profitable; trying to screw Linux is always in Redmon's top priorities.

    14. Re:MS by TheRaven64 · · Score: 4, Interesting

      I've said this before. Aside from games, very little legacy software is CPU-bound. A modern emulator can get somewhere between 50-80% of the host native speed on emulated software, and not all of the code that is running will be emulated. Take a look at a typical Windows application. Most spend at least 50% of their CPU time in system library code. A half-decent emulator will just pass these calls to the native versions of the libraries, so for half of the CPU time you are running native code. A lot of recent Windows applications use some .NET code. This will be JIT compiled to ARM, so it's also native. The remaining code will be emulated, but the number of programs for which this will be too slow is very small.

      Oh, and most people do not have a stack of x86 Windows software. They have one or two Windows programs that they depend on (or, at least, would not abandon without a lot of persuasion). You can bet that an ARM version of Windows would be accompanied by an ARM version of Office, and if MS really wanted to push it then they'd give a free download of the ARM binaries to people who owned the x86 version.

      In terms of C programming environment, x86 and ARM are very similar. C does a terrible job at abstracting the differences between SPARC64 and x86 (for example), but it does a lot better at abstracting the differences between ARM and x86. Most software, unless it uses inline assembly or SSE / MMX intrinsics, is a straight recompile. The SSE and MMX intrinsics can be implemented in terms of NEON or slower scalar operations, so the code will compile, even if it doesn't get the same performance.

      --
      I am TheRaven on Soylent News
    15. Re:MS by TheRaven64 · · Score: 1
      Making a C program 64-bit safe, if it was not designed to be portable originally, is a lot of effort. Porting a C (or C-family) program from x86 to ARM is generally a straight recompile.

      But, really, a port of Autocad is irrelevant. If you're running Autocad, you don't want the CPU with the best power consumption or the best performance per Watt, you want the CPU with the best performance. And, much as I like the ARM architecture, that's not the market it's (currently) in.

      --
      I am TheRaven on Soylent News
    16. Re:MS by MemoryDragon · · Score: 1

      Actually the ARM windows is WindowsCE and that one is currently seriously at a decline.

    17. Re:MS by MemoryDragon · · Score: 2, Interesting

      Apple did not kill the PPC market. IBM did at least the desktop market, one day they decided to give up the PPC desktop processors without telling Apple. Apple did not have a choice, there were new desktop and notebook processors in the pipeline, while IBM busily was working on their high end server processors and was designing console processors for Sony and Microsoft with their old cores.

    18. Re:MS by bhtooefr · · Score: 1

      Except netbooks didn't take off until Windows ran on them. Then, you got a real ultraportable that did everything your desktop did, for $300-400.

      This is true that MS can't effectively subvert the Linux smartbook, but the average person would have to buy a Linux smartbook in spite of Linux. (We won't talk about WinCE smartbooks, other than my saying that MS can't effectively subvert the Linux smartbook.)

      Basically, it's a really, really long battle to get smartbooks adopted, simply because Linux isn't Windows or even Mac OS.

      My prediction: The Linux zealots will buy them and say that they're insanely popular, the RISC OS community will buy them and port RISC OS to them, and then they'll disappear.

    19. Re:MS by Anonymous Coward · · Score: 0

      One word: structure padding.

    20. Re:MS by Anonymous Coward · · Score: 0

      It's your typical BS /. post where they allude to Linux users being virgins, etc. because someone brings out valid arguments that demolish their cherished notions. It's not some hippie like they claim...it's that they can't argue from a solid position the "it's as simple as recompiling" line as it doesn't work terribly well based upon a reflection of the history of things.

      If it were as simple as recompiling, the Alpha, and to a lesser extent, MIPS cpu architectures would've mopped up the floor with X86 on NT- as it was an available choice and they were solidly 2-4 times faster than x86 on anything you put on the machines, whether it was NT or Linux at the time.

      At the time they came out, they WERE a viable architecture, so there has to be some other good explanation in this case. Especially for the Alpha which Microsoft did make a big push alongside Digital to make the move because NT really did shine pretty well on Alpha, so long as the apps were also Alpha versions. Many people that make the remarks that they do on this subject weren't dealing with computers during that time so they wouldn't have anything to relate and can't conceive that the superior arch at the time didn't make it- and it wasn't MS' decision but the market's.

    21. Re:MS by bhtooefr · · Score: 1

      Although, there is something else.

      I don't believe Microsoft pays to do ports of Windows.

      IIRC, ports of Windows to non-x86 architectures are paid for by the processor maker. (That's why Windows 2000 for Alpha was cancelled, Compaq didn't want to pay for it any more.)

      ARM's said they need a port of Windows, too, and there's rumors out there that there's a team at MS porting Windows to ARM... made up of ARM employees.

    22. Re:MS by Svartalf · · Score: 1

      Heh... They kind of dropped all but the x86 versions because the backwards compatibility features of Windows kind of got in the way of selling the other architectures. There was this big push for Alpha as it WAS vastly better than x86- back when NT 3.1 was "king". It didn't go well then because you had to run pretty much most of the applications in emulation, negating most of the advantage the CPU had over X86 machines as it would run that stuff slightly slower than the comparable x86 machines of it's day.

      Don't fool yourselves. The old applications that make Windows compelling is like a huge lead weight placed on Microsoft and it'll sink them if something else gains ascendancy.

      --
      I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
    23. Re:MS by TheRaven64 · · Score: 1

      If you make packed structures on x86, they will require unaligned loads and stores, which are slow (so don't do that). If you do it on a new ARM chip, you get the same. If you do it on a slightly older ARM chip, you get a trap to the OS which fixes up the load. If you do it in x86 code emulated on ARM, then the emulator will turn it into a load-shift-mask sequence (and since ARM instructions get a free shift, this is actually a very quick sequence).

      --
      I am TheRaven on Soylent News
    24. Re:MS by Anonymous Coward · · Score: 0

      MS could invest in doing some kind of dynamic binary translation from x86 to arm that could work for a good part of the software available out there, and if they are indeed interested in going for ARM, I'd think they would have a research team already on it. It's technically quite feasible, specially if you do have the money (which they have) and the brains (which they have, but keep on the r&d division instead of the other more commercial ones :P).

    25. Re:MS by Alioth · · Score: 1

      Unfortunately for Intel (and happily for everyone else) the x86 arch is going to start haunting them. The bit that just figures out how big the next instruction is on an x86 CPU is as large as an entire ARM core. As things get more and more multicore and want to be more and more low power, this will be a ball and chain for them - already they are having to use considerably more expensive processes to make the Atom compete with the Cortex A9.

    26. Re:MS by Anonymous Coward · · Score: 0

      And if I design the ABI for an ARM processor I'm probably going to place some bits slightly differently than on an x86 ABI. Which means that shitty code that fread()s bitmap headers directly will break.

    27. Re:MS by Anonymous Coward · · Score: 0

      I'm sorry to say, but you drank too much of uncle Steve's Kool-Aid.

    28. Re:MS by tepples · · Score: 1

      MS could invest in doing some kind of dynamic binary translation from x86 to arm that could work for a good part of the software available out there

      And once you clock up the ARM CPU to the point where the dynamic binary translation from x86 to Thumb doesn't result in unacceptable slowdown, your CPU might already be consuming as much power as an Atom CPU. So what does that buy you?

    29. Re:MS by cheesybagel · · Score: 1
      If that was the case Apple could have simply bought a license to one of those console designs. The Xbox 360's Xenon triple core CPU, for example, is pretty decent. They could also have commissioned IBM to design processors for them. They had enough volume to do it. They did not because using Intel processors was more cost effective.

      Apple killed the PPC market when they sank the PPC Mac clone market (e.g. Power Computing), forcing companies like Motorola and even Be (which used hardware based on a PPC CHRP platform) out of the market. Apple could not compete in an open hardware market. The clone manufacturers often had superior hardware (Power Computing, UMAX) than Apple did.

    30. Re:MS by cheesybagel · · Score: 1
      Applications? If they just wanted an OS, any OS, they might as well use Linux. Having Windows with no decent applications to speak of provides little help. DEC and SGI had to figure that out the hard way.

      Apple solved that problem by making their own applications.

    31. Re:MS by cheesybagel · · Score: 2, Insightful

      Now that is silly. 8086 had like 29 thousand transistors. 80386 had some 275 thousand transistors. The StrongARM SA-110 processor had 2.5 million transistors, more transistors than a 80486, and that was years ago. x86 decoding is hardly the issue people think it is. Not at todays transistor budgets. Intel has surprised a lot of people with Atom and they should be able to shrink it further.

    32. Re:MS by MemoryDragon · · Score: 1

      As if the xbox processor would have made sense, the xbox processor is basically three g4 cores with some simd units attached on top, nothing fancy and not even that fast compared to amds and intels offerings, why should apple pay for the next processor generation if they can get it for free mostly on intels side.
      The powerpc market was also killed by ibm not really enforcing the desktop anymore. After the G4 and G5 they did not have any new designs in the pipeline and even their own workstation offerings are not that interesting anymore, and outside of that no one really enforced the PowerPC. It was mostly IBMs fault that they moved away from the desktop not Apples. It probably was not funny for Steve as well, to finally recognize, that IBM has nothing in the pipeline regarding future desktop and notebooks.

    33. Re:MS by cheesybagel · · Score: 1

      Why would IBM design new desktop processors when they had no desktop OS of their own, and the only desktop OS of interest for PPC was done by Apple, who were not interested in PPC anymore? I guess it is easier to blame IBM and Motorola than looking at your own issues. I find it interesting you give a blank check to Apple for taking their own financial interests at heart, while thinking IBM got to survive all these years by making products for third parties with no viable market in sight.

    34. Re:MS by evilviper · · Score: 1

      By the time an ARM-compatible Windows is released, there would be thousands of titles compatible with it.

      If Microsoft was anywhere near that capable, and insightful, people wouldn't be endlessly complaining about how lousy Windows is.

      Ask DEC how well their non-x86 version of Windows worked out...

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    35. Re:MS by MemoryDragon · · Score: 1

      Hen and egg problem, I personally think Apple simply was not enough to keep the PowerPC floating, lets face it Wintel simply killed it. IBM is slowly moving away from the entire hardware business, my personal guess is the next division which will be axed and sold off will be the processor division, and outside of the server space absolutely no one was interested in the power pc anyway, it would have taken more than simply apple to pull off the power pc as new desktop processor standard, if there was a chance at all. Not even the vastly superior Alpha was able to break into Intels domain, and the PowerPC never was that much superior to begin with, speedwise.

    36. Re:MS by tepples · · Score: 1

      Applications?

      An overclocked ARM running an x86 emulator has applications. Atom also has applications. So what's the point in running an x86 emulator on an overclocked ARM instead of just going with Atom in the first place?

    37. Re:MS by quantumphaze · · Score: 1

      Apple solved it by discontinuing their PPC line, leaving little choice for developers to go with it. MS doesn't have such an option. No sane developer will make and test an ARM binary without a market. And there is lots of x86 specific code (optimisations, ect.) that can't be ported without significant investment.

      An x86->ARM emulation layer could benefit Windows though. People get the impression that ARM processors are slow and spread the word, eventually killing ARM on the laptop. Killing ARM with a half hearted attempt is probably the path of least resistance for MS.

    38. Re:MS by Anonymous Coward · · Score: 0

      wait wait, let me fix that for you. "People generally use a $500 Windows on PCs because it comes pre-installed on their computer. Then they promptly spend 99% of their time on Facebook or whatnot which a $300 PC could do."

    39. Re:MS by Anonymous Coward · · Score: 0

      They lost me as a customer too. I don't care any more about Apple now that they are just another resale channel for Wintel clone hardware.

      The x86 monoculture is really frightening. Intel plans are clear, now that they have evicted all other architectures from the desktop, workstation and laptop markets, they are after IBM Power and mainframe servers (Sparc is already irrelevant). Once IBM throws the towel (when?, Power7 comes out in a few months, but I'm not even sure Power8 will exist), they will go after AMD. After that they will can Itanic (which they present right now as the alternative to x86. Alternative? From the same company?). Then they will go after ARM, which is the hardest to kill because of sale volumes and performance/W in some niches.

      The incredible thing is that most people think that variety is good in SW (Windows, Linux, MAcOS, BSD) and yet do not seem to mind about total hardware monoculture.

      For some reason that escapes me, Intel seems to always get away even with the most blatant monopolistic tricks that they have played over the last years. Remind that it is one of Intel's CEO that said that only the paranoid survive, now look at recent moves and be paranoid, saying that Intel is behind if it benefits Intel:

      - Intel Centrino: a big marketing campaign that allowed them to enter the WiFi market (the most important part of the Centrino brand is that it includess Intel's WiFi chip, not the processor and mobile chipset). For that one, you don't even need to be paranoid, this is a fact.

      - Apple buying PaSemi: PaSemi was going very strong in embedded and defense markets, winning designs left and right. This removed the strongest competitor to Intel in these markets (and one that really hurt them). What reward did Apple get from Intel for this? I can't believe that a world class processor design team is just going to glue together external IP for Apple iPhones and iPods (the iPod is going down BTW).

      - the current lawsuit against IBM for monopoly on mainframe class hardware. What are the users going to switch to? Intel is busy adding mainframe class features to x86 (will take some time, they will probably drop Itanium first, it is a money pit).

      - reports here and there that Intel did rebates on manufacturers that would not offer AMD chips. No volume related discounts
      (which could be acceptable), but on which manufacturer they would not buy chips from.

      - some more things that I missed

    40. Re:MS by DaVince21 · · Score: 1

      The biggest strength of Windows is running Win32 apps, and they are all compiled for Win/x86

      Microsoft has written VMs before to create compatibility with 16-bit applications on 32-bit systems before, right? The same should be possible with ARM, to at least a certain extent. (Someone mentioned the API differences of old software before so those probably wouldn't work unless old functionality was ported too in important libraries.)

      --
      I am not devoid of humor.
    41. Re:MS by badkarmadayaccount · · Score: 1

      Fucking with Intel?

      --
      I know tobacco is bad for you, so I smoke weed with crack.
    42. Re:MS by hattig · · Score: 1

      So you exclude the .NET applications (as .NET would be ported to ARM by Microsoft).

      And you stop considering the system calls (as they would be native ARM anyway).

      Then you consider that technology on the old Alpha (FX!32) could do x86 to Alpha translation at a speed that was acceptable for most applications. That was a long time ago.

      Older applications will not feel slow on an binary translated (not interpreted) x86.

      Leading-edge games will fail. Serious software will be turgid. Neither will be run on Atom systems anyway.

      Microsoft can use it to leverage .NET (i.e., migrate developers to newer technologies).

      But yes, an x86-to-ARM JIT recompiler is required. There are companies that specialise in such things like Transitive (who provided Apple's Rosetta technology for PPC on x86). I don't think this would be a roadblock.

      First, 2GHz dual/quad ARM Cortex A9s are required.

    43. Re:MS by hattig · · Score: 1

      A Cortex A5 core (inc L1 cache) is 1/9th the size of an Atom core (inc L1 cache). It will use far far less power. It is probably slower, clock for clock (I believe that A8 is competitive, clock for clock, and A9 beats Atom handily).

      A5 and Atom aren't competing however. A5 is in the market that Atom would like to be in in 3 or 4 generations. It's 0.9mm^2 in area!

      However ISA is getting less and less relevant. Android has applications run via a JIT, .NET is a JIT, Java has been JIT for years. The native platforms are probably Apple (but it's completely portable, and supports fat binaries on the desktop, but I reckon they could migrate iPhone ISA within a year if they wanted to), Nokia (Maemo), and legacy.

  10. Being late to the game is what is killing these... by chizu · · Score: 3, Interesting

    ARM talked about the Cortex A9 (the one I'd actually like to have in a netbook) over two years ago. There is still nothing you can get that actually has one in it. Yay something to replace the ARM11. Hope it actually gets used.

  11. 40NM by toastar · · Score: 0

    Just a Die Shrink?

  12. Different L2 memory interface makes the difference by Anonymous Coward · · Score: 2, Informative

    The Cortex-A5 has a more advanced L2 memory system with multiple outstanding transactions. This makes a huge difference for many workloads compared to the ARM11 cores. Thus, for workloads not contained entirely within the L1 memories the Cortex A5 should offer much better performance.

  13. Simpsons Did It by DirtyCanuck · · Score: 1

    So, Sparrow, we meet again.

    Yes. Sometimes I think that I am getting too old for this game.

    -- The Crepes of Wrath --

  14. More advanced identity? by Hurricane78 · · Score: 1

    Architecturally, it's identical to the more advanced Cortex-A9

    How can it be identical, when it's more advanced? Those two are opposites.

    Or is their definition of identity itself more advanced? ^^
    Like "(==) a b = a >= b" in Haskell?

    --
    Any sufficiently advanced intelligence is indistinguishable from stupidity.
    1. Re:More advanced identity? by Anonymous Coward · · Score: 0

      A Core2Duo is architecturally identical to a Core2Quad.

      Also, the word "advanced" is rather subjective.

    2. Re:More advanced identity? by Anonymous Coward · · Score: 0

      Same instruction architecture (ARM7A+Neon), same SMP support, same, same, same.
      Just slower but smaller than the A9.

    3. Re:More advanced identity? by TheRaven64 · · Score: 1
      This is what happens when you link to articles written by idiots instead of people who know what they are talking about. The article on Ars Technica was a lot better. The A9 is out-of-order, the A5 is in-order. The A9 is superscalar, the A5 is single-issue. They both have the same pipeline length (which surprised me; the A8 had a 10-stage pipeline, but apparently both the A5 and A9 have 8-stage ones). It's therefore possible that the A5 is a massively cut-down A9, with a single pipeline and a simpler instruction issue and retirement stages. That would make sense, because it would be relatively easy for ARM to design such a chip; just delete a load of stuff from the A9 and you've got the execution units. The cache controller is simpler, but it's possible that they just copied this from an earlier design too.

      The reason that they are described as identical is that they both support the same instruction set (although support for the NEON and floating point extensions is optional with the A5 but required with the A9). That means that you can run things compiled for the A9 on the A5 and they will work, just a lot more slowly. This is not true for the ARM9 and ARM11 cores currently used in the A5's target market; they have different privileged instruction sets to the Cortex A series and don't support many of the newer extensions that were added with this series. This will save development costs for handset manufacturers; they can use the same software stack (including OS) on their cheap low-end phones as on their high-end ones.

      --
      I am TheRaven on Soylent News
    4. Re:More advanced identity? by cheesybagel · · Score: 2, Informative
      What they mean is that the instruction set is compatible. So you can run the same binaries on both (although they would probably run faster if you recompiled them).

      ARM has several different instruction set versions and optional extensions. You cannot run binaries interchangeably in a simple fashion. This is arguably true as well for x86's SSE and the ilk but to a much smaller degree. Why do you think cellphone vendors use Java ME even if, more often than not, they use ARM processors?

      The hardware architecture is pretty different since A5 is in-order and A9 is out-of-order. It is like comparing an Intel Atom to an Intel Core processor.

    5. Re:More advanced identity? by SpinyNorman · · Score: 3, Insightful

      They're not saying "it's identical", they're saying "architecturally, it's identical", which is to say that any differences are non-architectural (i.e. performance, power consumption, etc).

      Perhaps a car analogy would help...

      If I say that color-wise my Ford Pinto is identical to my Ferrari, all I'm saying is identical is the color!

  15. First the Beatles; Now the ARM? by reporter · · Score: 1
    About 45 years ago, the Beatles took America by storm. They inspired a generation of pop-music writers and singers.

    Now, ARM -- another British invention -- has established a small beachhead in the notebook market (which includes netbooks). Can ARM do what SPARC, MIPS, Precision Architecture, and PowerPC failed to do? Can ARM actually reach 50% of the processor market for notebooks -- and eventually desktops?

    I hope so. I admit that I am biased and love cheering the underdog.

    Intel developed its x86 architecture by pumping globs of monopolistic profits into research and development. Too, the massive federal funding (via university research grants) and corporate funding furthered the development of both SPARC and MIPS. By contrast, ARM was developed on a shoestring budget. The goal was modest: low power and average performance.

    All the American processors are Goliaths. ARM is David. I hope that David slays the biggest Goliath: x86.

    Cheerio.

    1. Re:First the Beatles; Now the ARM? by MrNaz · · Score: 1

      I hope ARM beats x86 merely because x86 is an ancient technology that has a pile of limitations preventing the industry from moving forward as fast as it otherwise might. Previous attempts to move away from x86 failed due to the absence of software to run on the new machines. It's all fine and dandy if Microsoft write NT for the Dec Alpha and Itanium, but if there are no apps, it's pointless.

      ARM however, has a software patron in Linux and the open source community. I'm the hopeful kind, and I hope that ARM and Linux help each other gain market share. Super low power netbooks that only run Linux would rock. Windows will never run on a machine that delivers 20 hours run time on a single charge. Linux+ARM can deliver that, it's just a matter of an OEM having the balls to invest the marketing and development dollars in making it happen.

      --
      I hate printers.
    2. Re:First the Beatles; Now the ARM? by Anonymous Coward · · Score: 0

      ^ saddest attempt at karma whoring ever

    3. Re:First the Beatles; Now the ARM? by Hal_Porter · · Score: 3, Interesting

      I hope ARM beats x86 merely because x86 is an ancient technology that has a pile of limitations preventing the industry from moving forward as fast as it otherwise might. Previous attempts to move away from x86 failed due to the absence of software to run on the new machines. It's all fine and dandy if Microsoft write NT for the Dec Alpha and Itanium, but if there are no apps, it's pointless.

      Actually there is a way for this to work. Microsoft ports Windows to Arm. Most of the time the processor is in kernel mode so that makes a difference. Now running user mode code through an emulator which is basically a big switch statement will not deliver a decent performance level. Microsoft could port their Office applications to ARM.

      ARM have actually quite some experience of running non native instruction sets - Jazelle is mode where the ARM runs 80% of Java byte code natively. Basically there is an extra pipeline stage that decodes Java byte code into native ARM instructions.

      Now surprisingly this doesn't give particularly good performance

      http://weblogs.java.net/blog/mlam/archive/2007/02/when_is_softwar_1.html

      It's actually better to JIT the code. ARM have actually have a second generation produce that uses a mixture of Ahead or Time compilation to native code for the Java platform, DBX aka Jazelle for rarely used code and JIT for the hotspots that are executed frequently. In practice I'm told that you could get by with purely AOT for the platform and JIT for the rest, except that application startup will seem sluggish.

      x86 Java VMs have to do this because there is no equivalent of Jazelle DBX there. Now ARM could do something similar for netbooks. Still that is not without problems. Notebook processors, whether x86 or ARM are optimized for power consumption, not performance. Notebooks are also very short of memory - you basically can't afford to keep both the native ARM code and the original x86 code in memory. Actually there isn't much disk space either.

      So it's far from clear whether an ARM that can perform as fast as an Atom on native code - i.e. a faster processor that the fastest Cortex A9 - would be able to run x86 code as fast as an Atom. Given that the performance of an Atom running x86 code is pretty awful, that makes me wonder if you could sell them even if the battery life is much better. Even that is doubtful actually - Atom is pretty power efficient but current Atom chipsets are not. It's likely that Intel will fix that problem if Arm based notebooks start to become popular though. They'll cut the price of Atoms too. At that point ARM doesn't really have any advantage over x86.

      Of course I say x86 but most x86 chips will be running x86-64 code by then. ARM doesn't have a 64 bit extension either.

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
    4. Re:First the Beatles; Now the ARM? by Anonymous Coward · · Score: 0

      Notebooks these days are in the main most certainly not short of memory & storage space unless you call 2Gb of RAM & 160Gb HDD a limiting factor?

      Otherwise, most of what you say I am in complete agreememnt with.

    5. Re:First the Beatles; Now the ARM? by SimonTheSoundMan · · Score: 4, Interesting

      Acorn Computers tried in the 80's and 90's. The ARM processors were faster than their x86 rivals, and OS was years ahead of the likes of Windows and Mac OS. As you say, some monopolistic software company would never allow ARM to take off. Lucky ARM is now the most common architecture on the market.

      It's sad x86 is still here, the platform should have been done away with years ago.

    6. Re:First the Beatles; Now the ARM? by TheRaven64 · · Score: 1

      They were also much cheaper. I remember A3000s being under £100, when the cheapest PC that you could actually use seriously was at least £500, and probably closer to £1000. If you wanted a hard drive, it cost a bit more, but most RiscOS software at the time could run from floppy. If you got a 70MB or so hard disk (when PCs typically came with 250MB+) then you could store all of your applications and data on it easily.

      --
      I am TheRaven on Soylent News
    7. Re:First the Beatles; Now the ARM? by Hal_Porter · · Score: 1

      I've played around with an Atom based machine with 2Gb of Ram and a 160GB drive and Win7 which is relatively efficient compared to Vista. Still it was not a fast device and frankly not the sort of machine I'd buy.

      I can't see how people can think this sort class of machine has the spare horsepower to run a JIT compiler - It's dog slow even with the code being executed natively for bloated modern applications.

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
    8. Re:First the Beatles; Now the ARM? by jimicus · · Score: 1

      By contrast, ARM was developed on a shoestring budget. The goal was modest: low power and average performance.

      The goal was, simply, a half-decent processor architecture that could supplement and eventually replace the 6502 in Acorn's range of desktop computers. They didn't think anything on the market at the time was suitable.

      They read about the Berkeley RISC project and figured if a bunch of students could put together a processor architecture, they should be able to do a good job fairly easily.

      That the processor architecture wound up offering sufficiently good performance/watt as to become a roaring success in the embedded market was certainly not part of the original plan. Worked out pretty well for the people who went on to form ARM, though.

    9. Re:First the Beatles; Now the ARM? by TheRaven64 · · Score: 1

      Well, almost. This was true for the ARM1, but that chip never made it to market. The ARM2 was developed with some additional funding from Apple, with the aim of powering the Newton. Power efficiency was definitely a goal for this processor, and for all subsequent ARM chips.

      --
      I am TheRaven on Soylent News
    10. Re:First the Beatles; Now the ARM? by haruchai · · Score: 1

      The success of the x86 is mind-boggling considering all the true innovation that has been happening around it
      for 3 decades. Can its success be attributed to nothing more than Intel's fabrication capabilities and M$ support?
      Even Intel's shiny new Nehalem architecture is not much more than an updating of the DEC Alpha ( ditto for AMD
      but their designs, at least, have been based on it for 10 years.

      --
      Pain is merely failure leaving the body
    11. Re:First the Beatles; Now the ARM? by gyrogeerloose · · Score: 1

      ARM -- another British invention -- has established a small beachhead in the notebook market

      Not quite accurate. While Acorn is indeed a British company, the current batch of ARM (Acorn RISC Machine) processors is actually the result of a collaboration between Acorn, Apple Inc. and VLSI Technology. I guess you could say it's a multi-national invention.

      No argument at all about the Beatles, though.

      --
      This ain't rocket surgery.
    12. Re:First the Beatles; Now the ARM? by Anonymous Coward · · Score: 1, Insightful

      It's dog slow even with the code being executed natively for bloated modern applications.

      It's funny you say that. My Acer Aspire One running Ubuntu 9.10 is blazing fast. Every program I use just starts right up with very little latency. Using them, they are all very responsive. I have a few java programs that also run very well. Open Office runs great, Frostwire runs great, running the java printer program that you have to use to print postage through Paypal runs perfectly fine also. My other computer is a 2.8 GHz C2D running Debian so I have a good performance reference. The netbook hooked up to an external monitor, keyboard and mouse for most tasks is not much different than my desktop. Wait a minute, I think I just realized your problem

      and Win7

      Damn. My bad. Yeah, an Atom isn't nearly enough for that. *snicker*

    13. Re:First the Beatles; Now the ARM? by Hal_Porter · · Score: 1

      Ubuntu runs rather like treacle on netbooks too. And basically I wouldn't use it even if it run quickly because it doesn't run the applications I want to use. Still, I guess I'm not an elite hacker like you.

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
    14. Re:First the Beatles; Now the ARM? by Anonymous Coward · · Score: 0, Informative

      I'm going to keep this civil.

      Ubuntu runs rather like treacle on netbooks too.

      Short story: It used to but not anymore.
      Long story: Ubuntu 9.10 unlike its predecessors uses a newer more optimized kernel, new intel graphics drivers that have solved all of the performance issues of the previous effort, a new compiler that is pushing out significantly more processor efficient code, and it now defaults to the much faster modern ext4 file system. All of this adds up to significantly snappier performance on Atom based netbooks than both its predecessor or alternative OS's like Windows 7. So, please keep your old outdated FUD to yourself.

      And basically I wouldn't use it even if it run quickly because it doesn't run the applications I want to use.

      Two points for this one. First, between Wine, Crossover and VirtualBox, the old "it doesn't run my apps" is getting really tired. I'm getting into my 30's so I'm not as much of a gamer anymore but, occasionally I do fire up a golden oldie. Ever seen the level load times of FarCry on a Windows box using the NTFS file system? Cut that in half running it in Wine on a modern file system like Ext4. And when new stuff like an enemy jumps out, on Windows there a very small stutter, on Linux, no stutter. When you shoot and kill an enemy in Windows and they fall, they stutter again, not so on Linux. All of this is on the 2.8GHz C2D with a 9800GT video card. Same deal in Half-Life 2, Morrowind, FEAR, so on and so forth. They all run better in Linux than they do natively on Windows. Obviously, this doesn't apply on the netbook as it doesn't have the graphics card to play much more than Quake 2. But, that runs great in Ubuntu also, so there you have that. Oh, and Office 2003 runs faster in Crossover than it does natively. About the only downside I see to using Wine is the lack of support from the publishers. Hopefully that can be worked out in the future. In the meantime, I'll just suffer without it and console myself with the much greater performance and the portability. Portability, I say? Oh yeah, copy the Wine directory to another Linux machine and every program installed in it Just Works(TM). Try copying Program Files to another box and see what you get with most applications. Hint, it doesn't Just Work(TM). For the very few and steadily dwindling apps that don't play nice with Wine, there is another alternative. I find that a VM is the perfect place for Windows as it keeps malware like WGA from misbehaving and doing things like spontaneously rebooting my entire computer. Also, note that with Ubuntu 9.10, WinXP runs just fine in a VM when I really need it for oh, the two programs that don't have native Linux clients yet. As a matter of fact, if I were running Windows on the bare metal, I'd still run all of the auxiliary apps in a vm for many reasons. Ease of portability being one. When you reinstall Windows on a new box, you have to dig out all of your application CD's, driver CD's etc. and spend many hours getting back to where you started on your old machine. With Linux, I just pull the drive out of the old machine and plug it into the new machine. It starts right up on the new hardware as if nothing happened. Only a VM gives Windows this capability. My second point on your ridiculous FUD is that the coin has two sides. There are several Linux programs that I use very often that have no counterparts on Windows. To use the equivalent of your sentiment, I'll just say "So, there!"

      Still, I guess I'm not an elite hacker like you.

      Still more ancient fud. Every new user that isn't habitually entrenched in the backwards "Windows way" take to Ubuntu like a fish in water. No elite hacker skills required. You want to talk about elite hacker skills? Try removing much of the more nefarious malware that Windows boxes tend to be subject to. That takes some serious work.

    15. Re:First the Beatles; Now the ARM? by footnmouth · · Score: 1

      From my recollection, Acorn got the ARM2 to market before Apple placed the order for the Newton. I only remember because I bought 3 thousand shares with a bit of my student loan (as I was a massive Acorn fan) at 8p a share and made an absolute killing (I sold out at £1.05 - my father kept his through numerous stock splits and has bought 3 cars from the proceeds - thank you Acorn). The reason it sticks in the mind as it was a post on comp.sys.acorn or comp.sys.os.acorn or something that made me buy them. As a processor fan and a nerd, I was always impressed at how easy assembler was / is on the ARM and wish I'd made more from having email chats with some bloke called Linus in '91 / '92 about compiling his new operating system onto my A5000... ho hum :-)

      --
      -- For evil to triumph it is enough that good men do nothing.
    16. Re:First the Beatles; Now the ARM? by bjorniac · · Score: 1

      This man is bound to be correct - he's even got 6502 in his UID!

      (I couldn't convince my Dad to buy acorn shares when they were 6p...)

    17. Re:First the Beatles; Now the ARM? by Anonymous Coward · · Score: 0

      That's right, mark me Troll. The truth hurts doesn't it?

    18. Re:First the Beatles; Now the ARM? by snadrus · · Score: 1

      Except most of the performance value from -64 was from an increased register set that ARM already has. 64-bit extensions are likely easier to implement than x86 decode.

      Atoms using less power would hurt ARM, but a licensable?? processor is interesting as well (from a competitive standpoint).

      --
      Science & open-source build trust from peer review. Learn systems you can trust.
    19. Re:First the Beatles; Now the ARM? by Vastad · · Score: 1

      Is there somewhere I can learn about everything you've done with Ubuntu, Wine, Crossover and getting abandonware to work on Linux VMs?

      I have an old Toshiba M10 laptop from 2003 that's amazingly still ticking along and would be perfect for teaching myself Linux. I want to get the original System Shock to work if I can. Syndicate Wars as well (still have the box, manual and CD). I have a feeling I can squeeze out way more performance from it than the OEM XP install currently does.

    20. Re:First the Beatles; Now the ARM? by oakgrove · · Score: 1

      Sure, the best place to start when you are looking for advice on how to get a particular Windows application to work in Wine is here . Just run a search for your games in the application database and see what comes up.

      I've never personally ran either of the two games you mentioned, however, I do have a couple of general pointers.
      The very first thing I do when wanting to try a new game is I just put the CD in the drive on my Ubuntu box and see if it will work. Ubuntu 9.10 which is going to drop here in a couple of days offers much tighter integration between apps installed in Wine and the regular desktop. The correct icons are used instead of generic Wine icons, menu entries are better integrated, and the stock software add/remove functionality now supports Wine apps right along side the native Linux ones.

      Now, after you have installed Wine and put the CD in the drive and the autorun dialog comes up and you've installed the game, if you click on it in your menu and it doesn't work the most likely problem is there is a particular dll file it's looking for that isn't there. Open up your terminal and navigate to the game's executable in your /home/username/.wine/drive_c/Program files/ directory and try to run it with $ wine app_name.exe. Pay attention to the output and scan through the gobbledygood and look for what it says the problem is. If it is indeed a dll, just do a google search with "missing.dll download" and usually, a site will come up that has it for download. Copy it to the same directory the game's executable is and it should work at that point as that is in the search path for dll's when wine tries to load something. If it still doesn't work, that's when I hit the application database. Sometimes there are simple tweaks and sometimes there are more complex ones. Fallout 3 comes to mind here. That should get you started on that.

      A couple of general Linux pointers:
      First, don't be afraid to break your install. Linux is very robust but it will do anything you tell it to do with a salute and a smile. So, if you unwittingly tell it to break itself, it will. And as a curious technically adept user, you will do this probably more than once. No problem, just expect that at first, that will happen. Trying to fix it will be a good learning experience and even if you don't succeed and have to reinstall, you will still have learned a great deal. I generally recommend any new Linux user that really wants to learn Linux and not just use it to "get work done" start off in a virtual machine. VirtualBox is really good as it's free and it allows 3D capabilities in Linux guests unlike vmware so you get the full effect with compiz, etc. Run it and read all the Linux books you can find and experiment with it. It's a very rewarding experience and this is how I learned to use Linux. The funny thing is, after a year or so, you will look back on some of the mistakes you made at first, at the time seeing them as insurmountable errors requiring yet another reinstall but after the year, are the easiest thing in the world to fix. My first reinstall came after messing up the nvidia driver. Now, I can install and configure it in my sleep.

      So, don't let anything discourage you. There will be times when you're like, "Screw this, I'm going back to Windows." Just know that when that happens, it means you are normal and just need to persevere a little longer.

      I hope this helps and if I sound condescending at all, I don't mean it that way. If you have any questions, just reply.

      --
      The soylentnews experiment has been a dismal failure.
    21. Re:First the Beatles; Now the ARM? by Anonymous Coward · · Score: 0

      The ARM6 was the result of the early 90s Apple/ARM collaboration (Apple invested and encouraged the separation of Acorn and the ARM CPU division, and took an early large share in the company which they sold in the later 1990s for a nice profit), but only cleaned up some of the ARM2 architecture that was already designed and shipping.

      Since then ARM have brought us the ARM7 (GBA, original iPod), ARM9 (DS), ARM11 (iPhone 1) and ARM Cortex (iPhone 3, Pre) range of products. They're also known as Advanced RISC Machines now, I think they dropped the Acorn part back in the 90s as well. I guess if you are still living in the 90s (hey, top tip: invest in Apple in 1998!), then that part of your comment would be accurate.

    22. Re:First the Beatles; Now the ARM? by Vastad · · Score: 1

      Thank you very much for your reply. You weren't condenscending at all.

      I'll backup what I want to keep from the old Toshiba and upsize it's 20GB(!) hard disk.

    23. Re:First the Beatles; Now the ARM? by gyrogeerloose · · Score: 1

      hey, top tip: invest in Apple in 1998!

      Actually, I did--at $14 per share! It's at $202 as I write this and has split once since I purchased it. I only wish I'd been able to buy a more substantial amount.

      --
      This ain't rocket surgery.
  16. More PR Bullshit by hyades1 · · Score: 2, Funny

    We really have to start looking more carefully at posts like this, which clearly contain entire paragraphs of unexamined assertions by company PR drones that may or may not be true. Bottom line: Kill this shit unless a trustworthy, honest reviewer with a decent track record says it. If that isn't happening, quit posting it here, where we have more important stuff to spend time on.

    By the way, that "more important stuff" includes pulling our dicks and/or replaying World Championship Monopoly games move by move.

    --
    I've calculated my velocity with such exquisite precision that I have no idea where I am.
  17. your getting it mixed up by Anonymous Coward · · Score: 0

    The A5 is noy meant to compete with atom. it is meant to replace to ARM11 on the low end. Roughly the same power, but with more features and cheaper. I guess that the A8 hasn't been seeing a good enough uptake due to the recession. That would explain why they are only announcing it now. It is the A9 that is going to take on Atom.

  18. Re:Being late to the game is what is killing these by BikeHelmet · · Score: 1

    Late? They said 2010 in the article you linked.

    In this article, they said Cortex A5 in 2011.

  19. A5 is for people like me by OrangeTide · · Score: 3, Interesting

    As a developer for products based on ARM9 and ARM11 SoCs the A5 is targeted squarely at me. I'm not sure why it's of any interest to slashdot. But it does appear to be a cheaper ARM11 (to the point of making the ARM9 obsolete) but with some of the features of the A8.
    While smartphones are all sexy and exciting, the staple for cell phone manufacturers are the simple ordinary phones. If they can cram more features into the same cheap phone it usually means they can sell more of them. Think of it as competing in the free phone market. Where the styling and brand and features are the only way to differentiate yourself rather than price. The customer is just going to pick 1-4 of the plan bundled phones.

    --
    “Common sense is not so common.” — Voltaire
    1. Re:A5 is for people like me by Big+Jojo · · Score: 1

      Not sure I'd agree with a cheaper ARM11 ... more like a cheaper Cortex-A8!

      Absolutely agreed that A5 targets ARM9 and ARM11 users though. ARM makes that clear. All other things being equal, I'd want a Cortex-A5 instead of any of those. ARM9 is trusty but limited at the high end. ARM11 is kind of awkward; never quite took over from ARM9, and given Cortex I doubt it'll ever catch on all that much more. ThumbEE (on Cortex-A) is way better than Jazelle (on ARM9/ARM11); it works for any JIT-oriented runtime, not just Java. Thumb2 makes me think of pure Thumb2 userspace, for the code (and icache!!) space savings. If I were designing smartphone chips, I'd like that ability to stick in additional A5 cores, without huge changes when customers need more CPU horsepower. Ditto if I were designing any other kind of ARM-based SoC product.

      Another point is that Cortex-A5 is I think what Xilinx will use in their new ARM-equipped FPGAs, due next year or so. That's going to take another segment of the market by storm ... they're not giving up their PPC-equipped options, but are working more closely with ARM IP, and to evolve the ARM interconnects. Seems like a win all around; less work to integrate the various IP products, and Xilinx will be able to align some power reduction efforts to better match what most developers want: ARM applications driving low powered semicustom designs. In contrast, the Cortex-M1, long available in soft core packages from e.g. Altera and Actel, is a pretty low end beast ... for microcontrollers, not applications processsors.

    2. Re:A5 is for people like me by LWATCDR · · Score: 1

      I think that the "feature phone" is dead. Smart phones are in the $100 range right now. In a year or so I expect to see a free Android phone. Even the current feature phones are pretty dang smart. Take a look at the LG Lotus. Imagine that with an A5 and a real browser.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
  20. I do not think Exponentially means what you think by Kupfernigk · · Score: 3, Funny
    "Exponentially" means according to a function in which one of the terms is a constant raised to a term which includes the power of the x variable. It is not a synonym for "many times", and it cannot apply to something which is, even instantaneously, a constant, since it can only refer to a function. If you mean that the number of MIPS/Linux applications increases linearly while that of X86 functions is increasing exponentially you might have a point - except that, at any moment in time without more information, this would not tell you which function was largest or had the largest gradient.

    You have to expect pedantry, this is Slashdot.

    --
    From scarped cliff or quarried stone she cries "A thousand types are gone, I care for nothing, no not one."
  21. Re:Being late to the game is what is killing these by Anonymous Coward · · Score: 0

    You haven't seen any products with A9 inside, yet, because the chips that are built around the A9 can take 1-2 years to go into full manufacture. It then takes time to build devices out of finished product. Next year, you will see NVIDIA showing of Tegra2 based systems containing Cortex-A9.

      A5 is still being designed, so don't expect anything soon....

  22. Re:Being late to the game is what is killing these by TheRaven64 · · Score: 1

    Define 'you'. ARM began selling Cortex A9 licenses a while ago, but ARM does not produce chips. TI are shipping OMAP4 SoCs based on the A9 to high-volume OEMs for a little while, as have a couple of other ARM licensees. They should be appearing in consumer products in 2010. As, in fact, it said in the article you linked to.

    --
    I am TheRaven on Soylent News
  23. Re:Being late to the game is what is killing these by SimonTheSoundMan · · Score: 1

    Before the A series, ARM haven't really designed any new processors since Acorn Computers died in 2000/2001. The only development push ARM had is when RISCOS went to other manufacturers such as Castle. Now ARM needs to design new processors as their time has come where more powerful CPUs are needed in the mobile devices.

  24. Re:Being late to the game is what is killing these by bhtooefr · · Score: 1

    ARM11 launched in 2002. That's a pretty major one...

    (And, Acorn as a personal computer manufacturer died in 1998. They were using the DEC StrongARM, which predates the ARM9 and ARM10 - the StrongARM was used in place of the ARM8 that was still under development, and the ARM9 borrowed ideas from the StrongARM.)

  25. Re:hey i got the f by Anonymous Coward · · Score: 0

    I was just thinking about that yesterday. Did you ever notice that when a commercial or movie wants to be "edgy," they show a black man either kissing or in a suggestive post with a white woman (see Levis Jeans commercial with nonsensical video montage), but you never see a white man kissing a black woman on TV unless it's in the context of a slave owner raping his slaves?

  26. If it's free, it's likely already on *n?x by tepples · · Score: 1

    Plus, it could even take advantage of the enormous number of open source programs that could be compiled for ARM Windows before commercial titles get ported.

    Most open source desktop apps that I've seen either are ported to GNU/Linux (e.g. Firefox and OpenOffice.org) or came from the GNU side of the fence in the first place (e.g. GIMP and Inkscape). So Windows NT for ARM wouldn't have a huge advantage over Ubuntu in this case. It would probably be more productive to consider a compatibility layer from Windows CE to Windows NT, much like the Win16 to Win32 and Win32 to Win64 layers that Microsoft has already implemented in Windows NT, so that at least a user's collection of Pocket PC apps will still work.

  27. Publishers that decline to recompile by tepples · · Score: 1

    Making a C program 64-bit safe, if it was not designed to be portable originally, is a lot of effort. Porting a C (or C-family) program from x86 to ARM is generally a straight recompile.

    Plus the price of a hostile takeover of the non-free program's copyright owner, which otherwise declines to do this recompile in the interest of maintaining the market segmentation between the smartphone editions (Windows Mobile, iPhone, etc.) and the desktop edition of a program.

    But, really, a port of Autocad is irrelevant.

    AutoCAD was used as an example. There are plenty of other non-free programs for Windows that won't be recompiled on ARM.

  28. StrongARM got renamed; Games for Windows vs. Xbox by tepples · · Score: 1

    Converting 32-bit code from one CPU to another is much easier than going from 32-bit to 64-bit, so it wouldn't take very long for vendors to update their software for it.

    Unless the vendor declines to do the port at all for business reasons. This happened back in the days of NT 3, which was ported to MIPS and PowerPC but most apps still had to run in the emulator.

    Also, Microsoft strongarms ISVs into compatibility.

    Don't you mean Microsoft XScales ISVs into compatibility?

    For example, it's often hard (or harder) to get "Windows Logo" certifications for software unless it works on various platforms.

    Does Microsoft demand that all PC games in the "Games for Windows" brand get ported to Xbox 360? No. Desktop PCs and mobile phones are at least as different as desktop PCs and video game consoles.

  29. x86 abi by tepples · · Score: 2, Insightful

    You can bet that an ARM version of Windows would be accompanied by an ARM version of Office

    But how easily would Microsoft Office (for Windows 8 ARM Edition) run third-party extensions designed for Microsoft Office (for Windows x86)?

    Most software, unless it uses inline assembly or SSE / MMX intrinsics, is a straight recompile.

    A lot of programs' file formats depend on details of the x86 ABI because the programs pretty much just fwrite() a struct to disc.

  30. raw Mhz speed? by Anonymous Coward · · Score: 0

    Why no mention of raw speed? I know it doesn't matter that much and architecturally there exist two CPUs at any time, one with X Ghz and another with Y Ghz, with X less than Y but X being still a better CPU, but it still gives you a ballpark for the same (or almost) generation of CPUs.

  31. Benchmarks vs. Atom by wonkavader · · Score: 1

    Has anyone found intelligently done benchmarks which pit Cortex A9-MP against Intel Atom?

  32. Re:I do not think Exponentially means what you thi by ZERO1ZERO · · Score: 1
    You have to expect pedantry, this is Slashdot.

    Quite literally, I think you'll find.

  33. xSoftware stacks miss the point on Net/Smart Books by Anonymous Coward · · Score: 0

    These devices don't really run much legacy code. They spend most of their time on the, wait for it, Internet. Which is why Google never bothered with an OS until after Google docs. Will people be willing to get a "good enough machine" for USD 100 less (the approx. Wintel tax)?

    The point here is that what the microprocessor taught us was in the long haul, volume wins and there are a hell of a lot more phones then PCs.

  34. ARM got misled by Linux community by Anonymous Coward · · Score: 1, Insightful

    and the only advantage of Netbook over a real mini communication device which has OS designed to run on it is? Ability to run Windows unmodified.

    I speak about devices like Nokia E90, N97, N900.

    ARM really gets confused very easily it seems. They should ask Asus, HP, Acer and several others. Why does a customer buy a low powered laptop like device for?

  35. But what if Atom really works fine on smart phone? by Ilgaz · · Score: 2, Insightful

    Speaking (typing) from a Quad G5, PPC and watched the happenings in OS X community/developer scene since Intel transition announced. If Intel one day manages to make Atom (x86) run in same low power as ARM licensed CPUs, ARM is doomed.

    Why? Compare the compile process of an open source, multimedia application on PPC and Intel. See the "bonus" stuff Intel chips get? Every kind of optimization, way more cheaper is available on Intel x86/SSE. Trust me, I am more amazed to Intel's developer/development/application support every single day. I don't even blame Apple anymore, I blame IBM/Motorola etc.

  36. Re:I do not think Exponentially means what you thi by im_thatoneguy · · Score: 1

    How about this.

    Let's define a constant as X.

    There is X ARM software available
    There is at least X^Y where Y is >= 2 x86 software available

    Seeing as I have no idea what the actual numbers for ARM or x86 software is I decided to express the relationship between the two functions for any definition of X and Y as is accurate to the data.

  37. Re:I do not think Exponentially means what you thi by JTeutenberg · · Score: 1

    In this case you ought to say "there is an order of magnitude more software available...(base Y)".

    Otherwise, using your argument, for the same numbers you could equally say "there is a constant factor more more software available", in that for X ARM apps there are X*c x386 apps for c > 1

    Obviously this is true for the constant c = X^(Y-1)

    As soon as you start playing with two constants, there is an infinite number of functions that can interpolate between them (and hence describe their relationship). This includes exponential functions, polynomial, constant, sinusoidal, linear...

  38. Re:But what if Atom really works fine on smart pho by BikeHelmet · · Score: 1

    But ARM has those spiffy DSPs. More and more codecs are going GPU or DSP powered, so who cares about CPU optimizations for such multimedia tasks?

    By the time an Atom has as low power consumption as an Arm processor, Arm processors will be faster. :/

  39. premature evaluation by epine · · Score: 2, Interesting

    Even Intel's shiny new Nehalem architecture is not much more than an updating of the DEC Alpha (ditto for AMD but their designs, at least, have been based on it for 10 years).

    I'm shocked at this claim. Back in the day, Byte Magazine used to dissect processor architectures in a way you rarely see any more, apart from anything written by Jon Stokes over at Ars. Realworldtech picked up the torch, and I followed it for a while; smart guys, but you need a large Kool-Aid division factor to hang there.

    This problem of "true innovation" has dogged the computer industry since the introduction of Hype 1.0.

    Kurweil's law is "no technology before its time". Why is it that the premature ejaculator so often gets the lion's share of the credit? You can't deny the innovation at Xerox. The Xerox Dorado from 1979, which I once used for an hour, is reputed to have contained 3000 discrete ECL chips and have a BOM cost pushing up into six figures. Retail price might have been in the $200k range if, say, all the moon rocks recovered by NASA had been made of solid gold, and the engineers were suitably rewarded. I was told my my friend, a coop student there at the time, that the rumour on estimated street price to sell the Dorado was "probably $250k". I thought that was high at the time, but I knew less then about cost multiples.

    Ray Kurzweil on how technology will transform us

    ... acceleration of technology [is a] strong interest of mine, and a theme that I've developed for some 30 years. I realized that my technologies had to make sense when I finished the project. That invariably, the world was a different place when I would introduce a technology. And, I noticed that most inventions fail, not because the R&D department can't get it to work -- if you look at most business plans, they will actually succeed if given the opportunity to build what they say they're going to build, and 90 percent of those projects or more will fail, because the timing is wrong -- not all the enabling factors will be in place when they're needed.

    When you run a giant fab, you need to consider your volume targets in choosing processor design goals. What made the Alpha kick ass was the incorporation of some ultra-expensive metalization. That's how you get fast 64-bit adder in early 1990s process technology: an entire layer devoted to fast carry propagation. Lacking OOO, you need short, deterministic instruction latencies above all else, unobtainium be damned. Works for NASA, Boeing, and Ferrari. This fabrication approach was a total non-starter for Intel volume production.

    IIRC--and this is becoming dim--the Alpha was a four-issue core with a uniform instruction width and precious little OOO logic. What is it that Nahalem is reputed to have copied here? It's been known for 15 years now that x86 integer performance was able to directly compete with RISC designs given a large design team devoted to working around the instruction set wonkiness. Most of the problems with x86 were toll bridges, rather than permanent road blocks. On the floating point side, the blighted x86 stack architecture cost you a factor of two. But floating point defined the low-volume workstation market, where sports cars like the Alpha found fleeting glory. I actually think the Itanium better represented Intel's desire to take Alpha to the next level.

    Apart from that, over the longer time frame, reality imposes convergent evolution. To my knowledge, Intel never once publicly stated that AMD's on-die memory controller was the wrong path to take. Intel usually said "not yet, we can do it cheaper for another spin without going there, and besides, our marketing department ate some bad mushrooms for a couple of years there, so our roadmap is a bit jumbled right now." Does AMD get credit for innovating on-die memory controllers or for facing up to despe

    1. Re:premature evaluation by haruchai · · Score: 1

      Good Lord!! Did my little post cause this projectile vomitus?

      I think you're replying to every post on this topic, and possibly a few others, all at once.

        The non-starter argument for Intel and its fab volume production is poppycock.
      Chipzilla had plenty of fabs and plenty of clout and there were enough innovations in the Alpha architecture that they didn't need to implement everything at once.
      And, to top it off, Intel had essentially acquired the Alpha lock, stock and barrel from HP and probably thought they owned the world - x86 was well entrenched, they were partnered with HP on the architecture of the future, the Itanic and AMD, well, what could they do?

      As far as the x86 ISA, it stayed ahead of the RISC designs by essentially co-opting the competition, where each x86 instruction was split into smaller micro-ops.
      I'm not sure who was the first of the x86 makers to do this - perhaps NexGen, later absorbed into AMD.

      --
      Pain is merely failure leaving the body
  40. Motherboards? by Nuno+Sa · · Score: 1

    We need some motherboards with a couple of hyper-transport-3 enabled A9s, and sockets for RAM. At least 8GB (16GB NUMA?). That connected to a semi-decent south bridge (with pci, pci-e, sata, usb et al.)

    This board should cost less than USD$150 with the 2 A9s. And after a few months maybe < $100?

    That's a dream because the A9s are not working in dual socket configurations yet and ARM doesn't invest in the desktop with a motherboard reference design. Sad...

    1. Re:Motherboards? by Anonymous Coward · · Score: 0

      I agree. I've been looking for exactly this product for almost a year now.

  41. Context switches between native and emulated code by tepples · · Score: 1

    So you exclude the .NET applications (as .NET would be ported to ARM by Microsoft).

    Not all applications written in C++ have been rewritten in managed C++ or another .NET language. Not all developers want their apps to depend on the tens of megabytes in the .NET framework, especially if they still have a lot of users who don't already have the framework installed. Nor does it help apps that use PInvoke to call native libraries that fill holes in the .NET framework.

    And you stop considering the system calls (as they would be native ARM anyway).

    Can an end user quantify how much time a given application spends in user space vs. the kernel? I have access to a couple PCs running Windows XP; does Task Manager or a similar tool let the user separate out syscalls from user mode? And the last time I looked at a mixed-instruction-set environment (mixed x86/PowerPC in the era of System 7.5), context switches between instruction sets were rawther expensive.

    First, 2GHz dual/quad ARM Cortex A9s are required.

    I'd like to know how much battery power would be required.

  42. Re:Context switches between native and emulated co by hattig · · Score: 1

    ARM recently released a 2GHz dual-core A9 hard-core for TSMC's process (40nm). I forget the power consumption, but it was quite low compared to Atom.

    http://www.electronicsweekly.com/Articles/2009/09/16/46955/arm-produces-hard-cortex-a9-for-high-performance.htm

    ah... http://www.arm.com/news/25922.html

    "The Cortex-A9 power-optimized hard macro implementation delivers its peak performance of 4000 DMIPS while consuming less than 250mW per CPU when selected from typical silicon."