zlacker

Intel spent years trying to get manufacturers to use their x86 chips in phones, but manufacturers turned them down, because the power efficiency was never good enough.

>>lmm+(OP)
You're basically reiterating exactly what I just said. Intel had no interest in licensing ARM's IP, they'd have made more money selling their fab space for Cortex designs at that point.

Yes, it cost Intel their smartphone contracts, but those weren't high-margin sales in the first place. Conversely, ARM's capricious licensing meant that we wouldn't see truly high-performance ARM cores until M1 and Neoverse hit the market.

>>bigyab+q2
> Intel had no interest in licensing ARM's IP, they'd have made more money selling their fab space for Cortex designs at that point.

Maybe, but the fact remains that they spent years trying to make an Atom that could fit the performance/watt that smartphone makers needed to be competitive, and they couldn't do it, which pretty strongly suggests it's fundamentally difficult. Even if they now try to sour-grapes that they just weren't really trying, I don't believe them.

>>lmm+T7
I think we're talking past each other here. I already mentioned this in my original comment:

  ARM is typically [...] more efficient at idle.

From Intel's perspective, the decision to invest in x86 was purely fiscal. With the benefit of hindsight, it's also pretty obvious that licensing ARM would not have saved the company. Intel was still hamstrung by DUV fabs. It made no sense to abandon their high-margin datacenter market to chase low-margin SOCs.

>>lmm+(OP)
Well, they were targeting Android, and the apps were emulating ARM on x86, and they were going against a strong incumbent. Accounts on the web of this failure seem to bring up other failings as the main problems.

>>fulafe+TJ
Eg this review of the AZ210 phone from 2012 seems to think the battery life was good: https://www.trustedreviews.com/reviews/orange-san-diego

"Battery life during our test period seemed to be pretty good and perhaps slightly better than many dual-core Android phone’s we’ve tested."

>>fulafe+TJ
> the apps were emulating ARM on x86

They weren't (except some games maybe). Most apps were written in Java and JITed.

>>IshKeb+F01
Well, apps tuned for performance and apps using native code have more than a little overlap. Even back then there were a lot of apps besides games that used native code for the hot code paths. But games of course are huge by themselves, and besides performance you need to have good power efficiency in running them.

Here's some more details: https://www.theregister.com/2014/05/02/arm_test_results_atta...

(note it's a 2-part, the "next page" link is small print )