Skip to content
Merged
6 changes: 3 additions & 3 deletions docs/core-setup-linux.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ Written against the working install on this machine. Paths use `$P` for the
dependency prefix (here `/home/alfxu/ddprefix`); substitute your own.

> **Status:** the core backend has been run on hardware on Windows only. The
> steps below are updated for corelib 0.60.0, but they have not been run end
> steps below are updated for corelib 0.103.0, but they have not been run end
> to end on Linux at this revision. The [Known issues](#known-issues) are from
> an earlier Linux bring-up.

Expand Down Expand Up @@ -52,14 +52,14 @@ loaded from, so those libraries must sit beside it; nothing else is needed at
run time, no kernel store and no environment variable.

**Version must match exactly.** `src/include/core/corelib_api.hpp` has a
`#error` for anything other than corelib **0.60.0**:
`#error` for anything other than corelib **0.103.0**:

```bash
grep -E 'CORELIB_VERSION_(MAJOR|MINOR|PATCH)' \
$P/install-corelib/include/ryzenai/corelib/base.h
```

Must print `0`, `60`, `0`. (`BUILD-NOTES.md` still says 0.4.0 in its opening
Must print `0`, `103`, `0`. (`BUILD-NOTES.md` still says 0.4.0 in its opening
line — that text is stale.)

### Verify corelib before going further
Expand Down
4 changes: 2 additions & 2 deletions docs/docs/models/phi.md
Original file line number Diff line number Diff line change
Expand Up @@ -75,9 +75,9 @@ The `src/test/phi4_core` suite is still Windows-only and is not configured on Li

### Pointing FastFlowLM at the runtime

A core build (`-DFLM_ENABLE_CORE=ON`) **links corelib in**. corelib keeps its NPU device to itself and opens a hardware context per stream on it; FastFlowLM opens its own device for every other family, and a core model shares no buffer with those. The core backend is offered only where corelib reports a usable NPU (`ryzenai_corelib_npu_usable`): elsewhere corelib would run a session on the GPU or the host. Point the build at the library with `RYZENAI_CORELIB_INCLUDE_DIR` and `RYZENAI_CORELIB_LIBRARY`. `FLM_CORE_CORELIB_PATH` selects a shared library (`.dll` on Windows, `.so` elsewhere) only in the older dynamically loading configuration; in a statically linked core build it is ignored, and `flm` says so if it is set.
A core build (`-DFLM_ENABLE_CORE=ON`) **links corelib in**. corelib keeps its NPU device to itself and opens a hardware context per stream on it; FastFlowLM opens its own device for every other family, and a core model shares no buffer with those. The core backend is offered only where corelib reports an AIEM NPU (`ryzenai_corelib_has_feature(ryzenai_corelib_feature_npu_aiem)`): elsewhere, AIE2P included, corelib would run a session on the GPU or the host. Point the build at the library with `RYZENAI_CORELIB_INCLUDE_DIR` and `RYZENAI_CORELIB_LIBRARY`. `FLM_CORE_CORELIB_PATH` selects a shared library (`.dll` on Windows, `.so` elsewhere) only in the older dynamically loading configuration; in a statically linked core build it is ignored, and `flm` says so if it is set.

The corelib ABI is still pre-1.0, so FastFlowLM requires an **exact `0.60.0`** match on major, minor and patch. The version is queried before any other entry point, so a mismatched runtime reports a version error rather than a missing symbol. corelib's default build installs `ryzenai_corelib` plus one `ryzenai_corelib_model_<name>` library per model, each carrying that model's kernels; corelib loads them only from its own directory, so they must sit beside it (a Windows core build copies them next to `flm.exe`). Each engine enables its model's kernel bundle on the stream it opens; no kernel store or environment variable is involved. Corelib's own dependency directory must be reachable on `PATH` (Windows) or `LD_LIBRARY_PATH` (Linux).
The corelib ABI is still pre-1.0, so FastFlowLM requires an **exact `0.103.0`** match on major, minor and patch. The version is queried before any other entry point, so a mismatched runtime reports a version error rather than a missing symbol. corelib's default build installs `ryzenai_corelib` plus one `ryzenai_corelib_model_<name>` library per model, each carrying that model's kernels; corelib loads them only from its own directory, so they must sit beside it (a Windows core build copies them next to `flm.exe`). Each engine enables its model's kernel bundle on the stream it opens; no kernel store or environment variable is involved. Corelib's own dependency directory must be reachable on `PATH` (Windows) or `LD_LIBRARY_PATH` (Linux).

```powershell
flm pull phi4-mini-it-core:4b
Expand Down
2 changes: 1 addition & 1 deletion docs/docs/models/qwen.md
Original file line number Diff line number Diff line change
Expand Up @@ -111,7 +111,7 @@ flm run qwen3:8b
- **Backend:** `core` — one engine for all four sizes. The GGUF's own metadata selects the size and is cross-checked against it.
- **Source format:** GGUF, read directly by corelib. With a Hugging Face token that can read AMD's private repositories (`HF_TOKEN`, or `hf auth login`), `flm pull` fetches AMD's 4-bit file, which packs exactly as it is; without one, a tag below on an AMD file cannot be pulled, as corelib's own runner has no public fallback either. Only Qwen3-0.6B and Llama, which AMD ships no 4-bit file of, pull a public `Q8_0`, requantized to 4-bit groups on every load, which is lossy; corelib refuses `Q8_0` for Qwen3.5, Qwen3.6, Gemma 4 and Phi-4-mini.
- **Context:** each tag's limit is the most corelib runs that model at; the default is lower where corelib or our own runs found answers going wrong past it. Over-capacity requests are rejected with HTTP 400 before any work reaches the device.
- **Availability:** developer build against corelib 0.60.0 — see [Phi-4 on the core backend](phi.md).
- **Availability:** developer build against corelib 0.103.0 — see [Phi-4 on the core backend](phi.md).

The same corelib path runs every `-core` tag:

Expand Down
Loading
Loading