Texas Instrument wants to enter the Windows Phone 7 party

As you probably already know Microsoft has currently only certified one chipset manufacturer for Windows Phone 7  (Qualcomm) and only one SoC model is being used in the first batch of WP7 devices: the QSD8250 Snapdragon. The company has previously announced that this was meant to change in the future but so far nothing new has been said on the this subject. Microsoft’s decision to go with only one chipset manufacturer is obviously a good thing when it comes to hardware and software compatibility between all WP7 devices. It’s because of this that Microsoft was able to pump out one of the smoothest and snappiest OS (and UX) this fall.But as it is always the case in technology, things evolve quickly and MS will now have to start supporting Qualcomm’s newest chipsets ( like the ones found on HTC’s latest Android devices; MSM8x55, MSM7X30) and because OEMs don’t like to be controlled that way Microsoft will also have to decide whether they certify other Chipset Manufacturers or not. For example, even-thought Samsung builds its own mobile SoCs (like the Hummingbird found in the Galaxy S) they were”forced” to use Qualcomm’s QSD82500 on their WP7 devices (Focus and Omnia 7). Texas Instrument, makers of the TI OMAP line of mobiles SOC found in several high profile mobile phones (principally Motorola’s stuff lately) has recently expressed its desire to get into the Windows Phone 7 party:

Going forward, TI’s focus will shift to include other tablets, the open-source MeeGo platform and, possibly, Microsoft’s Windows Phone 7, says Greg Delagi, senior vice president and general manager of the company’s wireless business unit. [...]That crop of phones won’t include any Windows Phone 7 devices, even though TI has worked with Windows Mobile handsets in the past. Based on Microsoft’s specifications, the first batch of WP7 phones runs exclusively on Qualcomm’s Snapdragon platform. Delagi hopes Microsoft will relax its guidelines and let TI in. “Microsoft will have to address questions of platform diversity,” he says. “Right now, it’s requiring manufacturers to lock in to a single architecture.”

Being locked to one single Chipset manufactured is a good thing for developers but business wise this can be risky if this manufacturer screws up something. So it’s entirely up to Microsoft to decide whether it should open up a bit at the risk of making the WP7 ecosystem a bit more fragmented.

source: forbes

  • http://twitter.com/argenys argenys

    Is there a way that Microsoft can Let TI and others in the game without having the same problem as Android? Is there a possiblity of this? Can they guarantee that the developer has not to worry about different chip sets and just code for the platfrom without having issues? Becuase the easy part is getting the Platform to run on the chips its the rest that is tricky.

  • http://bit.ly/samirsshah ???? ???

    To Microsoft: See how well the current architecture does in holiday season and decide on Jan 1.

  • BucksterMcgee

    I have the same question, but some evidence from the past suggests that it’s not only possible, but already planned for by Microsoft.

    First, Microsoft has stated repeatedly that this first chipset is only a limitation for launch and that in the future other chip sets would be able to be used. So right there, other chipsets will be used.

    Secondly, if Microsoft takes a page out of their desktop book, they should be able to get their same platform to run on all different types of hardware, including several different GPU designs. The developers ‘shouldn’t’ notice any difference from hardware to hardware besides different processing amounts, which already happens in all sorts of forms on the desktop, where games are designed to run on both netbook hardware, with bare minimum graphics up to monster quad cpu and gpu configurations. Basically, the amount of graphics change the better hardware you have, but at the very least the run on all hardware.

    From there, you have to remember that everything that developers are writing for in WP7 is managed code, meaning that the biggest hurdless they are jumping are for screen resoltution and available input controls. With the heavy standardization that WP7 has, e.g., they all have exactly the same screen resolution on purpose, devlopers only have to code for that, and they are on their way. Another example is how porting from the PC to Xbox to WP7 can reuse 90%+ of the same code, so if they can move between extremes like that, I’m sure adjusting between different phone hardware would be even easier, if not just exactly the same as any other phone hardware for WP7.

    I think if there is any company in the world that knows how to build a platform for all different types of hardware in every shape and size and make it all work, it’s Microsoft. Apple on the other hand controls every micrometer of their own hardware and still find ways to mess up despite their insane control, and Google despite having impressive success lately still seems like a sloppy attempt to throw their expermental OS where ever it will stick, and then leave it to the wolves. Apple will always have their faithful followers, but as WP7 matures and people see what a real and stable modern mobile OS is supposed to be, they will stop moving to the broken Android world as the not-apple solution and a far more widespread adoption will happen in favor of Microsoft. I’m sure Android will stick around for the tweakers out their, but even then a lot of them are only tweakers because they aren’t getting what they want with their stock choices, if their stock devices did what they wanted them too, then there wouldn’t be as much need to hack and root your rom.