Home
last modified time | relevance | path

Searched refs:release (Results 1 – 25 of 49) sorted by relevance

12

/rk3399_ARM-atf/docs/plat/st/
H A Dstm32mp1.rst187 tools/cert_create/cert_create -n --rot-key build/stm32mp1/release/rot_key.pem \
191 --trusted-key-cert build/stm32mp1/release/trusted_key.crt \
195 --tos-fw-cert build/stm32mp1/release/tos_fw_content.crt \
196 --tos-fw-key-cert build/stm32mp1/release/tos_fw_key.crt \
198 --nt-fw-cert build/stm32mp1/release/nt_fw_content.crt \
199 --nt-fw-key-cert build/stm32mp1/release/nt_fw_key.crt \
201 --fw-config build/stm32mp1/release/fdts/fw-config.dtb \
202 --stm32mp-cfg-cert build/stm32mp1/release/stm32mp_cfg_cert.crt
209 --fw-config build/stm32mp1/release/fdts/fw-config.dtb \
210 --trusted-key-cert build/stm32mp1/release/trusted_key.crt \
[all …]
/rk3399_ARM-atf/docs/about/
H A Drelease-information.rst7 The project currently aims to do a release once every 6 months which will be
9 non-essential changes) up to 4 weeks prior to the target release date. The release
11 required for the release will be merged. The maintainers are free to use their
12 judgement on what changes are essential for the release. A release branch may be
16 The release testing will be performed on release candidates and depending on
17 issues found, additional release candidates may be created to fix the issues.
43 These are the estimated dates for the upcoming release. These may change
H A Dlts.rst30 | 2025-03-27 | Chris Palmer | Playbook for making a new release. |
87 This section approaches three questions: for how long should an LTS release be
91 1. For how long should an LTS release be supported?
102 Given that many products that have a release cycle, have a yearly release
107 TF-A releases are cut twice a year: May and November. Basing LTS release
108 on the November TF-A release has a few benefits. First, it aligns with Linux
111 releases are timed with Android release, this gives enough time to harden
112 the TF-A LTS release during development so that it's ready for launch in
113 Q3 following year. On the other hand, if the May release of TF-A is chosen as
116 before Android release.
[all …]
H A Dindex.rst9 release-information
/rk3399_ARM-atf/docs/process/
H A Dplatform-ports-policy.rst27 the release after which each one will be removed. When an interface is
28 deprecated, the page must be updated to indicate the release after which the
29 interface will be removed. This must be at least 1 full release cycle in future.
43 period before deleting it (typically 2 release cycles). In this case, we keep
H A Dfaq.rst39 * If there is a code freeze in place in preparation for the release. Please
53 The worst case is if the TF maintainers are trying to make a release while also
54 receiving patches that will not be merged into the release. In this case, the
56 the release branch. The ``integration`` branch will be rebased onto ``master``
57 after the release, and then ``master`` will be fast-forwarded to ``integration``
/rk3399_ARM-atf/docs/plat/
H A Dqemu-sbsa.rst41 Images will be placed at build/qemu_sbsa/release (bl1.bin and fip.bin).
46 cp build/qemu_sbsa/release/bl1.bin ../
47 cp build/qemu_sbsa/release/fip.bin ../
H A Dsynquacer.rst70 --tb-fw ./build/synquacer/release/bl31.bin \
71 --soc-fw ./build/synquacer/release/bl31.bin \
72 --scp-fw ./build/synquacer/release/bl31.bin \
H A Dqemu.rst133 dd if=build/qemu/release/bl1.bin of=flash.bin bs=4096 conv=notrunc
134 dd if=build/qemu/release/fip.bin of=flash.bin seek=64 bs=4096 conv=notrunc
/rk3399_ARM-atf/docs/plat/arm/juno/
H A Dindex.rst17 `Linaro release software stack`_ version 20.01. You can alternatively
28 a single FIP binary. It assumes that a Linaro release software stack has been
33 onwards. Before that release, pre-built binaries are only available for
67 package included in the Linaro release:
75 ./tools/fiptool/fiptool unpack <path-to-linaro-release>/[SOFTWARE]/fip.bin
158 ./build/juno/release/bl1.bin
159 ./build/juno/release/fip.bin
162 ./build/fvp/release/bl1.bin
163 ./build/fvp/release/fip.bin
246 .. _Linaro release software stack: http://releases.linaro.org/members/arm/platforms/
/rk3399_ARM-atf/plat/mediatek/include/lpm/
H A Dmt_lp_rq.h26 int (*release)(struct mt_lp_resource_user *this); member
/rk3399_ARM-atf/plat/mediatek/include/lpm_v2/
H A Dmt_lp_rq.h29 int (*release)(struct mt_lp_resource_user *this); member
/rk3399_ARM-atf/docs/
H A Dconf.py18 release = "2.14.0" variable
H A Dindex.rst41 This release provides a suitable starting point for productization of secure
65 The **Processes & Policies** chapter explains the project's release schedule
/rk3399_ARM-atf/plat/mediatek/build_helpers/
H A Dconditional_eval_options.mk10 ifeq ($(BUILD_TYPE),release)
/rk3399_ARM-atf/
H A D.versionrc.cjs63 … a summary of the new features, changes, fixes and known\nissues in each release of Trusted Firmwa…
114 const _rel = 'release = "' + version + '"'
117 contents = contents.replace(/^(release\s=\s")((\d).?)*$/m, _rel)
/rk3399_ARM-atf/docs/plat/qti/
H A Drb3gen2.rst38 $ ./tools/qti/generate_fip_elf.sh build/rb3gen2/release/fip.bin \
73 NOTICE: BL2: v2.13.0(release):v2.13.0-825-gc17b22110
76 NOTICE: BL31: v2.13.0(release):v2.13.0-825-gc17b22110
H A Dmsm8916.rst81 The BL31 ELF image is generated in ``build/$PLAT/release/bl31/bl31.elf``.
90 The BL32 ELF image is generated in ``build/$PLAT/release/bl32/bl32.elf``.
132 $ ./qtestsign.py tz build/msm8916/release/bl31/bl31.elf
134 Then install the resulting ``build/msm8916/release/bl31/bl31-test-signed.mbn``
/rk3399_ARM-atf/plat/mediatek/common/lpm/
H A Dmt_lp_rq.c106 ru->release = NULL; in mt_lp_resource_user_register()
128 ru->release = mt_lp_resource_release; in mt_lp_resource_user_register()
/rk3399_ARM-atf/plat/mediatek/common/lpm_v2/
H A Dmt_lp_rq.c135 ru->release = mt_lp_resource_release; in mt_lp_resource_user_register()
144 ru->release = NULL; in mt_lp_resource_user_register()
/rk3399_ARM-atf/plat/mediatek/drivers/ufs/
H A Dufs_ctrl.c65 ret = ufs_res_user.release(&ufs_res_user); in ufs_rsc_ctrl()
/rk3399_ARM-atf/docs/getting_started/
H A Dinitial-build.rst85 - By default this produces a release version of the build. To produce a
99 is either ``debug`` or ``release``. The actual number of images might differ
/rk3399_ARM-atf/docs/tools/
H A Dmemory-layout-tool.rst45 build-path: build/fvp/release
127 build-path: build/fvp/release
160 build-path: build/fvp/release
213 build-path: build/fvp/release
/rk3399_ARM-atf/docs/perf/
H A Dpsci-performance-methodology.rst13 the Trusted Firmware Test Framework (TFTF). The release build of this framework
/rk3399_ARM-atf/docs/components/spd/
H A Dtlk-dispatcher.rst21 (FOSS) release of the NVIDIA® Trusted Little Kernel (TLK) technology, which

12