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

  • Mastering AI Development and Building AI Apps with GitHub Copilot

    Two Microsoft experts explain how GitHub Copilot is evolving from a coding assistant into a broader platform for building, customizing and testing AI-powered developer workflows.

  • VS Code 1.123 Adds Agent Session Sync, 1M Context Windows

    Microsoft released Visual Studio Code 1.123 on June 3, adding agent-focused features, larger model context support, integrated browser updates and a new delay for some automatic extension updates.

  • Copilot Billing Shock Hits Developers

    Developer complaints about GitHub Copilot's new usage-based billing model have centered on unexpectedly rapid AI credit consumption, and neither GitHub nor Microsoft has responded directly to the backlash, though they have previously published guidance to lessen model usage costs.

  • Hands On with GitHub Copilot App Technical Preview: Turning a Blazor Issue into a PR

    GitHub's brand-new Copilot desktop app, in technical preview, handled a small Blazor issue from planning through pull request creation, but the hands-on test also showed why developers still need to verify agent work in the running app before merging.

Subscribe on YouTube