Legacy Platform Pages
Some older KTransformers pages mention Ascend NPU, Intel xPU, ROCm, AMD BLIS, or old Docker/server paths. Whether they can be used directly depends on whether they match the current package and serving entries.
Current Status
| Platform page type | Current status |
|---|---|
| Ascend NPU old tutorials | Not current support. |
| Intel xPU old tutorials | Not current support. |
| ROCm old tutorials | Legacy; needs current package validation before use. |
| AMD BLIS CPU path | Supported direction; waiting for public model and hardware validation data. |
Old Docker pages using ktransformers.local_chat | Legacy |
NPU and Intel xPU currently do not have a mainline operation path. AMD support needs public validation for the target model, method, and hardware configuration before data is published.
Before Returning to the Current Path
Before using a legacy hardware path as current guidance, make sure it can identify:
- package versions
- exact hardware SKU
- model and checkpoint
- launch command
- smoke prompt and response
- throughput or profiling method if performance is claimed
- known failures and fallback behavior
Until then, treat legacy pages as historical context.