nv: Allow access to nvdrv:t #633
Closed
Conversation
This file contains 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
|
Thanks for the patch |
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.
Applications wishing to access NVJPG need to initialize
nvdrv:a, asnvdrvdoes not have permission for this channel. However, it appears that this service only allows a limited amount of memory to be mapped using/dev/nvhost-as-gpu(around 430MiB in my testing).As a workaround, this PR restores the possibility to access
nvdrv:t, which was removed in efacee6.NB: it would be nicer to explicitely choose which type of service to initialize, like what is done in vi, but I didn't want to break backwards compatibility.