rajamesandClaude Opus 5.5 a425f738a4 fix(kernel): the block chain's fast RAM is cleared on the v3 path ...

It came from kmalloc, which does not clear what it hands out; only the
ramdrive beside it was cleared.  A VM's BLOCK on blocks 0 to 2047 read
whatever had been in the kernel's heap.  The v4 path already cleared its
own.

Accepted on the v3 configuration: amd64, aarch64 and riscv64 reach the
zuse prompt, no UNKNOWN WORD, PARITY:M7.1a hash 0x08873e0f44b7cb2a on all
three, as before.  logs/20261007-140609, -140735, -140946.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-07 14:10:49 -04:00

..

include/starkernel

feat(v4.0.0): every node asks the kernel for its blocks; a born node is not POSTed

2026-10-07 08:24:47 -04:00

linker

Reorganize source tree: kernel/, v3/, v4/ split and board infrastructure

2026-10-01 15:40:09 -04:00

src

fix(kernel): the block chain's fast RAM is cleared on the v3 path

2026-10-07 14:10:49 -04:00

Makefile

feat(v4.0.0): POST is the kernel's -- the boot feeds the cases, and nothing of the harness is on the node

2026-10-07 10:59:02 -04:00