[BOOTSCRIPT] Remove old custom boot.env file of EVK machines
This because we are goint to use a new bootscript management where a set
of placeholders is used to parametrize the various boot*.scr and
boot*.env files. In this way (only for the actual stage of the
development) is no longer need to have custom script per machine and a
set of flags of the variable BOOTSCRIPT_PARAM (see documentation and
implementation in meta-seco-bsp) will be added to machine related file
(seco-imx8-common.inc, seco-imx93-common.inc, ...).
The customization can be performet at both SOC and board/SOM levels.
Signed-off-by:
Davide Cardillo <davide.cardillo@seco.com>
- recipes-bsp/bootscript/bootscript.bbappend 0 additions, 1 deletionrecipes-bsp/bootscript/bootscript.bbappend
- recipes-bsp/bootscript/files/nxp-imx8mpevk/boot.env 0 additions, 6 deletionsrecipes-bsp/bootscript/files/nxp-imx8mpevk/boot.env
- recipes-bsp/bootscript/files/nxp-imx93evk/boot.env 0 additions, 5 deletionsrecipes-bsp/bootscript/files/nxp-imx93evk/boot.env
- recipes-bsp/bootscript/files/nxp-imx95evk/boot.env 0 additions, 5 deletionsrecipes-bsp/bootscript/files/nxp-imx95evk/boot.env
-
mentioned in commit clea-os/seco-manifest@c48a1a24
-
mentioned in commit clea-os/seco-manifest@5b952ced
-
mentioned in merge request clea-os/seco-manifest!772 (merged)
-
mentioned in commit clea-os/seco-manifest@70064f7d
-
mentioned in commit clea-os/seco-manifest@70064f7d