Update boot assets to latest asset tag for qcs9100, qcs615, qcs8300 and qcs6490#1676
Open
ishnajain-qcom wants to merge 4 commits intoqualcomm-linux:masterfrom
Open
Update boot assets to latest asset tag for qcs9100, qcs615, qcs8300 and qcs6490#1676ishnajain-qcom wants to merge 4 commits intoqualcomm-linux:masterfrom
ishnajain-qcom wants to merge 4 commits intoqualcomm-linux:masterfrom
Conversation
…ation for qcs8300 Known fixes: -Adjusts eMMC and UFS coexistence handling to avoid platform interference and improve storage stability. -Increases device‑tree size when disabling nodes, improving storage driver configuration flexibility. -Updates CAN transceiver mapping to ensure correct vehicle‑network behaviour. -Applies safety‑related improvements, including mutex logic updates and startup‑file verification. Signed-off-by: Ishna Jain <ishnjain@qti.qualcomm.com>
…n for qcs6490 Known changes: -Restores splash‑screen functionality, improving the visual behavior during boot. -Enables the Renesas PCIe‑USB controller, adding support for additional hardware connectivity on this platform. Signed-off-by: Ishna Jain <ishnjain@qti.qualcomm.com>
…ation for qcs9100 Known fixes: -Updates CAN transceiver mapping, ensuring proper signal routing. -Adds device‑tree sizing improvements for storage handling, improving node‑disable behavior. -Includes SAIL‑related improvements: mutex assembly updates and verification of startup object files. -Enables ECC, enhancing reliability for memory operations. Signed-off-by: Ishna Jain <ishnjain@qti.qualcomm.com>
…tion for qcs615 Known fixes: -Improves the QSPI AC policy logic to ensure the timing and access constraints are handled correctly. -Enhances reliability by ensuring QSPI operations stay within defined limits, preventing timing‑related faults or unintended behavior Signed-off-by: Ishna Jain <ishnjain@qti.qualcomm.com>
ishnajain-qcom
requested review from
anujm1,
koenkooi,
lumag,
ndechesne,
ricardosalveti,
sbanerjee-quic and
vkraleti
as code owners
Contributor
|
This change is sending versions backwards, which is not acceptable. After 00116.0, next version should be something bigger than 116, not 00004. |
Test run workflowTest jobs for commit c06953d
All jobs summary
|
Test Results 46 files + 22 198 suites +174 3h 3m 19s ⏱️ + 1h 45m 4s For more details on these failures, see this check. Results for commit c06953d. ± Comparison against base commit b062add. This pull request removes 2 and adds 36 tests. Note that renamed tests count towards both. |
Contributor
How? It is released under r2.0_00002.0 but the zip has 00005? Makes no sense to me. |
Contributor
|
@ishnajain-qcom there are no "asset tags", it's firmware versions (or tarball versions). |
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
4 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.
This PR is for updating boot firmware recipes to latest asset tag for respective soc.
Instead of relying on SPF release tag, the build ID will be used to version individual boot firmware artifacts (zip) per soc.
Going forward, build id will be incremental.
As of now, SPF name in URL is hardcoded but will be replaced with a unified folder going forward.
This PR is an intermediate step toward removing the multiple Artifactory locations currently used for the 1.0, 2.0, and 0.0 SPFs, and consolidating everything under a single umbrella directory where build ID will be used for versioning boot critical zips.
We have addressed versioning and use of in package version concerns mentioned in #1633
Known fixes across targets:
QCS615-
-Improves the QSPI AC policy logic to ensure the timing and access constraints are handled correctly.
-Enhances reliability by ensuring QSPI operations stay within defined limits, preventing timing‑related faults or unintended behavior.
QCS9100:
-Updates CAN transceiver mapping, ensuring proper signal routing.
-Adds device‑tree sizing improvements for storage handling, improving node‑disable behavior.
-Includes SAIL‑related improvements: mutex assembly updates and verification of startup object files.
-Enables ECC, enhancing reliability for memory operations.
QCS6490:
-Restores splash‑screen functionality, improving the visual behavior during boot.
-Enables the Renesas PCIe‑USB controller, adding support for additional hardware connectivity on this platform.
QCS8300:
-Adjusts eMMC and UFS coexistence handling to avoid platform interference and improve storage stability.
-Increases device‑tree size when disabling nodes, improving storage driver configuration flexibility.
-Updates CAN transceiver mapping to ensure correct vehicle‑network behaviour.
-Applies safety‑related improvements, including mutex logic updates and startup‑file verification.