[dunfell][RFC 0/6] HS SDK on GP EVM support


Andrew Davis
 

Hello all,

Still some changes pending in the k3-image-gen and u-boot projects
but wanted to get some comments on this early. Plan is to remove
the GP SDK. Have the HS SDK work on GP SoCs with minimal effort
and have HS become the default single SDK type (starting only
with AM64x and working out from there so don't panic (yet)).

Thanks,
Andrew

Andrew Davis (6):
conf: machine: Make multi-certificate image the default
ti-sci-fw: Use new SOC_TYPE and SYSFW_DIR to simplify recipe
ti-sci-fw: Deploy all SYSFW firmware types
ti-sci-fw: Use SYSFW_TIBOOT3 to point to the SYSFW image
machine: am64xx-k3r5: The output of u-boot is not used
ti-sci-fw: Deploy GP version of tiboot3.bin with HS SDK

conf/machine/am64xx-evm-k3r5.conf | 7 +
conf/machine/am64xx-hs-evm-k3r5.conf | 7 +
conf/machine/am64xx-hs-evm.conf | 2 +
conf/machine/include/am62xx.inc | 3 -
conf/machine/include/am64xx.inc | 3 -
conf/machine/include/am65xx.inc | 5 +-
conf/machine/include/j7.inc | 2 -
conf/machine/include/k3.inc | 5 +-
conf/machine/j7-evm.conf | 3 +
conf/machine/j7-hs-evm.conf | 1 -
conf/machine/j7200-evm.conf | 3 -
conf/machine/j721s2-evm.conf | 3 -
recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb | 334 +++++++++----------------
recipes-bsp/u-boot/u-boot-ti.inc | 10 -
14 files changed, 149 insertions(+), 239 deletions(-)
rewrite recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb (72%)

--
2.36.1


Denys Dmytriyenko
 

On Fri, Jul 01, 2022 at 05:02:22PM -0500, Andrew Davis via lists.yoctoproject.org wrote:
Hello all,

Still some changes pending in the k3-image-gen and u-boot projects
but wanted to get some comments on this early. Plan is to remove
the GP SDK. Have the HS SDK work on GP SoCs with minimal effort
and have HS become the default single SDK type (starting only
with AM64x and working out from there so don't panic (yet)).
So, quick question - does this set have any chance to get merged this year
into dunfell before kirkstone becomes the current base?

Reason being is that I've been mulling over a much better and granular
grouping of platforms in master/kirkstone into different categories, such
as legacy (ARMv7) HS vs. K3 HS, legacy vs. multi-cert boot, GPU vs headless,
etc.

This would be the best use of those new groupings...


Thanks,
Andrew

Andrew Davis (6):
conf: machine: Make multi-certificate image the default
ti-sci-fw: Use new SOC_TYPE and SYSFW_DIR to simplify recipe
ti-sci-fw: Deploy all SYSFW firmware types
ti-sci-fw: Use SYSFW_TIBOOT3 to point to the SYSFW image
machine: am64xx-k3r5: The output of u-boot is not used
ti-sci-fw: Deploy GP version of tiboot3.bin with HS SDK

conf/machine/am64xx-evm-k3r5.conf | 7 +
conf/machine/am64xx-hs-evm-k3r5.conf | 7 +
conf/machine/am64xx-hs-evm.conf | 2 +
conf/machine/include/am62xx.inc | 3 -
conf/machine/include/am64xx.inc | 3 -
conf/machine/include/am65xx.inc | 5 +-
conf/machine/include/j7.inc | 2 -
conf/machine/include/k3.inc | 5 +-
conf/machine/j7-evm.conf | 3 +
conf/machine/j7-hs-evm.conf | 1 -
conf/machine/j7200-evm.conf | 3 -
conf/machine/j721s2-evm.conf | 3 -
recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb | 334 +++++++++----------------
recipes-bsp/u-boot/u-boot-ti.inc | 10 -
14 files changed, 149 insertions(+), 239 deletions(-)
rewrite recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb (72%)

--
2.36.1


Andrew Davis
 

On 7/2/22 5:43 PM, Denys Dmytriyenko wrote:
On Fri, Jul 01, 2022 at 05:02:22PM -0500, Andrew Davis via lists.yoctoproject.org wrote:
Hello all,

Still some changes pending in the k3-image-gen and u-boot projects
but wanted to get some comments on this early. Plan is to remove
the GP SDK. Have the HS SDK work on GP SoCs with minimal effort
and have HS become the default single SDK type (starting only
with AM64x and working out from there so don't panic (yet)).
So, quick question - does this set have any chance to get merged this year
into dunfell before kirkstone becomes the current base?
Was hoping this (for AM64x only) could be ready for merge in the next week or so..

Reason being is that I've been mulling over a much better and granular
grouping of platforms in master/kirkstone into different categories, such
as legacy (ARMv7) HS vs. K3 HS, legacy vs. multi-cert boot, GPU vs headless,
etc.
This would be the best use of those new groupings...
Does sound interesting, I'm game for re-working this series for
master/kirkstone as needed too.

Is this new grouping still in the mulling stage only, or do you
have some details on what this new grouping scheme might look like?

Most categories feel orthogonal already, (any can be GPU vs headless, etc.),
only the "Legacy vs K3" being a top level that would have some specifics
under it,

* legacy
- GP / HS
* K3
- non-combined / multi-cert boot
- combined / split SYSFW
- GP / HS <- this one I'd like to go away making it a legacy-only
category and not a purely orthogonal one like before.

Andrew


Thanks,
Andrew

Andrew Davis (6):
conf: machine: Make multi-certificate image the default
ti-sci-fw: Use new SOC_TYPE and SYSFW_DIR to simplify recipe
ti-sci-fw: Deploy all SYSFW firmware types
ti-sci-fw: Use SYSFW_TIBOOT3 to point to the SYSFW image
machine: am64xx-k3r5: The output of u-boot is not used
ti-sci-fw: Deploy GP version of tiboot3.bin with HS SDK

conf/machine/am64xx-evm-k3r5.conf | 7 +
conf/machine/am64xx-hs-evm-k3r5.conf | 7 +
conf/machine/am64xx-hs-evm.conf | 2 +
conf/machine/include/am62xx.inc | 3 -
conf/machine/include/am64xx.inc | 3 -
conf/machine/include/am65xx.inc | 5 +-
conf/machine/include/j7.inc | 2 -
conf/machine/include/k3.inc | 5 +-
conf/machine/j7-evm.conf | 3 +
conf/machine/j7-hs-evm.conf | 1 -
conf/machine/j7200-evm.conf | 3 -
conf/machine/j721s2-evm.conf | 3 -
recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb | 334 +++++++++----------------
recipes-bsp/u-boot/u-boot-ti.inc | 10 -
14 files changed, 149 insertions(+), 239 deletions(-)
rewrite recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb (72%)

--
2.36.1