One Pixel Then Another: How to Run DOOM on an E‑Reader
summary
A developer shows how they ported the Doom engine to a jailbroken Kindle e‑reader: they used a purchased WAD and compiled Doom Generic for an ARM Cortex‑A8 with a large crosstool‑ng ARM toolchain to produce an ARM binary. The port opens /dev/fb0 and /dev/input/event1, converts RGB frames to e‑ink values using black/white plus error‑diffusion dithering, and runs at about 10 FPS in portrait mode with no sound, making it playable but slow and monochrome.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:09Porting Doom to devices
- 4:38Kindle E Ink display
- 6:45Jailbreaking Kindle
- 9:11Tools and SSH setup
- 13:00First compilation tests
- 14:45Cross-compilation challenges
- 19:21Kindle toolchain
- 20:50Doom architecture
- 23:14Doom Generic adaptation
- 25:40E Ink pixel display
- 28:09Kindle frame buffer
- 31:01Kindle input handling
- 33:30Running Doom on Kindle
- 35:56Fluidity and rendering issues
- 37:59Grayscale to black and white
- 39:23Error diffusion rendering
- 43:33Final demo and review
related talks
17mHow We Got DOOM Running on Zephyr (And Why You Should Try It)
23mDo You Want to Play Doom in Your Browser?
21mJS Games on Retro Handheld Devices
29mOnce Upon A Time, Somewhere Between Your Console And Browser
57mIgnite
10mLearning to code with Doom! (Now I’m even more confused!)
18mEmulating the Nintendo Game Boy CPU with Elm
26mResponsive HTML5 games - on microcontrollers