Repository navigation
[Docs] Clarify model platform support and Ascend setup - #201
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Required human contributor answers
1. What outcome are you trying to achieve?
Make supported platforms easy to find in the README and documentation, including the Ascend NPU setup.
2. What is the highest-leverage variable for that outcome?
The model-to-platform mapping in the README's Model Support table.
3. How will this work move that variable rather than create busywork?
Add a Platforms column to the existing model table and link the existing device guides from Getting Started, the documentation index, and the first-run and serving guides.
4. Who is the customer or user, and what do they actually need?
Readers selecting a model and device need to see the supported platform and the corresponding setup. Ascend users need the supported Ouro-1.4B configuration and a checkout of
main.PR necessity and bugfix evidence
A documentation PR was requested. The release entry point accepts CPU and CUDA. The Ascend integration landed after
v0.2.0. I verified the distinction by comparing the tag and the current main branch.Purpose
Test Plan
vllm-rlt Version / Commit:
364ee4conefb5cd0.pre-commit run --all-filesandgit diff --check.v0.2.0and main serving entry points.Test Result
e69ff58.--device npuis available onmainand was added afterv0.2.0.