Searched refs:go (Results 1 – 25 of 71) sorted by relevance
123
/u-boot-v2022.01-rc1/arch/arm/mach-mediatek/mt7629/ |
A D | lowlevel_init.S | 51 bne go @ Go if UP 54 beq go @ Go if core0 on primary core tile 57 go: label
|
/u-boot-v2022.01-rc1/cmd/ |
A D | boot.c | 50 go, CONFIG_SYS_MAXARGS, 1, do_go,
|
A D | bootm.c | 57 U_BOOT_CMD_MKENT(go, 0, 1, (void *)BOOTM_STATE_OS_GO, "", ""),
|
/u-boot-v2022.01-rc1/board/timll/devkit8000/ |
A D | README | 7 For more information go to:
|
/u-boot-v2022.01-rc1/doc/develop/devicetree/ |
A D | intro.rst | 16 from Linux who are used to quite strict rules about what can go into the 39 place it can go. It is a highly suitable data structure for just about anything
|
/u-boot-v2022.01-rc1/board/google/chromebook_coral/ |
A D | Kconfig | 32 to enable monitoring of the boot and debugging when things go wrong.
|
/u-boot-v2022.01-rc1/board/synopsys/iot_devkit/ |
A D | README | 104 Run U-Boot's configuration utility with "make menuconfig", go to 123 go 0x20000000 131 go 0x20000000 138 setenv bootcmd fatload mmc 0 0x20000000 yourapp.bin\; go 0x20000000
|
/u-boot-v2022.01-rc1/arch/arm/dts/ |
A D | cn9130-db-dev-info.dtsi | 6 /* This should go only into devel boards */
|
A D | logicpd-torpedo-37xx-devkit.dts | 30 * probably device tree overlays is the way to go with the various SOM and
|
/u-boot-v2022.01-rc1/doc/device-tree-bindings/net/phy/ |
A D | atheros.txt | 12 Don't go into hibernation mode.
|
/u-boot-v2022.01-rc1/doc/chromium/ |
A D | run_vboot.rst | 43 -L6 -c "host bind 0 $IMG; vboot go auto" \ 47 -c "host bind 0 $IMG; vboot go auto" -w -s $UB/state.dtb -r -n -m $UB/mem 127 useful command is 'vboot go auto', which continues where the last stage left 200 zboot go
|
/u-boot-v2022.01-rc1/doc/device-tree-bindings/usb/ |
A D | tegra-usb.txt | 21 otg means it can operate as either ("on the go")
|
/u-boot-v2022.01-rc1/doc/imx/common/ |
A D | imx5.txt | 12 The PLL's in the i.MX51 processor can go out of lock due to a metastable
|
/u-boot-v2022.01-rc1/doc/ |
A D | README.link-local | 36 is getting called. It is possible for a conflict to go undetected
|
A D | README.fsl-ddr | 296 type command "go" to continue calculation and enable DDR controller 304 STEP_PROGRAM_REGS. Upon issuing command "go", the debugger will program the 352 go 405 FSL DDR>go
|
A D | README.nokia_rx51 | 85 automatically set to 1. So output from Maemo kernel would go to serial port.
|
A D | README.standalone | 67 => go 0x40004
|
/u-boot-v2022.01-rc1/arch/arm/lib/ |
A D | memset.S | 48 ldmfdeq sp!, {r8, pc} @ Now <64 bytes to go.
|
/u-boot-v2022.01-rc1/arch/x86/include/asm/acpi/ |
A D | debug.asl | 39 /* THRE - Wait for serial port transmitter holding register to go empty */
|
/u-boot-v2022.01-rc1/board/technexion/pico-imx6/ |
A D | README | 20 go to step 2 below in order to update U-Boot.
|
/u-boot-v2022.01-rc1/doc/develop/driver-model/ |
A D | pci-info.rst | 137 The pci-emul node should go outside the pci bus node, since otherwise it will 146 When accesses go to the pci@1f,0 device they are forwarded to its emulator.
|
/u-boot-v2022.01-rc1/arch/arm/cpu/armv8/fsl-layerscape/doc/ |
A D | README.falcon | 20 It is equivalent to go through "bootm" step-by-step until device tree fixup is 58 stops before "bootm go". There we have the fixed-up device tree in memory.
|
/u-boot-v2022.01-rc1/board/work-microwave/work_92105/ |
A D | README | 33 executed with 'go'.
|
/u-boot-v2022.01-rc1/doc/uImage.FIT/ |
A D | verified-boot.txt | 83 5. This chaining process can go on indefinitely. It is recommended to use a
|
/u-boot-v2022.01-rc1/board/technexion/pico-imx6ul/ |
A D | README | 22 the user can go to step 2 below in order to update U-Boot.
|
Completed in 205 milliseconds
123