From 051fa32a31fab2980b5e8af3113befc83d7914b3 Mon Sep 17 00:00:00 2001 From: Gabriel Schneider Date: Tue, 15 Sep 2026 20:36:53 -0300 Subject: Fetch cloud9 from sourcehut, and correct the citations into the board toolchain --- src/esp32p4/app.zig | 4 ++-- src/esp32p4/input_rescue.zig | 13 ++++++++----- 2 files changed, 10 insertions(+), 7 deletions(-) (limited to 'src') diff --git a/src/esp32p4/app.zig b/src/esp32p4/app.zig index ae5679f3..4ee131ec 100644 --- a/src/esp32p4/app.zig +++ b/src/esp32p4/app.zig @@ -35,7 +35,7 @@ //! builds, it is what every measurement in that repository's `experiments/` was taken through, and //! it is the firmware build path. Its externs link against that object file. //! The reasons the seam is a file at all - a nested `build.zig.zon` dependency broke every build in -//! the toolchain repository - are recorded in `src/esp32p4.zig:8-15` and `05-zig-p4/build.zig:238-260`. +//! the toolchain repository - are recorded in `src/esp32p4.zig:8-15` and `05-zig-p4/build.zig:252-272`. //! //! Who owns which symbol: `src/esp32p4.zig` exports all eight `pardes_esp32p4_*` functions and nothing else. //! This file exports `_start`, `zig_main`, `trapEntry` and `trapReport`. `esp_app_desc` belongs to @@ -52,7 +52,7 @@ //! ## Where the memory is //! //! Measured on this die by the toolchain's `examples/memprobe.zig`, not read off a datasheet, and -//! written down once in the generated linker script (`05-zig-p4/build.zig:1572,1579,1584-1585`): +//! written down once in the generated linker script (`05-zig-p4/build.zig:1569,1576,1581-1582`): //! //! 0x4FF00000..0x4FF3F000 252 KiB `l2mem`: .data/.bss/.stack are linked into this //! 0x4FF3F000..0x4FF40000 4 KiB mask ROM .data/.bss - untouchable, ets_printf needs it diff --git a/src/esp32p4/input_rescue.zig b/src/esp32p4/input_rescue.zig index 3f1c0268..ba6974d2 100644 --- a/src/esp32p4/input_rescue.zig +++ b/src/esp32p4/input_rescue.zig @@ -31,11 +31,14 @@ //! same source compile for riscv32-freestanding and for the host unchanged. //! //! ONE COPY, TWO BUILDS. This file is the only copy; the toolchain repository's is gone. Its build -//! reads this tree across a sibling-relative seam, and names this path twice: once as the -//! `input_rescue` module of `-Dpardes`'s application (`05-zig-p4/build.zig:230-231`, whose root is -//! `../02-pardes-code/src/esp32p4/app.zig` by the `-Dapp` default at `:168-169`) and once as the -//! same-named module of `zig build selftest`'s on-die root (`:437-438`). Both spell -//! `../02-pardes-code/src/esp32p4/input_rescue.zig`, so there is nothing to keep in step. +//! reads this tree across a sibling-relative seam in exactly one place: `zig build selftest` hands +//! this path over as the `input_rescue` module of its on-die root (`05-zig-p4/build.zig:434-435`, +//! the module at `:453`). The editor's own application root needs no such wiring - `app.zig` reads +//! the policy through the `uart.zig` beside it, which imports this file as its sibling - and the +//! toolchain deliberately registers no module for it, because zig hashes every registered module's +//! root source on every compile, so registering one that a root does not use breaks every build in +//! a checkout without this tree. `-Dapp` still defaults under `-Dpardes` to +//! `../02-pardes-code/src/esp32p4/app.zig` (`:168-169`). //! //! Host checks run under `zig build unit-test` here. In `../05-zig-p4`, //! `zig build selftest` flashes and runs the on-die checks against UART0. -- cgit v1.3