update boot firmware to 00143 - #3165
ishnajain (ishnajain-qcom) wants to merge 4 commits into
Conversation
The upstream delivery format for this release changes the naming convention for the XBL configuration binaries. The KVM configuration is now provided as the default xbl_config.elf, while the Gunyah configuration is explicitly renamed to xbl_config_gunyah.elf. Signed-off-by: Ishna Jain <ishnjain@qti.qualcomm.com>
The upstream delivery format for this release changes the naming convention for the XBL configuration binaries. The KVM configuration is now provided as the default xbl_config.elf, while the Gunyah configuration is explicitly renamed to xbl_config_gunyah.elf. Signed-off-by: Ishna Jain <ishnjain@qti.qualcomm.com>
The upstream delivery format for this release changes the naming convention for the XBL configuration binaries. The KVM configuration is now provided as the default xbl_config.elf, while the Gunyah configuration is explicitly renamed to xbl_config_gunyah.elf. Signed-off-by: Ishna Jain <ishnjain@qti.qualcomm.com>
The upstream delivery format for this release changes the naming convention for the XBL configuration binaries. The KVM configuration is now provided as the default xbl_config.elf, while the Gunyah configuration is explicitly renamed to xbl_config_gunyah.elf. Signed-off-by: Ishna Jain <ishnjain@qti.qualcomm.com>
Test Results 30 files - 38 30 suites - 289 2h 47m 0s ⏱️ - 3h 0m 43s For more details on these failures, see this check. Results for commit d706152. ± Comparison against base commit 0397e37. This pull request removes 140 and adds 2 tests. Note that renamed tests count towards both. |
|
ishnajain (@ishnajain-qcom) you also need to swap QCOM_XBL_CONFIG selection in qcom-common.inc. |
|
ishnajain (@ishnajain-qcom) Just now noticed that the commit 7c9711d is adding an unwanted QCS615_bootbinaries_00143.zip file. You must drop it. |
Why unwanted? |
|
I think renaming xbl_config, and changing the hypervisor as a side effect, is a bad change, as it will cause unexpected behavior for users consuming this update (suddenly the default xbl_config will switch from gunyah to kvm). Also, we can only do this rename for all targets, so it needs to be an all or nothing. It would be terribly confusing to have kvm enable via xbl_config for some but gunyah for others, using the same file name. We should probably just stick with different files, and have a variable defining the default one to be used as part of the machine conf. |
There is no need check-in binary .zips into the layer, they are supposed to be fetched from a remote location.
|
Dmitry Baryshkov (lumag)
left a comment
There was a problem hiding this comment.
Why? What is wrong with the current naming scheme? If you want to be explicit, don't add "default" config. Let's have two separate entries, xbl_config_kvm.mbn and xbl_config_gunyah.mbn.

This PR updates the QCS615,QCS9100, QCS8300 and QCS6490 boot firmware to tag 00143 and adapts to a new upstream delivery format where KVM is now the default XBL configuration (xbl_config.elf), and Gunyah is explicitly renamed (xbl_config_gunyah.elf)."