Add neoverse-v3ae support - #160
Open
abrandemuehl-rai wants to merge 1 commit into
Open
Conversation
abrandemuehl-rai
marked this pull request as ready for review
July 27, 2026 13:17
Author
|
@alalazo is there a good way I should test this on my device? I was thinking testing would be to pip install -e a local copy and do |
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.
This adds support for the jetson thor CPU based on the one I have (Neoverse-V3AE). The AE extension has a different id (0xd83) than the Neoverse-V3 (0xd84) https://github.com/torvalds/linux/blob/master/arch/arm64/include/asm/cputype.h#L95
As far as I understand there should be a neoverse_v3 that I should depend on, but I don't have one to test with, so I left it to someone who actually needs that specific cpu