Should smartphone OEMs design their own chips?
February 23, 2012
It’s amazing how often the argument for OEMs to design chips raises its ugly head in the electronics industry.
You would think that at almost 40 years old, the semiconductor market would be mature enough to put this argument to rest, but the rapid pace of consumer device innovation manages to create micro-ecosystem lifecycles within the industry as a whole.
These lifecycles force the industry participants, both new and old, to constantly evaluate many of the same decisions that were faced before. One such decision is whether a device or systems OEM should design chips, especially the processors—the brains of the device.
To read the full article, click here
Related Semiconductor IP
- Flexible Pixel Processor Video IP
- 1.6T/3.2T Multi-Channel MACsec Engine with TDM Interface (MACsec-IP-364)
- 100G MAC and PCS core
- xSPI + eMMC Combo PHY IP
- NavIC LDPC Decoder
Related Blogs
- Qualcomm and Arm Drink Their Own Champagne
- What are AI Chips? A Comprehensive Guide to AI Chip Design
- Why You Should Create Your Own NPU Benchmarks
- Intel vs. ARM : In the Smartphone Era (Part 1)
Latest Blogs
- Morgan State University (MSU) Leveraging Intel 16 and the Cadence Tool Flow for Academic Chip Tapeout
- Securing the Future of Terabit Ethernet: Introducing the Rambus Multi-Channel Engine MACsec-IP-364 (+363)
- Why Weebit’s IP Licensing Model Matters
- Arasan’s xSPI/eMMC5.1 PHY: Unified Dual-Mode Physical Layer IP
- Evolution of CXL PBR Switch in the CXL Fabric