<feed xmlns='http://www.w3.org/2005/Atom'>
<title>esp32p4.git/cpu-docs/espressif-custom-isa, branch main</title>
<subtitle>ESP32-P4</subtitle>
<id>https://git.0x4200.cafe/esp32p4.git/atom?h=main</id>
<link rel='self' href='https://git.0x4200.cafe/esp32p4.git/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://git.0x4200.cafe/esp32p4.git/'/>
<updated>2026-08-25T19:17:41Z</updated>
<entry>
<title>Archive the vendor and ISA documents this port was read against</title>
<updated>2026-08-25T19:17:41Z</updated>
<author>
<name>Gabriel Schneider</name>
<email>gbrls@0x4200.cafe</email>
</author>
<published>2026-08-25T18:42:03Z</published>
<link rel='alternate' type='text/html' href='https://git.0x4200.cafe/esp32p4.git/commit/?id=9ab0cbb93dd7678dcc8e86e164325e7d1b8ea7c6'/>
<id>urn:sha1:9ab0cbb93dd7678dcc8e86e164325e7d1b8ea7c6</id>
<content type='text'>
`cpu-docs/` holds the documents behind the reverse-engineering in this repo, and
`cpu-docs/manifests/` records each source URL with a sha256, a byte count and a
page count. The manifests ARE the archive as far as this history is concerned:
121 MB of vendor PDFs are ignored, exactly as `/zig-pkg/` is, because a re-fetch
is one command away and the manifest makes a drifted document detectable.

The small text sources stay tracked instead of ignored, because Espressif
publishes them in no other form - the esptool serial protocol, firmware image
format and boot-mode selection pages, and the P4's custom PIE/SIMD instruction
reference. There is no PDF to re-fetch in their place.
</content>
</entry>
</feed>
