This commit is contained in:
MrARM
2026-07-07 07:13:01 -05:00
parent 7ff39227fe
commit b2c2355a06
4 changed files with 27 additions and 15 deletions

View File

@@ -24,7 +24,7 @@ Suggested first passes:
Follow-up passes:
- Continue from `emulation/`: QEMU now boots the generated rootfs, exposes noVNC/dashboard, loads `virtio_gpu`, creates `/dev/dri/card0`, and reaches `/games/spike3/bin/boot_display`. The current blocker is `boot_display` `create_window` retries plus shader compile/link failures, so the next pass should focus on Mesa/GBM/EGL userspace compatibility or a targeted display interposer before moving to `spike-menu` and `/games/game`.
- Continue from `emulation/`: QEMU now boots the generated rootfs, exposes noVNC/dashboard, loads `virtio_gpu`, creates `/dev/dri/card0` plus `/dev/dri/renderD128`, and reaches `/games/spike3/bin/boot_display`. `/dev/dri/card1` is shimmed to card0, SPIKE menu's disconnected second-connector failure is patched in the LD_PRELOAD shim, the Mesa/GLVND overlay clears the prior `DRI_Mesa` loader fatal, and the Docker image now includes ARM64 Mesa Vulkan/lavapipe support. The current blocker is earlier than the repeated `gbm_buffer[0] is null` symptom: `eglGetPlatformDisplayEXT(EGL_PLATFORM_GBM_KHR, gbm_device, NULL)` returns `NULL` with `EGL_BAD_PARAMETER` after `gbm_create_device(fd=3)` succeeds. The next pass should focus on making the QEMU non-virgl `virtio_gpu` work with the app's GBM EGL path or implementing a targeted EGL/GBM display interposer before moving deeper into `spike-menu` and `/games/game`.
- Validate `analysis/topper-emulator/topper_emulator.py` on live hardware or a nodebus capture.
- Recover the exact Magikarp topper `IDENTITY_BOARD_PART_ID` expected by command `0xfe`.
- Confirm physical UART pins, baud, voltage level, and any netbridge timing/break behavior required for a MicroPython node.