| /u-boot/doc/SPL/ |
| A D | README.spl-secure-boot | 15 SPL image, so to continue chain of trust SPL image verifies U-boot image using
|
| /u-boot/doc/sphinx/ |
| A D | cdomain.py | 43 from itertools import chain 114 matches = sorted(chain(*match_iterators), key=lambda m: m.start())
|
| A D | automarkup.py | 16 from itertools import chain 104 sorted_matches = sorted(chain(*match_iterators), key=lambda m: m.start())
|
| /u-boot/tools/buildman/ |
| A D | README | 256 Tool chain test: OK, arch='x86', priority 1 258 Tool chain test: OK, arch='arm', priority 1 264 Tool chain test: OK, arch='i386', priority 4 294 Tool chain test: OK, arch='arm', priority 3 307 Tool chain test: OK, arch='mips', priority 4 322 Tool chain test: OK, arch='m68k', priority 4 334 Tool chain test: OK, arch='bfin', priority 6 347 Tool chain test: OK, arch='mips', priority 4 382 Tool chain test: OK, arch='arm', priority 4 388 Tool chain test: OK, arch='arm', priority 4 [all …]
|
| /u-boot/lib/optee/ |
| A D | Kconfig | 39 Select this command to enable chain-loading of a Linux kernel
|
| /u-boot/board/ste/stemmy/ |
| A D | README | 13 At the moment, U-Boot is intended to be chain-loaded from
|
| /u-boot/drivers/usb/host/ |
| A D | xhci-ring.c | 94 u32 chain; in inc_enq() local 97 chain = le32_to_cpu(ring->enqueue->generic.field[3]) & TRB_CHAIN; in inc_enq() 114 if (!chain && !more_trbs_coming) in inc_enq() 124 next->link.control |= cpu_to_le32(chain); in inc_enq()
|
| /u-boot/doc/ |
| A D | README.esbc_validate | 35 verify the u-boot code, the subsequent chain of trust should also
|
| A D | README.vxworks | 19 With CONFIG_EFI_LOADER option, it's possible to chain load a VxWorks x86 kernel 72 When using 'bootefi' to chain load an x86 kernel, the UEFI boot loader
|
| A D | README.armada-secureboot | 19 a specially prepared boot image. This can be used to establish a chain of trust 41 The chain of trust is thus as follows:
|
| A D | README.chromium-chainload | 229 what settings are actually used. When chain-loading into U-Boot we must be
|
| A D | README.ti-secure | 195 verifying proper operation of the secure boot chain in case of successful
|
| /u-boot/drivers/usb/dwc3/ |
| A D | ep0.c | 54 u32 len, u32 type, unsigned chain) in dwc3_ep0_start_trans() argument 70 if (chain) in dwc3_ep0_start_trans() 81 if (chain) in dwc3_ep0_start_trans() 90 if (chain) in dwc3_ep0_start_trans()
|
| A D | gadget.c | 708 unsigned length, unsigned last, unsigned chain, unsigned node) in dwc3_prepare_one_trb() argument 714 length, last ? " last" : "", chain ? " chain" : ""); in dwc3_prepare_one_trb() 760 if (!req->request.no_interrupt && !chain) in dwc3_prepare_one_trb() 770 if (chain) in dwc3_prepare_one_trb()
|
| /u-boot/tools/patman/ |
| A D | series.py | 139 all_ccs = itertools.chain(cover_cc, *self._generated_cc.values())
|
| /u-boot/doc/android/ |
| A D | avb2.rst | 12 Verified Boot establishes a chain of trust from the bootloader to system images:
|
| /u-boot/doc/uefi/ |
| A D | iscsi.rst | 54 iPXE executes its internal script. This script may optionally chain load a
|
| A D | uefi.rst | 110 To make the boot sequence safe, you need to establish a chain of trust; 111 In UEFI secure boot the chain trust is defined by the following UEFI variables
|
| /u-boot/doc/board/st/ |
| A D | stm32mp1.rst | 73 The **Trusted** boot chain 95 The **Basic** boot chain
|
| /u-boot/drivers/usb/cdns3/ |
| A D | gadget.c | 549 u8 chain; in cdns3_wa2_remove_old_request() local 552 chain = !!(priv_req->flags & REQUEST_INTERNAL_CH); in cdns3_wa2_remove_old_request() 562 if (!chain) in cdns3_wa2_remove_old_request()
|
| /u-boot/doc/driver-model/ |
| A D | livetree.rst | 150 a node to be linked together in a chain.
|
| /u-boot/doc/arch/ |
| A D | x86.rst | 411 Currently this is tested on QEMU x86 target with U-Boot chain-loading SeaBIOS 426 SeaBIOS then chain-loading a GRUB on a USB drive, then Linux kernel finally. 717 U-Boot can be chain-loaded from another bootloader, such as coreboot or
|
| A D | sandbox.rst | 192 tests which emulate the action of chain-loading U-Boot, typically used in
|
| /u-boot/lib/ |
| A D | Kconfig | 345 device. Introduces such features as boot chain of trust, rollback 453 This enables support for LZMA (Lempel-Ziv-Markov chain algorithm),
|
| /u-boot/doc/develop/ |
| A D | coccinelle.rst | 97 - ``chain`` tries the previous modes in the order above until one succeeds.
|