Fix EVS sample driver not getting started as service #229
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
EVS sample driver not getting started as service due to missing sepolicies and onrestart automotive_display trigger. Changes done to fix the issue: Allow carservice_app with service find rights Allow carservice_app with open, read and search access for sysfs dir Allow carservice_app with search access for data folder Tracked-On: OAM-108953 Signed-off-by: pillai45 <[email protected]>
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.
EVS sample driver not getting started as service due to missing sepolicies and onrestart automotive_display trigger.
Changes done to fix the issue:
Allow carservice_app with service find rights
Allow carservice_app with open, read and search access for sysfs dir Allow carservice_app with search access for data folder
Tracked-On: OAM-108953