Print 35 comment(s) - last by ekv.. on Dec 23 at 10:46 PM

Microsoft will reportedly announced in a couple weeks a new version of Windows, which runs on ARM CPUs, like Apple's iOS. The OS will be put on new Windows tablets, geared to compete with the best-selling iPad.
Intel can't be happy with this news

While Windows Phone 7 runs happily on ARM-architecture processors, suffice it to say that no traditional version of Windows has ever run on an ARM CPU.  But according to reports, Microsoft Corp. is preparing a full fledged ARM-based Windows in an attempt to capture tablet market share.

According to 
Bloomberg and The Wall Street Journal, Microsoft has reached an understanding with ARM Holdings Plc. and will announce the coming operating system at the 2011 Consumer Electronics Show, likely during CEO Steve Ballmer's keynote.

The shift seems a logical one.  For mobile applications, ARM is a particularly good fit.  It features much lower power consumption and similar clock speeds versus the rival x86 architecture.  While Intel has come a long way with its low voltage x86 Atom platform, it still lags behind ARM's designs in power efficiency.

In the long run, the announcement of an ARM-based Windows could spell very bad news for Intel, and to a lesser extent smaller competitor Advanced Micro Devices. 

The irony there is that Intel used to produce ARM CPUs, but in what now looks like an unwise move, it divested itself of those holdings.  After purchasing the Digital Equipment Company (DEC), Intel continued to design and produce the company's ARM-based "StrongARM" processors for mobile devices.  In 2000 it transitioned to a newly named line of ARM CPUs called XScale.  

But in 2006 it sold its XScale mobile processor unit to Marvell.  An XScale processor is found in the Blackberry Torch, among other devices.  To this day Intel and Marvell still co-own some XScale processor lines -- but only network processors, embedded processors and their ilk.  Intel firmly passed away its rights to mobile ARM designs -- a move it likely is now beginning to regret.

Furthering Intel's troubles has been its laggard pace at pushing out improvements to its Atom platform.  Microsoft had hoped to release Windows tablets this year, but delays to Intel's Windows-compatible Oak Trail (Atom) platform dashed those hopes. 

Currently the biggest ARM CPU makers are Qualcomm Inc., Texas Instruments Inc., Marvell Technology Group, and Samsung Electronics Co.

Robert Breza, a Minneapolis-based analyst for RBC Capital Markets, estimates that an ARM-powered Windows tablet would be as cheap as the iPad and could take 10 to 20 percent of an estimated 50 million unit tablet market last year.  But he says the company has to deliver, commenting, "They've got to come back with a product that’s better than 'me too' and is equal if not better in features.  A lot of tablets today are inferior to PCs."

Comments     Threshold

This article is over a month old, voting and posting comments is disabled

A question
By aegisofrime on 12/22/2010 9:59:51 AM , Rating: 2
I have been wondering about this. In a recent Anandtech article about the CR-42, I seem to remember something about how applications written for the Chrome OS will run fine regardless of the underlying hardware platform. Is that actually possible? Will it work here as well? Will current Windows applications work on a Windows written for ARM?

RE: A question
By mforce on 12/22/2010 10:26:43 AM , Rating: 2
Current Windows apps are compiled to run on x86 CPUs. Apple had this problem when they made the switch from PowerPC to X86 and yes there are solutions like Apple had with Rosetta which is based on this
You do need some special software to translate from one instruction set to another.

RE: A question
By Flunk on 12/22/2010 10:48:57 AM , Rating: 2
Well, it is possible that .NET apps might. .NET is meant to be platform agnostic but based on the difference in interface I expect they will probably need some code changes.

RE: A question
By PsychoPif on 12/22/2010 12:42:26 PM , Rating: 2
MS would need a new Just-In-Time compiler, but I doubt developers would have to change much.

There is already a .Net framework for Windows Phone 7, which run on ARM, and you don't need any recoding to port your application from the phone to the PC. You just have limited fonctionality.

RE: A question
By omnicronx on 12/22/2010 1:02:38 PM , Rating: 2
.NETCF is a subset of .NET, so yes you can obviously port from phone applications to full blown desktop applications, just not the other way around.

