News

Microsoft Charts Long-Term Mobile Strategy With ARM Deal

Microsoft has licensed the architecture for ARM Holdings' mobile microprocessor platform, but the move does not appear likely to have an impact on devices in the near-term pipeline.

ARM, whose processors are widely used in mobile devices, notably Apple's iPhone and iPad, said Microsoft is the first software vendor to say it is taking on an architectural license. The move lets Microsoft customize ARM's family of mobile microprocessors rather than just work off the implementation guidelines.

Microsoft and ARM, which have had licensing agreements since 1997, announced the architectural license on Friday, July 23. The companies are sharing few details other than to suggest that Microsoft will build a larger number of devices using its Windows Embedded and its forthcoming Windows Phone 7 platforms.

"With closer access to the ARM technology we will be able to enhance our research and development activities for ARM-based products," said K.D. Hallman, general manager for Microsoft's strategic software/silicon architectures team, in a statement. A Microsoft spokeswoman said the company is not elaborating on the announcement but reports have speculated that the ARM platform could be key to partners building smartphones and slate PCs that would compete with Apple's iPad.

Hardware vendors Infineon Technologies, Marvell Technology Group and Qualcomm have licensed the ARM architecture, but Microsoft is the first software company to announce such a relationship, according to Antonio Viana, ARM executive board member. Infineon's deal is specifically for security-based devices.

"There are very few architectural licenses," Viana said in an interview. "This gives Microsoft the ability to create custom implementations on the ARM architecture." Viana declined to speculate how Microsoft might customize the architecture, but he did suggest that it is unlikely it would result in near-term deliverables.

"Creating your implementations and then creating SOC's [system on chips] based on those implementations, that's not something that happens overnight. That requires a great deal of investment and a great deal of effort," he said. "There's a fair deal of work involved."

About the Author

Jeffrey Schwartz is editor of Redmond magazine and also covers cloud computing for Virtualization Review's Cloud Report. In addition, he writes the Channeling the Cloud column for Redmond Channel Partner. Follow him on Twitter @JeffreySchwartz.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube