Hardware/Software Co-design: The Coming Golden Age
summary
Argument: hardware and software must be co-designed because economics and capability are changing, not the topic. Moore’s Law decelerates economically while Wright’s law keeps unit transistor cost falling with volume; speculative execution yields security failures (Spectre/Meltdown); Canon Lake shows process risk. Practical enablers list real tools and numbers: RISC‑V cores, open FPGAs (Lattice iCE40, QuickLogic), Bluespec for high‑level HDL, Rust firmware for small safe boot ROMs; M1 on TSMC 7nm ≈100M transistors/mm²; $30 STM32 H7 and one‑GHz BeagleBone Black make rapid PCB iteration (12 hours ideation → board sent) realistic.
AI-written summary · about
chapters (13)
- 0:00Start
- 2:29Mark Andreessen's 2011 Essay Why Software Is Eating the World
- 7:33Why Is the Chromebook Interesting
- 15:37Moore's Law as the Doubling of Transistor Density
- 22:38Symmetric Multi-Processing
- 28:26How Big Is a Silicon Atom
- 32:50Wright's Law
- 33:11Wright's Law versus Moore's Law
- 37:34Jevin's Paradox
- 45:02Open Instruction Sets
- 46:50Open Fpgas
- 49:46Hardware Description Languages Hdls
- 59:13Hardware Is Eating the World
related talks
01h 09mComputer Architecture, C++, and High Performance
14mRISC-V: The Open Era of Computing
43mClosing Keynote: Safe Systems Software and the Future of Computing
32mHeterogeneous Linux and RTOS Software Architecture for Low-Price RISC-V...
01h 16mPaying for Lunch: C++ in the ManyCore Age
36mIt's Embedded Rust Time
01h 00mBuilding Effective Embedded Systems in C++: Architectural Best Practices
55mComprehensive Testing of Embedded Software