EV74 device kernels
Start with a typed request, not a legacy graph control. The current support matrix defines each operation's tensors, parameters and backend availability. Shared transforms use the same request for A65 and EV74; EV-only operations have no A65 fallback.
Runtime owns allocation, mappings, coherency, asynchronous submission and retirement. Kernels owns metadata admission, native descriptor encoding and numerical execution. C++ request and plan objects are not wire descriptors.
Native typed operations
Choose the operation guide for its exact mathematical and device contract:
| Transform | Native guide |
|---|---|
| Scalar format conversion | Cast |
| INT8 dequantization | Dequant |
| Floating-point quantization to INT8 | Quant |
| Conversion and BF16 MLA packing | CastTess |
| Quantization and INT8 MLA packing | QuantTess |
| BF16 MLA unpacking and conversion | DetessCast |
| INT8 MLA unpacking and dequantization | DetessDequant |
| Bit-preserving MLA packing/unpacking | Tess, Detess |
EV-only perception operations
| EV-only operation | Native guide |
|---|---|
| Image preprocessing | Preproc |
| Intensity histograms | Histogram |
| Corner extraction | FAST |
| Corners and binary descriptors | FAST+BRIEF |
| Camera RGB, metric depth and XYZ | SIMOR depth map |
| Sparse point tracking | Tracker |
Prepare metadata through canonical check_inference(); Runtime adds backend
admission and actual buffer-binding checks. Follow the
asynchronous lifecycle.
The matching Runtime package documents its concrete connection recipe in
docs/linux-cvu.md and its executor in docs/async-execution.md. Selecting EV74
alone does not configure a transport or install firmware.
Every native route requires explicit matching firmware composition and a verified capability. Missing capability fails closed; it does not select a legacy graph or silently fall back to A65. Host codecs, mock dispatch and successful builds are not device correctness or latency qualification.
Memory, builds and verification
- Memory and dataflow: buffer ownership, local DMA and completion.
- Private build requirements: toolchain and qualification boundaries.
- Implementation inventory: source families, not interchangeable APIs.
See the generated native identity reference.