Purpose
Preserve the allo-side OPEN items from the mininpu -> allo integration
handoff before the parent-directory handoff document is deleted. These
are the items that mininpu/allo/charter.md does NOT already capture,
so they would be lost with the handoff doc. Each needs an allo-side
decision or design.
Open items to preserve
-
Lockstep bump protocol on an isa.py change. Define the ordering
and ownership when the ISA changes: who bumps allo-spec versus the
allo compiler, and in what order, so the two never drift out of sync.
-
Internal reorganization of ../allo. Branch strategy and the
boundary between mininpu-specific support and generic Allo support:
what stays fork-local versus what is upstreamable, and how the tree
is laid out.
-
Compiler-side features the compute-tile reproduction needs first
(beyond #import). Enumerate and prioritize the minimum compiler
surface required to reproduce a compute tile.
-
#import(HLS) / #import(RTL) expression and lowering. How these
import forms are written in the source language and how each is
lowered through the compiler.
-
Multi-backend #to LLM|HLS|BSV routing. How the #to directive
selects and structures the code path to each backend.
-
Versioning / release cadence of ../allo relative to mininpu ISA
releases: how allo releases are cut and how they line up with ISA
release points.
-
Host-runtime decisions. The runtime moves to C/C++ with
PetaLinux + UIO/udmabuf, REPLACING PYNQ; Python/PYNQ is demoted;
../mininpu-runtime is folded in and ARCHIVED.
- NOTE:
mininpu/allo/charter.md lines 40-41 currently CONTRADICT
this by still describing mininpu-runtime as a live sibling repo.
That charter needs reconciling on the mininpu side to reflect the
fold-in-and-archive decision.
Follow-up
Once these are captured/decided here, the parent-directory handoff doc
is safe to delete; mininpu/allo/charter.md should be reconciled on the
mininpu side (item 7 note).
Purpose
Preserve the allo-side OPEN items from the mininpu -> allo integration
handoff before the parent-directory handoff document is deleted. These
are the items that
mininpu/allo/charter.mddoes NOT already capture,so they would be lost with the handoff doc. Each needs an allo-side
decision or design.
Open items to preserve
Lockstep bump protocol on an
isa.pychange. Define the orderingand ownership when the ISA changes: who bumps allo-spec versus the
allo compiler, and in what order, so the two never drift out of sync.
Internal reorganization of
../allo. Branch strategy and theboundary between mininpu-specific support and generic Allo support:
what stays fork-local versus what is upstreamable, and how the tree
is laid out.
Compiler-side features the compute-tile reproduction needs first
(beyond
#import). Enumerate and prioritize the minimum compilersurface required to reproduce a compute tile.
#import(HLS)/#import(RTL)expression and lowering. How theseimport forms are written in the source language and how each is
lowered through the compiler.
Multi-backend
#to LLM|HLS|BSVrouting. How the#todirectiveselects and structures the code path to each backend.
Versioning / release cadence of
../allorelative to mininpu ISAreleases: how allo releases are cut and how they line up with ISA
release points.
Host-runtime decisions. The runtime moves to C/C++ with
PetaLinux + UIO/udmabuf, REPLACING PYNQ; Python/PYNQ is demoted;
../mininpu-runtimeis folded in and ARCHIVED.mininpu/allo/charter.mdlines 40-41 currently CONTRADICTthis by still describing
mininpu-runtimeas a live sibling repo.That charter needs reconciling on the mininpu side to reflect the
fold-in-and-archive decision.
Follow-up
Once these are captured/decided here, the parent-directory handoff doc
is safe to delete;
mininpu/allo/charter.mdshould be reconciled on themininpu side (item 7 note).