Add support for compatible TNSPECs #25
Merged
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
* Compatibility logic derived from the nv-l4t-bootloader-config script in stock L4T * BUP entries are compared to the exact TNSPEC first, then the compatibility spec in bup_enumerate_entries() * Adds some cleanup in TNSPEC parsing handle machine names containing hyphens, and the actual maximum number of fields Signed-off-by: Matt Madison <[email protected]>
Signed-off-by: Matt Madison <[email protected]>
Signed-off-by: Matt Madison <[email protected]>
Signed-off-by: Matt Madison <[email protected]>
Signed-off-by: Matt Madison <[email protected]>
Signed-off-by: Matt Madison <[email protected]>
ichergui
approved these changes
Jan 9, 2023
|
Note that to actually use these changes, you need BUP payloads that have been created under the same compatibility rules. I'll be submitting the needed |
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.
This implements the equivalent of the
COMPATIBLE_SPECconfiguration in the stock L4T update tools, but the computation of the compatibility spec is directly coded, rather than implemented in a separate script and stored in a configuration file.With this change, we can reduce the size of BUP payloads by including fewer variants, and support bootloader updates for new revisions of Jetson modules when those revisions have no impact on boot firmware compatibility.
Verified with: