Article: Medfield, Intel's x86 Phone Chip
By: Doug Siebert (foo.delete@this.bar.bar), January 26, 2012 1:20 pm
Room: Moderated Discussions
David Kanter (dkanter@realworldtech.com) on 1/25/12 wrote:
---------------------------
>Andreas (kingmouf@gmail.com) on 1/25/12 wrote:
>---------------------------
>>I'm afraid that the success of Medfield and its follow-ons could be something that
>>simply is not related to performance or performance per watt or whatever. From the
>>point that Medfield is simply usable or at least in the same ballpark with ARM offerings
>>then it is marketing, carriers and design tricks that will do the job (or not) for Intel.
>>
>>We are talking here in a tech savvy forum. But people who actually buy phones,
>>know nothing about ARM, TI, Tegra whatever. They know Apple, Android (probably),
>>Verizon, things like that. Most probably they have heard Intel, so a program like
>>"Intel Inside" could work for them (what would the average user make of a "nVidia
>>Inside" or even worse "TI inside"? ). People will probably buy the slick design
>>phone (e.g. iPhone), or the one that is on offer by their carrier.
>>
>>Intel just needs to be in the same ballpark with ARM. It doesn't need to have the
>>highest performing device nor the lowest power consuming. After that it all comes
>>to the marketing money it is willing to spend. And it has a lot more money than any of the other players.
>
>Actually it's a lot more complicated than that. Motorola, HTC, etc. are all quite
>savvy buyers and can spend significant resources to investigate the power efficiency and performance.
True, but if Intel is willing to spend hundreds of millions to support an inferior technology via marketing money, as they did back in the Prescott days, that could swing some things their way. But it wouldn't be sticky, once the marketing money stops there'd be no reason to stay with Intel. If so, why do it? Because having higher prices and offering marketing dollars as a way to lower your customer's actual per unit prices allows you to claim a higher ASP to your shareholders. Being able to show gross margins comparable to that they maintain for PC CPUs would keep Intel shareholders happy and their stock price from dropping. Which it would if shareholders believed Intel was generating a lot of new revenue from entering a lower margin line of business. Because the kickbacks are counted as a marketing cost rather than a reduction in sales revenue, they count against net profit but not gross margin!
I am however skeptical of Andreas' idea about "Intel Inside" carrying any market weight. That worked for PCs because back when they started that DRAM was very expensive. So the lower end PCs that used the non-Intel CPUs to save money also shortchanged the user on RAM, so a CPU that was at worst 50% slower than a Pentium resulted in a PC that several times slower. People didn't realize how much an extra few megabytes of RAM helped back then, and incorrectly believed the CPU was to blame. Intel was able to capitalize on the bad rep those non-Intel alternatives had. I don't believe a similar situation exists in the current smartphone market, and if anything Intel having to translate ARM code risks making them look like the crap alternative where phones are concerned.
Honestly I think Intel's biggest problem is going to be their decision to support translating ARM code. If it performs poorly, it makes Intel phones look crappy and they become what Cyrix was in the early 90s. If performs good enough, then there's no incentive for anyone to ever write x86 versions of their apps. Intel's process advantage would always be totally negated by the translation overhead. Intel is about two years too late, and IMHO the best they can possibly hope for is to be the AMD of the smartphone market. Even that is only possible if Windows Phone becomes a strong third player in the smartphone market - I think they'll be third but probably not a strong third. Basically, third only because RIM will probably be bought out (possibly by Microsoft) within 18 months for their patents and Exchange integration technology.
---------------------------
>Andreas (kingmouf@gmail.com) on 1/25/12 wrote:
>---------------------------
>>I'm afraid that the success of Medfield and its follow-ons could be something that
>>simply is not related to performance or performance per watt or whatever. From the
>>point that Medfield is simply usable or at least in the same ballpark with ARM offerings
>>then it is marketing, carriers and design tricks that will do the job (or not) for Intel.
>>
>>We are talking here in a tech savvy forum. But people who actually buy phones,
>>know nothing about ARM, TI, Tegra whatever. They know Apple, Android (probably),
>>Verizon, things like that. Most probably they have heard Intel, so a program like
>>"Intel Inside" could work for them (what would the average user make of a "nVidia
>>Inside" or even worse "TI inside"? ). People will probably buy the slick design
>>phone (e.g. iPhone), or the one that is on offer by their carrier.
>>
>>Intel just needs to be in the same ballpark with ARM. It doesn't need to have the
>>highest performing device nor the lowest power consuming. After that it all comes
>>to the marketing money it is willing to spend. And it has a lot more money than any of the other players.
>
>Actually it's a lot more complicated than that. Motorola, HTC, etc. are all quite
>savvy buyers and can spend significant resources to investigate the power efficiency and performance.
True, but if Intel is willing to spend hundreds of millions to support an inferior technology via marketing money, as they did back in the Prescott days, that could swing some things their way. But it wouldn't be sticky, once the marketing money stops there'd be no reason to stay with Intel. If so, why do it? Because having higher prices and offering marketing dollars as a way to lower your customer's actual per unit prices allows you to claim a higher ASP to your shareholders. Being able to show gross margins comparable to that they maintain for PC CPUs would keep Intel shareholders happy and their stock price from dropping. Which it would if shareholders believed Intel was generating a lot of new revenue from entering a lower margin line of business. Because the kickbacks are counted as a marketing cost rather than a reduction in sales revenue, they count against net profit but not gross margin!
I am however skeptical of Andreas' idea about "Intel Inside" carrying any market weight. That worked for PCs because back when they started that DRAM was very expensive. So the lower end PCs that used the non-Intel CPUs to save money also shortchanged the user on RAM, so a CPU that was at worst 50% slower than a Pentium resulted in a PC that several times slower. People didn't realize how much an extra few megabytes of RAM helped back then, and incorrectly believed the CPU was to blame. Intel was able to capitalize on the bad rep those non-Intel alternatives had. I don't believe a similar situation exists in the current smartphone market, and if anything Intel having to translate ARM code risks making them look like the crap alternative where phones are concerned.
Honestly I think Intel's biggest problem is going to be their decision to support translating ARM code. If it performs poorly, it makes Intel phones look crappy and they become what Cyrix was in the early 90s. If performs good enough, then there's no incentive for anyone to ever write x86 versions of their apps. Intel's process advantage would always be totally negated by the translation overhead. Intel is about two years too late, and IMHO the best they can possibly hope for is to be the AMD of the smartphone market. Even that is only possible if Windows Phone becomes a strong third player in the smartphone market - I think they'll be third but probably not a strong third. Basically, third only because RIM will probably be bought out (possibly by Microsoft) within 18 months for their patents and Exchange integration technology.
Topic | Posted By | Date |
---|---|---|
Medfield article online | David Kanter | 2012/01/23 01:51 PM |
server error | bakaneko | 2012/01/24 03:00 AM |
Fixed | David Kanter | 2012/01/24 04:02 AM |
Fixed | Joel | 2012/01/24 07:43 AM |
Fixed | Ricardo B | 2012/01/24 11:25 AM |
Fixed | David Kanter | 2012/01/24 05:29 PM |
Fixed | Gabriele Svelto | 2012/01/24 01:07 PM |
Fixed | David Kanter | 2012/01/24 05:30 PM |
Reference platform battery life | Doug Siebert | 2012/01/24 02:03 PM |
standby time | Foo_ | 2012/01/25 06:58 AM |
standby time | Anon | 2012/01/26 03:42 AM |
standby time | Foo_ | 2012/01/26 04:02 AM |
standby time | Doug Siebert | 2012/01/26 12:39 PM |
standby time | Anon | 2012/01/26 01:22 PM |
standby time | anon | 2012/01/26 02:08 PM |
standby time | Anon | 2012/01/26 06:03 PM |
standby time | anon | 2012/01/26 08:57 PM |
standby time | anon | 2012/01/26 09:01 PM |
standby time | Anon | 2012/01/27 09:32 PM |
standby time | Doug Siebert | 2012/01/27 02:15 PM |
standby time | anon | 2012/01/27 02:41 PM |
Reference platform battery life | David Kanter | 2012/01/27 10:09 AM |
Performance analysis laughable | Wilco | 2012/01/24 03:23 PM |
Performance analysis laughable | David Kanter | 2012/01/24 05:19 PM |
Performance analysis laughable | IntelUser2000 | 2012/01/24 07:30 PM |
Performance analysis laughable | IntelUser2000 | 2012/01/24 07:32 PM |
Performance analysis laughable | David Kanter | 2012/01/24 11:34 PM |
Performance analysis laughable | IntelUser2000 | 2012/01/24 11:56 PM |
Performance analysis laughable | David Kanter | 2012/01/25 02:07 AM |
Performance analysis laughable | Alberto | 2012/01/25 12:54 PM |
Atom HT gain | Wilco | 2012/01/25 05:43 AM |
Atom HT gain | IntelUser2000 | 2012/01/25 06:53 AM |
Atom HT gain | none | 2012/01/25 07:04 AM |
Atom HT gain | IntelUser2000 | 2012/01/25 07:35 AM |
Atom HT gain | Foo_ | 2012/01/25 07:06 AM |
Performance analysis laughable | Wilco | 2012/01/24 08:21 PM |
Performance analysis laughable | David Kanter | 2012/01/24 10:13 PM |
Performance analysis laughable | Wilco | 2012/01/25 04:30 AM |
Performance analysis laughable | none | 2012/01/25 06:14 AM |
Performance analysis laughable | Wilco | 2012/01/25 07:18 AM |
Performance analysis laughable | observer | 2012/01/26 04:17 AM |
Performance analysis laughable | Wilco | 2012/01/26 06:25 AM |
Process numbers | Alberto | 2012/01/26 09:29 AM |
Performance analysis laughable | David Kanter | 2012/02/02 12:38 AM |
Performance analysis laughable | tupper | 2012/01/25 04:27 PM |
Performance analysis laughable | Linus Torvalds | 2012/01/25 08:37 PM |
Performance analysis laughable | Doug Siebert | 2012/01/26 02:12 PM |
Medfield article online | Andreas | 2012/01/25 03:10 AM |
Medfield article online | Alberto | 2012/01/25 09:44 AM |
Medfield article online | IntelUser2000 | 2012/01/25 10:24 AM |
Medfield article online | David Kanter | 2012/01/25 09:58 PM |
Medfield article online | Doug Siebert | 2012/01/26 01:20 PM |
Medfield article online | Eric | 2012/01/26 06:10 PM |
Medfield article online | Doug Siebert | 2012/01/27 02:40 PM |
64-bit | Ingeneer | 2012/01/25 09:28 AM |
64-bit | Foo_ | 2012/01/25 10:23 AM |
64-bit | Ingeneer | 2012/01/25 02:34 PM |
64-bit | Ungo | 2012/01/25 04:08 PM |
64-bit | EduardoS | 2012/01/26 12:55 PM |
Saltwell memcpy | SHK | 2012/01/26 02:41 AM |
Medfield WiFi & Bluetooth | Rob Thorpe | 2012/01/26 03:09 AM |
Medfield WiFi & Bluetooth | David Kanter | 2012/01/27 05:54 PM |
Medfield WiFi & Bluetooth | Rob Thorpe | 2012/01/28 02:22 PM |
Medfield article online (NT) | Anil | 2012/01/26 05:57 PM |
Medfield article online | Anil | 2012/01/26 06:11 PM |
Medfield article online | Mr. Camel | 2012/01/26 06:26 PM |
Medfield article online | none | 2012/01/27 01:41 AM |