Less than a month ago, Texas Instruments revealed a change of focus for its processor division, which makes the OMAP chips used in a range of smartphones and tablets. Instead of concentrating on those product categories, Senior Vice President of Embedded Processing Greg Delagi told investors the company would devote more effort to wooing industrial clients like automobile makers. Delagi expects slower growth in the embedded market, but he anticipates it will "generate a more stable long-term business" than competing in the wireless device market.
If the latest rumor is to be believed, there might be one player who is happy to chase that purportedly shorter-term wireless growth. According to Israeli site Calcalist, Amazon is in talks to buy TI's OMAP division. The deal could be worth billions, the site says, and Gizmodo points out that Calcalist's sources have some credibility; they were the first to reveal Apple's takeover of Anobit last year.
There's good reason for Amazon to be interested in picking up the OMAP division, of course. The company's Kindle tablets, including the latest HD models, all use Texas Instruments processors. Amazon has been widely rumored to be interested in making a phone, as well, and the OMAP line has certainly proven itself in that field. Bringing processor development in-house should help Amazon compete with Apple and Samsung, which design their own chips. The move would also give Amazon an important edge over device makers who source SoCs from other firms.
|Gigabyte's Z170X-Gaming G1 motherboard reviewed||10|
|Star Wars Battlefront video review||38|
|Club 3D active adapters convert DisplayPort 1.2 to HDMI 2.0||22|
|Phanteks' Power Splitter lets two systems run on one PSU||45|
|Just Cause 3 system requirements won't blow up your wallet||28|
|Biostar's GeForce Gaming GTX 950 glows a fiery red||23|
|Asus updates Zenbook UX305 with a Skylake Core M CPU||63|
|Shuttle XPC Nano's svelte body is clad in black and gold||20|
|AMD ends driver support for non-GCN Radeon cards||87|
|This is the answer to SSK's question on the Firefox news post.||+33|