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
- NFC wireless interface supporting ISO14443 A and B with EEPROM on SMIC 180nm
- DDR5 MRDIMM PHY and Controller
- RVA23, Multi-cluster, Hypervisor and Android
- HBM4E PHY and controller
- LZ4/Snappy Data Compressor
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
- lowRISC Tackles Post-Quantum Cryptography Challenges through Research Collaborations
- How to Solve the Size, Weight, Power and Cooling Challenge in Radar & Radio Frequency Modulation Classification
- Programmable Hardware Delivers 10,000X Improvement in Verification Speed over Software for Forward Error Correction
- The Integrated Design Challenge: Developing Chip, Software, and System in Unison
- Introducing Mi-V RV32 v4.0 Soft Processor: Enhanced RISC-V Power