Home
last modified time | relevance | path

Searched refs:chain (Results 1 – 18 of 18) sorted by relevance

/rk3399_rockchip-uboot/doc/SPL/
H A DREADME.spl-secure-boot15 SPL image, so to continue chain of trust SPL image verifies U-boot image using
/rk3399_rockchip-uboot/tools/buildman/
H A DREADME96 Buildman automatically selects the correct tool chain for each board. You
239 Tool chain test: OK, arch='x86', priority 1
241 Tool chain test: OK, arch='arm', priority 1
247 Tool chain test: OK, arch='i386', priority 4
253 Tool chain test: OK, arch='aarch64', priority 4
259 Tool chain test: OK, arch='microblaze', priority 4
265 Tool chain test: OK, arch='mips64', priority 4
271 Tool chain test: OK, arch='sparc64', priority 4
277 Tool chain test: OK, arch='arm', priority 3
284 Tool chain test: OK, arch='sparc', priority 4
[all …]
/rk3399_rockchip-uboot/drivers/usb/host/
H A Dxhci-ring.c92 u32 chain; in inc_enq() local
95 chain = le32_to_cpu(ring->enqueue->generic.field[3]) & TRB_CHAIN; in inc_enq()
112 if (!chain && !more_trbs_coming) in inc_enq()
122 next->link.control |= cpu_to_le32(chain); in inc_enq()
/rk3399_rockchip-uboot/doc/
H A DREADME.esbc_validate36 verify the u-boot code, the subsequent chain of trust should also
H A DREADME.armada-secureboot19 a specially prepared boot image. This can be used to establish a chain of trust
41 The chain of trust is thus as follows:
H A DREADME.chromium242 what settings are actually used. When chain-loading into U-Boot we must be
H A DREADME.ti-secure179 verifying proper operation of the secure boot chain in case of successful
H A DREADME.x86845 Currently this is tested on QEMU x86 target with U-Boot chain-loading SeaBIOS
858 SeaBIOS then chain-loading a GRUB on a USB drive, then Linux kernel finally.
/rk3399_rockchip-uboot/drivers/usb/dwc3/
H A Dep0.c51 u32 len, u32 type, unsigned chain) in dwc3_ep0_start_trans() argument
67 if (chain) in dwc3_ep0_start_trans()
78 if (chain) in dwc3_ep0_start_trans()
87 if (chain) in dwc3_ep0_start_trans()
H A Dgadget.c703 unsigned length, unsigned last, unsigned chain, unsigned node) in dwc3_prepare_one_trb() argument
710 chain ? " chain" : ""); in dwc3_prepare_one_trb()
772 if (!req->request.no_interrupt && !chain) in dwc3_prepare_one_trb()
778 if (chain) in dwc3_prepare_one_trb()
/rk3399_rockchip-uboot/tools/patman/
H A Dseries.py134 all_ccs = itertools.chain(cover_cc, *self._generated_cc.values())
/rk3399_rockchip-uboot/lib/
H A DKconfig227 This enables support for LZMA (Lempel-Ziv-Markov chain algorithm),
236 This enables support for LZMA (Lempel-Ziv-Markov chain algorithm),
/rk3399_rockchip-uboot/drivers/usb/cdns3/
H A Dgadget.c544 u8 chain; in cdns3_wa2_remove_old_request() local
547 chain = !!(priv_req->flags & REQUEST_INTERNAL_CH); in cdns3_wa2_remove_old_request()
557 if (!chain) in cdns3_wa2_remove_old_request()
/rk3399_rockchip-uboot/doc/driver-model/
H A Dlivetree.txt139 a node to be linked together in a chain.
/rk3399_rockchip-uboot/board/sandbox/
H A DREADME.sandbox163 tests which emulate the action of chain-loading U-Boot, typically used in
/rk3399_rockchip-uboot/tools/binman/
H A DREADME73 - Each binary can have its own build system and tool chain without creating
/rk3399_rockchip-uboot/cmd/
H A DKconfig568 Support decompressing an LZMA (Lempel-Ziv-Markov chain algorithm)
/rk3399_rockchip-uboot/
H A DREADME3669 (potentially obsolete) versions. In case of tool chain problems we