Searched refs:release (Results 1 – 25 of 39) sorted by relevance
12
7 The project currently aims to do a release once every 6 months which will be9 non-essential changes) up to 4 weeks prior to the target release date. The release11 required for the release will be merged. The maintainers are free to use their12 judgement on what changes are essential for the release. A release branch may be16 The release testing will be performed on release candidates and depending on17 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
9 release-information
38 -sLS -o build/n1sdp/release/scp_rom.bin \39 https://downloads.trustedfirmware.org/tf-a/css_scp_2.12.0/n1sdp/release/n1sdp-bl1.bin41 --retry 5 -sLS -o build/n1sdp/release/scp_ram.bin \42 https://downloads.trustedfirmware.org/tf-a/css_scp_2.12.0/n1sdp/release/n1sdp-bl2.bin49 -sLS -o build/n1sdp/release/mcp_rom.bin \50 … https://downloads.trustedfirmware.org/tf-a/css_scp_2.12.0/n1sdp/release/n1sdp-mcp-bl1.bin52 -sLS -o build/n1sdp/release/mcp_ram.bin \53 … https://downloads.trustedfirmware.org/tf-a/css_scp_2.12.0/n1sdp/release/n1sdp-mcp-bl2.bin61 uuid=cfacc2c4-15e8-4668-82be-430a38fad705,file=build/n1sdp/release/bl1.bin \62 --scp-fw build/n1sdp/release/scp_ram.bin build/n1sdp/release/scp_fw.bin[all …]
13 the Trusted Firmware Test Framework (TFTF). The release build of this framework
56 https://downloads.trustedfirmware.org/tf-a/css_scp_2.12.0/juno/release/juno-bl2.bin346 for the 3 other CPUs in the cluster (0-2) to complete ``PSCI_ENTRY`` and release
185 tools/cert_create/cert_create -n --rot-key build/stm32mp1/release/rot_key.pem \189 --trusted-key-cert build/stm32mp1/release/trusted_key.crt \193 --tos-fw-cert build/stm32mp1/release/tos_fw_content.crt \194 --tos-fw-key-cert build/stm32mp1/release/tos_fw_key.crt \196 --nt-fw-cert build/stm32mp1/release/nt_fw_content.crt \197 --nt-fw-key-cert build/stm32mp1/release/nt_fw_key.crt \199 --fw-config build/stm32mp1/release/fdts/fw-config.dtb \200 --stm32mp-cfg-cert build/stm32mp1/release/stm32mp_cfg_cert.crt207 --fw-config build/stm32mp1/release/fdts/fw-config.dtb \208 --trusted-key-cert build/stm32mp1/release/trusted_key.crt \[all …]
26 int (*release)(struct mt_lp_resource_user *this); member
27 the release after which each one will be removed. When an interface is28 deprecated, the page must be updated to indicate the release after which the29 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
39 * If there is a code freeze in place in preparation for the release. Please53 The worst case is if the TF maintainers are trying to make a release while also54 receiving patches that will not be merged into the release. In this case, the56 the release branch. The ``integration`` branch will be rebased onto ``master``57 after the release, and then ``master`` will be fast-forwarded to ``integration``
18 release = "2.10.4" variable
40 This release provides a suitable starting point for productization of secure64 The **Processes & Policies** chapter explains the project's release schedule
41 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 ../
70 --tb-fw ./build/synquacer/release/bl31.bin \71 --soc-fw ./build/synquacer/release/bl31.bin \72 --scp-fw ./build/synquacer/release/bl31.bin \
81 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.elf134 Then install the resulting ``build/msm8916/release/bl31/bl31-test-signed.mbn``
133 dd if=build/qemu/release/bl1.bin of=flash.bin bs=4096 conv=notrunc134 dd if=build/qemu/release/fip.bin of=flash.bin seek=64 bs=4096 conv=notrunc
182 has to call ``PSCI_CPU_ON`` to release the secondary CPUs from the wait loop.438 NOTICE: BL1: v1.4(release):v1.4-329-g61e94684-dirty441 NOTICE: BL2: v1.4(release):v1.4-329-g61e94684-dirty444 NOTICE: BL31: v1.4(release):v1.4-329-g61e94684-dirty
10 maintained in NXP official release.
17 `Linaro release software stack`_ version 20.01. You can alternatively28 a single FIP binary. It assumes that a Linaro release software stack has been33 onwards. Before that release, pre-built binaries are only available for67 package included in the Linaro release:75 ./tools/fiptool/fiptool unpack <path-to-linaro-release>/[SOFTWARE]/fip.bin158 ./build/juno/release/bl1.bin159 ./build/juno/release/fip.bin162 ./build/fvp/release/bl1.bin163 ./build/fvp/release/fip.bin246 .. _Linaro release software stack: http://releases.linaro.org/members/arm/platforms/
10 ifeq ($(BUILD_TYPE),release)
45 build-path: build/fvp/release127 build-path: build/fvp/release160 build-path: build/fvp/release213 build-path: build/fvp/release
106 ru->release = NULL; in mt_lp_resource_user_register()128 ru->release = mt_lp_resource_release; in mt_lp_resource_user_register()
85 - By default this produces a release version of the build. To produce a99 is either ``debug`` or ``release``. The actual number of images might differ
21 (FOSS) release of the NVIDIA® Trusted Little Kernel (TLK) technology, which
74 default, there are platform-specific ways to release any number of cores out of81 a programmable CPU reset address and which release a single CPU out of reset.
83 TBB := $(WTP)/wtptp/src/TBB_Linux/release/TBB_linux
