ARM Attacks Intel's Netbook Stranglehold

Barence writes "British chip designer ARM is launching an outright attack on Intel with the launch of a 2GHz processor aimed at everything from netbooks to servers. ARM claims the 40nm Cortex A9 MPCore processor represents a shift in strategy for the company, which has until now concentrated on low-power processors for mobile devices. In the consumer market, ARM is pitching the Cortex A9 directly against Intel's Atom, claiming the processor offers five times the power while drawing comparable amounts of energy. 'It's head and shoulders above anything Intel can deliver today,' ARM VP of marketing Eric Schom claims. However, it has one major hurdle to overcome: it doesn't support Windows. 'We've had conversations with Microsoft and you can imagine what they entail,' says Schom."

Comments

Porting code to a new architecture

[Xocet_00]

What is involved in porting code to a new chip? I've done some programming in my life, but it has mostly been limited to personal interest and school projects. I imagine it can't be as simple as just recompiling. So what does it take to port code?What are the hurdles? Assume (accurately) that I'm a total noob.

Re:Porting code to a new architecture

[FourthAge]

Another ARM gotcha is that "char" is "unsigned" unless you specifically make it "signed", because "unsigned char" can be manipulated more efficiently by the instruction set. This is not what C programmers usually expect, although it is permitted by ANSI C. It can cause some interesting bugs.

Re:But, does it run DOS?

[TheRaven64]

People are willing to pay $15 more for XP (the cost of an XP Netbook license), but are they willing to pay $100 more for Windows (the difference between the cost of the announced ARM-based netbooks and a typical x86 model)?

A call to ARMs!

[MarkvW]

A Microsoft refusal to support a really cool netbook technology would be a good opening for Linux.

real solution

[99BottlesOfBeerInMyF]

There are a lot of barriers to Windows adoption on the ARM processor that go beyond MS not really wanting it. If they really want to gain market share above and beyond cell phones and PDA's, ARM needs a strong partner to create a real, integrated, polished solution. And by solution I don't mean a device. They need to do something akin to the iPhone, in creating a nice device or set of devices with a consistent polished operating system and with an integrated ecosystem of solutions. The project is large in scope and they need a partner that preferably has an existing position to leverage, experience, money, and which is not beholden to Microsoft. A cell phone service company might be a viable partner or Canonical and someone, or RIM or Google or an appliance maker that has not entered the netbook market yet.

If they really want to sell netbooks with ARM processors in them they have to think big. They need to better than hope MS is scared. They need to commit to building a system that bypasses MS's core monopolies through vertical integration. This is no small task. They need the hardware, which has to be cheap and hit a sweet spot. They need an OS and applications. They need dev tools for applications and services. They need Web and network services integrated with the device. More than all those pieces which are out there, they need someone to put it all together in a nice package and usability test the whole user experience from buying to opening the box right up through using it for all the common tasks: Web surfing, E-mail, chat, word processing, potentially phone calls and videophone, playing games, playing music and video, and adding new applications. The problem with a lot attempts at this sort of thing is the assumption that someone else will take care of parts or that blaming someone else somehow makes a failure better.

Re:Goody

[TheRaven64]

Any half-decent OS (I think this even include Linux these days) uses the same drivers on multiple architectures with just an abstraction layer for dealing with the different busses. OpenBSD on ARM, for example, supports exactly the same set of USB devices as OpenBSD on x86, including things like USB video cameras. If anything, supporting multiple architectures improves the quality of the code. NetBSD and OpenBSD both recommend testing all drivers on x86 and SPARCv9 and this has helped find a lot of bugs that are not obvious on x86 but crash on SPARC, which has improved the drivers and benefitted x86 users.

Re:What does it support?

[QuantumRiff]

Just out of curiosity, does the ARM version of Ubuntu take advantage of some of the stuff in ARM for doing HD video at low power? Or is it just ubuntu, recompiled for the architecture? There are several advantages to each different CPU. Do things like Flash (or even Gnash) work on ARM? Or VLC, or anything?