Conversation
Contributor
|
Closing as all PRs are applied to the internal codebase. |
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
2 participants
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.
On QLI 2.0, the RB3 Gen 2 device-tree model is reported as RB3gen2 and does not include the vision suffix expected by the existing platform detection logic. As a result, the CLI selected the default GStreamer discovery path, which returned no cameras even though the Qualcomm
qtiqmmfsrcpipeline was working correctly.This change preserves the existing RB3 Gen 2 detection and adds a targeted QLI 2.0 fallback based on the RB3gen2 model together with
ID=qcom-distroandVERSION_ID=2.The CLI now selects the Qualcomm camera path and successfully detects and captures from the RB3 Gen 2 camera using the explicitqtiqmmfsrcpipeline