| /u-boot/board/coreboot/coreboot/ |
| A D | coreboot.c | 32 const struct smbios_header *system = smbios_header(smbios, SMBIOS_SYSTEM_INFORMATION); in show_board_info() local
34 const struct smbios_type1 *t1 = (struct smbios_type1 *)system; in show_board_info()
40 const char *model = smbios_string(system, t1->product_name); in show_board_info()
41 const char *manufacturer = smbios_string(system, t1->manufacturer); in show_board_info()
|
| /u-boot/drivers/power/acpi_pmc/ |
| A D | Kconfig | 5 provides features including checking whether the system started from
6 resume, powering off the system and enabling/disabling the reset
14 provides features including checking whether the system started from
15 resume, powering off the system and enabling/disabling the reset
23 provides features including checking whether the system started from
24 resume, powering off the system and enabling/disabling the reset
|
| /u-boot/doc/device-tree-bindings/remoteproc/ |
| A D | k3-system-controller.txt | 11 - compatible: Shall be: "ti,am654-system-controller"
20 system-controller: system-controller {
21 compatible = "ti,am654-system-controller";
|
| /u-boot/drivers/sysreset/ |
| A D | Kconfig | 8 bool "Enable support for system reset drivers"
11 Enable system reset drivers which can be used to reset the CPU or
17 bool "Enable support for system reset drivers in SPL mode"
20 Enable system reset drivers which can be used to reset the CPU or
26 bool "Enable support for system reset drivers in TPL mode"
29 Enable system reset drivers which can be used to reset the CPU or
56 Support for system poweroff using a GPIO pin. This can be used
57 for systems having a single GPIO to trigger a system poweroff.
86 must be running on your system.
99 This enables the system reset driver support for Intel SOCFPGA
[all …]
|
| /u-boot/drivers/firmware/scmi/ |
| A D | Kconfig | 9 and system management. The SCMI specification is available at
10 https://developer.arm.com/architectures/system-architectures/software-standards/scmi
13 located in another sub-system, as a companion micro controller
14 or a companion host in the CPU system.
|
| /u-boot/doc/ |
| A D | README.sata | 6 * ext2load to read a file from ext2 file system
17 1.1 How to raw write the kernel, file system, dtb to a SATA hard disk?
34 1.2 How to raw read the kernel, file system, dtb from a SATA hard disk?
48 1.3 How to load an image from an ext2 file system in U-Boot?
50 U-Boot doesn't support writing to an ext2 file system, so the
|
| A D | README.memory-test | 29 - It is terribly slow. Running "mtest" on the whole system RAM
34 will reliably crash or hang your system. "mtest" is dumb and has
43 test basically the whole system RAM, with only exempting the
46 system memory) and for U-Boot (code, data, etc. - see above;
47 these are usually at the very upper end of system memory). But
52 failures (system crashes).
60 POST (Power-On Self Test) sub-system, see "post/drivers/memory.c".
82 a system like that is to boot Linux with root file system mounted over
84 compile a Linux kernel on the system) - this will cause enough context
|
| A D | README.fsl-clk | 1 Freescale system clock options
|
| /u-boot/doc/device-tree-bindings/sysinfo/ |
| A D | smbios.txt | 21 - 1 : system
27 "system" subnode optional properties:
29 - manufacturer: Product manufacturer for system
32 - serial: Serial number for system (note that this can be overridden by
56 system {
|
| /u-boot/arch/arm/cpu/armv7/ |
| A D | sctlr.S | 18 mrc p15, 0, r0, c1, c0, 0 @ load system control register
20 mcr p15, 0, r0, c1, c0, 0 @ write system control register
|
| /u-boot/arch/arm/cpu/arm11/ |
| A D | sctlr.S | 20 mrc p15, 0, r0, c1, c0, 0 @ load system control register
23 mcr p15, 0, r0, c1, c0, 0 @ write system control register
|
| /u-boot/board/armadeus/apf27/ |
| A D | fpga.c | 196 struct system_control_regs *system = in apf27_fpga_setup() local
203 writel(ACFG_DSCR10_VAL, &system->dscr10); in apf27_fpga_setup()
204 writel(ACFG_DSCR3_VAL, &system->dscr3); in apf27_fpga_setup()
205 writel(ACFG_DSCR7_VAL, &system->dscr7); in apf27_fpga_setup()
206 writel(ACFG_DSCR2_VAL, &system->dscr2); in apf27_fpga_setup()
|
| /u-boot/doc/board/emulation/ |
| A D | qemu-ppce500.rst | 28 $ qemu-system-ppc -nographic -machine ppce500 -bios u-boot
30 You can also run U-Boot using 'qemu-system-ppc64'::
32 $ qemu-system-ppc64 -nographic -machine ppce500 -bios u-boot
39 Both qemu-system-ppc and qemu-system-ppc64 provide emulation for the following
45 Additionally qemu-system-ppc64 provides support for the following 64-bit CPUs:
54 $ qemu-system-ppc64 -nographic -machine ppce500 -cpu e6500 -bios u-boot
70 $ qemu-system-ppc -nographic -machine ppce500 -bios u-boot \
|
| A D | qemu-x86.rst | 31 $ qemu-system-i386 -nographic -bios path/to/u-boot.rom
37 $ qemu-system-i386 -nographic -bios path/to/u-boot.rom -M q35
39 Note by default QEMU instantiated boards only have 128 MiB system memory. But
41 system memory by pass '-m' parameter to QEMU if you want more memory::
43 $ qemu-system-i386 -nographic -bios path/to/u-boot.rom -m 1024
45 This creates a board with 1 GiB system memory. Currently U-Boot for QEMU only
46 supports 3 GiB maximum system memory and reserves the last 1 GiB address space
80 $ qemu-system-i386 -nographic -bios path/to/u-boot.rom -m 1024 \
106 To run 64-bit U-Boot, qemu-system-x86_64 should be used instead, e.g.::
108 $ qemu-system-x86_64 -nographic -bios path/to/u-boot.rom
|
| /u-boot/doc/device-tree-bindings/sysreset/ |
| A D | ti,sci-sysreset.txt | 4 Some TI SoCs contain a system controller (like the SYSFW, etc...) that is
6 Communication between the host processor running an OS and the system
24 compatible = "ti,am654-system-controller";
|
| /u-boot/doc/device-tree-bindings/firmware/ |
| A D | ti,sci.txt | 6 management of the System on Chip (SoC) system. These include various system
9 An example of such an SoC is K2G, which contains the system control hardware
42 - ti,system-reboot-controller: If system reboot can be triggered by SoC reboot
|
| /u-boot/doc/device-tree-bindings/reset/ |
| A D | ti,sci-reset.txt | 4 Some TI SoCs contain a system controller (like the SYSFW, etc...) that is
6 Communication between the host processor running an OS and the system
26 compatible = "ti,am654-system-controller";
46 used by system controller.
|
| /u-boot/doc/device-tree-bindings/clock/ |
| A D | fsl,mpc83xx-clk.txt | 1 MPC83xx system clock devices
4 system.
|
| /u-boot/doc/device-tree-bindings/timer/ |
| A D | fsl,mpc83xx-timer.txt | 8 - clocks: must be a reference to the system's CSB (coherent system bus) clock,
|
| /u-boot/doc/android/ |
| A D | ab.rst | 9 A/B system updates ensures modern approach for system update. This feature
11 (normally slot A and slot B). The system runs from the current slot while the
64 A/B metadata is organized according to AOSP reference [2]_. On the first system
|
| /u-boot/doc/uefi/ |
| A D | iscsi.rst | 16 operating system kernel and the initial file system (initrd).
22 Furthermore the services providing the operating system loader or kernel are
23 not the ones that the operating system typically will use. Especially in a SAN
24 environment this makes updating the operating system a hassle. After installing
37 same target where the operating system is installed.
63 file system driver. U-Boot reads from the iSCSI drive via the block IO protocol
165 #define DOWNLOAD_PROTO_FILE /* Local file system access */
170 When the root file system is on an iSCSI drive you should disable pings and set
|
| /u-boot/doc/device-tree-bindings/leds/ |
| A D | common.txt | 10 system
19 system-status {
|
| /u-boot/doc/api/ |
| A D | serial.rst | 3 Serial system
|
| /u-boot/doc/device-tree-bindings/power/ |
| A D | ti,sci-pm-domain.txt | 4 Some TI SoCs contain a system controller (like the SYSFW, etc...) that is
6 Communication between the host processor running an OS and the system
33 compatible = "ti,am654-system-controller";
|
| /u-boot/doc/device-tree-bindings/reserved-memory/ |
| A D | reserved-memory.txt | 4 The operating system shall exclude reserved memory from normal usage
52 be used by an operating system to instantiate the necessary pool
56 - Indicates the operating system must not create a virtual mapping
57 of the region as part of its standard mapping of system memory,
61 - The operating system can use the memory in this region with the
64 system can use that region to store volatile or cached data that
|