As for JIT.. I'm not sure what you are talking about.. .NET in general heavily depends on JIT.. i.e why would they need a new JIT compiler? (in fact they already have two, standard JIT for optimized, and EconoJIT for unoptimized code with obvious speed increase)

RE: A question
By Shadowself on 12/23/2010 9:13:41 AM , Rating: 2
Apple had a version of OS X (and before that OS 8 & OS 9) running inside Apple on Intel based platforms for many years under the various code names (StarTrek was the biggest project). Apple admitted this openly when they announced "the switch" to Intel processors. The conversion to an Intel based platform from a Motorola/IBM platform (PowerPC) took several years. Not two.

And for those thinking of the Apple iOS... Apple once owned a significant fraction of Advanced RISC Machines (ARM). Apple sold of most of its stake in ARM back when they were nearly bankrupt just to stay afloat. Apple used an ARM chip in the original Newton. Apple spent many years working on variants of its operating systems for the ARM platforms. Additionally, Apple bought PA Semi to help fine tune the ARM processor for its mobile devices.

Developing for a new architecture -- even if you're basing the software on existing code -- is one hell of a lot of work.

Two years? I doubt it. Microsoft was late with XP and late with Vista (even after jettisoning many of the new core features). I find it very hard to believe they will ship a new mobile OS based on the ARM processor in two years.

RE: A question
By ekv on 12/23/2010 10:46:50 PM , Rating: 2
Two years? I doubt it.
Two points: we don't know how long MS has been considering this. However, they appear to be shooting for a release in two years. Secondly, MS already has some experience developing a "mobile OS", in fact a couple: CE versions (ala "kin") and WP7. [You could almost throw min-Win in as well, and who knows what other research versions there are].

RE: A question
By DanNeely on 12/22/2010 11:04:05 AM , Rating: 2
ChromeOS "applications" are just web pages. As long as Google can get the Chrome browser to run on the hardware everything is golden.

Porting the entire windows OS to ARM is a much more ambitious endevour, but if MS can pull it off the only apps that won't be able to run after a recompile are those that have native assembly code in them. .Net apps will be easier as long as they don't call any 3rd party C++ libraries they should run without doing anything. The only other fly in the ointment would be .net apps explicitly built for x86 or x64 instead of AnyCpu. Unless something changes in the MSIL itself it should be possible to thump most of them over without effort. The problem again would be those that are x86 because they're calling 3rd party libraries that are 32bit only; most I suspect are set as x86 only because the VS2010 debugger is less capable with x64 apps.

RE: A question
By niva on 12/22/2010 2:54:51 PM , Rating: 2
Chrome OS is linux kernel underneath, so properly writetn applications can be compiled to run on any platform. The key word is properly in the previous sentence :)

RE: A question
By Spivonious on 12/23/2010 8:36:33 AM , Rating: 2
Since Chrome OS apps are written in Java, yes. Java inserts a virtual machine (JVM) between the app and the OS. This means that as long as the JVM is there (and supports the needed features), the app will run without recompiling. At compile time, the Java code is turned into Java bytecode. This is turned into machine code at runtime.

For all intents and purposes, .NET is the same way. There are technical differences, but as long as the CLR exists for the platform, the app will run without recompiling. At compile time the C#/VB/whatever is turned into CIL. This is turned into machine code at runtime.

Most Windows apps are compiled to machine code, so you can't switch the CPU type without recompiling the app. They are turned into x86/x64 code at compile time.

RE: A question
By Spivonious on 12/23/2010 8:37:39 AM , Rating: 2
D'oh, forget the ChromeOS part. I had Android OS on the brain. Chrome OS "apps" are all web pages with access to local storage. As long as ChromeOS supports the hardware, then any ChromeOS app will run.

"My sex life is pretty good" -- Steve Jobs' random musings during the 2010 D8 conference

Copyright 2016 DailyTech LLC. - RSS Feed | Advertise | About Us | Ethics | FAQ | Terms, Conditions & Privacy Information | Kristopher Kubicki