Disclosure: I work for ARM
Regarding Cortex-A15 processor; Our model is to design a processor for multiple markets. The product definition work ensures that ARM profiles the efficiency with which the processor handles multiple workloads. For ARM's applications processors, the first instantiations in actual SoCs are normally focused the mobile arena as evidenced by the 3 lead silicon partners revealed in September 2010 at the Cortex-A15 launch. But the processor's extended addressing, hardware virtualization support and higher performance will, I believe, see it gain adoption over time into a number of additional segments including automotive infotainment, medical and yes, some computing/server applications. One other point. There is nothing in the processor itself that prevents more than 8 or 16 or.. processors to be put down on a piece of silicon. ARM focuses its on-chip interconnect IP toward high volume applications so naturally, this tends to be centered toward smaller processor configurations. Other partners that wish to target higher performance applications are either utilizing their own internally-developed interconnect technology or licensing IP from other 3rd parties to form significantly bigger processor compute subsystems.
Disclosure: I work for ARM..
Been sat reading this thread for the past couple of days trying to decide if/how to chime in here. In this area, I see us as having two beliefs
1) Different applications require different computing requirements. One size does not fit all
2) There is room (indeed there is demand) for technical innovation alongside the processor core to deliver optimized solutions for particular applications. Algorithms that involve bit manipulation are often better handled in hardware than in general purpose processors...
Microsoft's announcement this week delivers an additional element of choice to the ARM ecosystem. It will be massively important for some companies, while this announcement will be a NOP for others.
That is because OS was developed by SW engineers, not HW engineers. There are lots lots of resource wasting in boot process. I hope one day some talent hardware engineers could come up a OS which could have boot time measured in ms not minutes. :-)
Both Intel and AMD produced many different versions of x86 chip with different packages and configuration over years. I don't see any issues for Windows to support that.
If you look Windows 8 news, it is going to support ARM based SoC from Qualcomm/nVidia/TI at the same time. Although all three chips have same ARM core(Qualcomm uses its own core based on ARM architecture), other peripherals devices are vastly different. Open source Linux has been supporting many different flavors of SoC now.
If you look the context of this article, you can find out that we are talking about nVidia being a NOTEBOOK/DESKTOP CPU replacement running Win 8 OS.
For Embedded market what you are saying totally makes sense.
Why people keep bitching about windows boot speed? It is very good to me considering its complexity. Do a quick experiment on your iPhone. Remove battery and put it back on. Time it to see how fast to boot. It is unfair comparison between cold boot speed in PC to wake up speed in your iPhone.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.