feat: support hami-vnpu-core#4
Open
DSFans2014 wants to merge 2 commits into
Open
Conversation
DSFans2014
force-pushed
the
feat/support-hami-vnpu-core
branch
21 times, most recently
from
June 17, 2026 09:27
fc35a59 to
4ab2503
Compare
DSFans2014
force-pushed
the
feat/support-hami-vnpu-core
branch
8 times, most recently
from
June 26, 2026 08:55
42b1a75 to
3289d17
Compare
DSFans2014
force-pushed
the
feat/support-hami-vnpu-core
branch
from
June 30, 2026 08:47
3289d17 to
fab95ce
Compare
Signed-off-by: james <open4pd@4paradigm.com>
Signed-off-by: james <open4pd@4paradigm.com>
DSFans2014
force-pushed
the
feat/support-hami-vnpu-core
branch
from
July 1, 2026 03:21
fab95ce to
9e59a50
Compare
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
1 participant
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.
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?