Home
last modified time | relevance | path

Searched refs:process (Results 1 – 25 of 67) sorted by relevance

123

/rk3399_rockchip-uboot/scripts/kconfig/
H A Dstreamline_config.pl275 my $process = "";
283 $process .= $start . $vars{$var};
285 $process .= $start . $variable;
289 $process .= $line;
291 return $process;
/rk3399_rockchip-uboot/doc/uImage.FIT/
H A Dverified-boot.txt7 machine during the boot process to ensure that it is authorised and correct
11 into the boot process. An example might be loading U-Boot from read-only
27 made available without risk to the verification process. The private and
31 The signing and verification process looks something like this:
83 5. This chaining process can go on indefinitely. It is recommended to use a
H A Dhowto.txt29 process is a binary file (by convention with the ".itb" extension) that
41 Here's a graphical overview of the image creation and booting process:
66 the build process. It gets passed a list of device tree files (taken from the
H A Dx86-fit-boot.txt51 As a result, the x86 kernel boot process is needlessly complex. The file
58 This document describes an alternative boot process which uses simple raw
246 1. It demystifies the process of booting an x86 kernel
/rk3399_rockchip-uboot/doc/
H A DREADME.ti-secure25 When CONFIG_TI_SECURE_DEVICE is set, the U-Boot SPL build process
27 viable boot image. The build process will look for the environment
38 This is called as part of the SPL/u-boot build process. As the secure
119 Note: ULO is not yet used by the u-boot build process
162 device's ROM boot process. In order to continue the secure boot
163 process, the authenticated SPL must authenticate the main u-boot
167 process use the FIT image format for the u-boot.img (CONFIG_SPL_FRAMEWORK
171 process. In order to secure these components so that they can be
186 SECDEV package. Within the SECDEV package exists a script to process
191 This is called as part of the u-boot build process. As the secure
H A DREADME.atmel_pmecc40 generate this PMECC header and integrated this into the build process of SPL.
45 tool will be called in build process to parametrize mkimage for atmelimage
H A DREADME.socfpga25 Updated/working projects should build using either process below.
107 Now that the handoff files are generated, U-Boot can be used to process
137 Here is an example for the DE-0 Nano SoC after the above rebuild process:
H A DREADME.armada-secureboot24 pertaining to the boot process. Furthermore, a eFuse structure (a
27 Roughly, the secure boot process works as follows:
81 and data pertaining to the boot process (used for both
97 boot process.
140 trusted boot process to enable and configure secure debugging, but they were
160 9) Continue the boot process as in the case of the regular boot.
283 After the build process has finished, and the SEC_FUSE_DUMP option was set in
294 rough overview of the process is:
H A DREADME.ARC22 or process, and are supported by a complete suite of development tools.
H A DREADME.marvell47 The ARM Trusted Firmware (ATF) build process uses this image to generate the
H A DREADME.mpc85xx-spin-table7 process is described below:
H A DREADME.mxs120 HINT: To speed-up the build process, you can add -j<N>, where N is number of
127 NOTE: The process that produces u-boot.sb uses the mkimage to generate the
217 from the U-Boot prompt. To simplify the process, the U-Boot default
239 To simplify the process of firmware update, the U-Boot default
H A DREADME.fdt-overlays24 Building an overlay follows the same process as building a traditional dtb.
H A DREADME.falcon10 Falcon Mode is introduced to speed up the booting process, allowing
108 kernel_addr : kernel is loaded as part of the boot process, but it is not started.
/rk3399_rockchip-uboot/doc/SPL/
H A DREADME.spl-secure-boot14 the main u-boot image. For secure boot process on these platforms ROM verifies
/rk3399_rockchip-uboot/drivers/mailbox/
H A DKconfig10 the basis of a variety of inter-process/inter-CPU communication
/rk3399_rockchip-uboot/test/py/
H A DREADME.md34 - Executing a sandbox port of U-Boot on the local machine as a sub-process,
74 then print a summary of the test process. A complete log of the test session
86 sandbox process in order to debug it. See `man gdbserver` and the example
110 Some tests deliberately cause the sandbox process to exit, e.g. to test the
128 environment variables required by the build process are already set, such as
186 should be connected to the board's console. This process should continue to run
198 process to always communicate with the current simulator instance.
207 This script should perform the entire flashing process synchronously; the
214 - Some other process has already written the desired U-Boot binary into the
/rk3399_rockchip-uboot/tools/scripts/
H A Ddefine2mk.sed9 # Only process values prefixed with #define CONFIG_
/rk3399_rockchip-uboot/board/freescale/mpc8536ds/
H A DREADME15 The bootup process can be divided into two stages: the first stage will
55 and config word at the fixed address. The config word direct the process how
/rk3399_rockchip-uboot/board/armltd/integrator/
H A DREADME40 boot process c) above then CONFIG_INIT_CRITICAL may need to be defined to ensure
44 boot process c) above. They have been preserved for backward compatibility with
/rk3399_rockchip-uboot/drivers/video/rockchip/
H A DKconfig3 # compile process. You can surely check all the options. In this case, all the
/rk3399_rockchip-uboot/drivers/block/
H A DKconfig31 data in the background and the device run some other process in the
/rk3399_rockchip-uboot/arch/xtensa/cpu/
H A Du-boot.lds27 * we can simplify the boot process and unpack U-Boot to RAM immediately.
/rk3399_rockchip-uboot/doc/device-tree-bindings/firmware/
H A Dnvidia,tegra186-bpmp.txt4 booting process handling and offloading the power management, clock
/rk3399_rockchip-uboot/arch/arm/mach-bcm283x/
H A DKconfig57 b) You should run the following to tell the VC FW to process DT when

123