Searched full:boot (Results 1 – 25 of 722) sorted by relevance
12345678910>>...29
| /Documentation/arch/powerpc/ |
| D | bootwrapper.rst | 2 The PowerPC boot wrapper
8 a boot wrapper to make it usable by the system firmware. There is no
9 standard PowerPC firmware interface, so the boot wrapper is designed to
12 The boot wrapper can be found in the arch/powerpc/boot/ directory. The
17 others. U-Boot is typically found on embedded PowerPC hardware, but there
21 The boot wrapper is built from the makefile in arch/powerpc/boot/Makefile and
22 it uses the wrapper script (arch/powerpc/boot/wrapper) to generate target
28 U-Boot (for versions that don't understand the device
30 the image. The boot wrapper, kernel and device tree
31 are all embedded inside the U-Boot uImage file format
[all …]
|
| D | firmware-assisted-dump.rst | 23 - Once enabled through kernel boot parameter, FADump can be
47 kernel during early boot.
50 low memory regions (boot memory) from source to destination area.
54 The term 'boot memory' means size of the low memory chunk
55 that is required for a kernel to boot successfully when
56 booted with restricted memory. By default, the boot memory
58 Alternatively, user can also specify boot memory size
59 through boot parameter 'crashkernel=' which will override
61 boot memory size is not sufficient for second kernel to
62 boot successfully. For syntax of crashkernel= parameter,
[all …]
|
| /Documentation/arch/arm/ |
| D | booting.rst | 11 In order to boot ARM Linux, you require a boot loader, which is a small
12 program that runs before the main kernel. The boot loader is expected
16 Essentially, the boot loader should provide (as a minimum) the
30 Existing boot loaders:
32 New boot loaders:
35 The boot loader is expected to find and initialise all RAM that the
39 the RAM in the machine, or any other method the boot loader designer
46 Existing boot loaders:
48 New boot loaders:
51 The boot loader should initialise and enable one serial port on the
[all …]
|
| /Documentation/devicetree/bindings/nvmem/layouts/ |
| D | u-boot,env.yaml | 4 $id: http://devicetree.org/schemas/nvmem/layouts/u-boot,env.yaml#
7 title: U-Boot environment variables layout
10 U-Boot uses environment variables to store device parameters and
14 Data is stored using U-Boot specific formats (variant specific header and NUL
33 const: u-boot,env
35 const: u-boot,env-redundant-bool
37 const: u-boot,env-redundant-count
81 label = "u-boot";
86 compatible = "u-boot,env";
102 compatible = "brcm,u-boot";
[all …]
|
| /Documentation/devicetree/bindings/mtd/ |
| D | st-fsm.txt | 11 - st,syscfg : Phandle to boot-device system configuration registers
12 - st,boot-device-reg : Address of the aforementioned boot-device register(s)
13 - st,boot-device-spi : Expected boot-device value if booted via this device
22 st,boot-device-reg = <0x958>;
23 st,boot-device-spi = <0x1a>;
|
| D | amlogic,meson-nand.yaml | 67 amlogic,boot-pages:
75 amlogic,boot-page-step:
88 amlogic,boot-pages: [nand-is-boot-medium, "amlogic,boot-page-step"]
89 amlogic,boot-page-step: [nand-is-boot-medium, "amlogic,boot-pages"]
|
| D | rockchip,nand-controller.yaml | 91 rockchip,boot-blks:
97 algorithms supported by the boot ROM.
98 Only used in combination with 'nand-is-boot-medium'.
100 rockchip,boot-ecc-strength:
105 supported by the boot ROM.
118 Only used in combination with 'nand-is-boot-medium'.
159 nand-is-boot-medium;
160 rockchip,boot-blks = <8>;
161 rockchip,boot-ecc-strength = <16>;
|
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | u-boot.yaml | 4 $id: http://devicetree.org/schemas/mtd/partitions/u-boot.yaml#
7 title: U-Boot bootloader partition
10 U-Boot is a bootloader commonly used in embedded devices. It's almost always
25 - const: brcm,u-boot
27 Broadcom stores environment variables inside a U-Boot partition. They
44 compatible = "brcm,u-boot";
46 label = "u-boot";
48 partition-u-boot-env {
|
| /Documentation/admin-guide/ |
| D | efi-stub.rst | 2 The EFI Boot Stub
9 jumps to are collectively known as the "EFI boot stub", and live in
10 arch/x86/boot/header.S and drivers/firmware/efi/libstub/x86-stub.c,
12 arch/arm/boot/compressed/efi-header.S and
21 By using the EFI boot stub it's possible to boot a Linux kernel
22 without the use of a conventional EFI boot loader, such as grub or
23 elilo. Since the EFI boot stub performs the jobs of a boot loader, in
24 a certain sense it *IS* the boot loader.
26 The EFI boot stub is enabled with the CONFIG_EFI_STUB kernel option.
32 The bzImage located in arch/x86/boot/bzImage must be copied to the EFI
[all …]
|
| D | bootconfig.rst | 6 Boot Configuration
14 The boot configuration expands the current kernel command line to support
21 The boot config syntax is a simple structured key-value. Each key consists
45 The boot config file syntax allows user to merge partially same word keys
63 at boot time. So you can append similar trees or key-values.
151 /proc/bootconfig is a user-space interface of the boot config.
158 Boot Kernel With a Boot Config
161 There are two options to boot the kernel with bootconfig: attaching the
164 Attaching a Boot Config to Initrd
167 Since the boot configuration file is loaded with initrd by default,
[all …]
|
| /Documentation/devicetree/bindings/regulator/ |
| D | pv88060.txt | 32 regulator-boot-on;
39 regulator-boot-on;
46 regulator-boot-on;
53 regulator-boot-on;
60 regulator-boot-on;
67 regulator-boot-on;
74 regulator-boot-on;
81 regulator-boot-on;
94 regulator-boot-on;
101 regulator-boot-on;
[all …]
|
| D | tps65090.txt | 54 regulator-boot-on;
62 regulator-boot-on;
68 regulator-boot-on;
74 regulator-boot-on;
80 regulator-boot-on;
86 regulator-boot-on;
92 regulator-boot-on;
98 regulator-boot-on;
104 regulator-boot-on;
110 regulator-boot-on;
[all …]
|
| D | nxp,pf8x00-regulator.yaml | 106 regulator-boot-on;
113 regulator-boot-on;
120 regulator-boot-on;
127 regulator-boot-on;
135 regulator-boot-on;
142 regulator-boot-on;
149 regulator-boot-on;
156 regulator-boot-on;
163 regulator-boot-on;
170 regulator-boot-on;
[all …]
|
| D | tps65217.txt | 32 regulator-boot-on;
39 regulator-boot-on;
46 regulator-boot-on;
53 regulator-boot-on;
60 regulator-boot-on;
67 regulator-boot-on;
74 regulator-boot-on;
|
| D | mt6380-regulator.txt | 26 regulator-boot-on;
42 regulator-boot-on;
51 regulator-boot-on;
60 regulator-boot-on;
69 regulator-boot-on;
78 regulator-boot-on;
87 regulator-boot-on;
|
| D | nxp,pca9450-regulator.yaml | 122 regulator-boot-on;
130 regulator-boot-on;
140 regulator-boot-on;
147 regulator-boot-on;
154 regulator-boot-on;
162 regulator-boot-on;
169 regulator-boot-on;
176 regulator-boot-on;
183 regulator-boot-on;
190 regulator-boot-on;
|
| D | tps65218.txt | 31 regulator-boot-on;
39 regulator-boot-on;
47 regulator-boot-on;
55 regulator-boot-on;
63 regulator-boot-on;
70 regulator-boot-on;
|
| /Documentation/driver-api/mmc/ |
| D | mmc-dev-parts.rst | 8 As of this writing, MMC boot partitions as supported and exposed as
12 MMC Boot Partitions
15 Read and write access is provided to the two MMC boot partitions. Due to
16 the sensitive nature of the boot partition contents, which often store
30 The boot partitions can also be locked read only until the next power on,
36 not support boot partition locking, the file will not exist. If the
39 The boot partitions can also be locked permanently, but this feature is
|
| /Documentation/arch/x86/ |
| D | boot.rst | 4 The Linux/x86 Boot Protocol
7 On the x86 platform, the Linux kernel uses a rather complicated boot
14 Currently, the following versions of the Linux/x86 boot protocol exist.
22 boot loader and the kernel. setup.S made relocatable,
44 the boot command line.
46 Protocol 2.07 (Kernel 2.6.24) Added paravirtualised boot protocol.
59 pref_address fields. Added extended boot loader IDs.
74 ("x86/boot: Add ACPI RSDP address to setup_header")
86 features to the boot loader. Due to very limited space available in
89 communicate things to the boot loader is the kernel_info.
[all …]
|
| D | booting-dt.rst | 10 Documentation/arch/x86/boot.rst
12 which requires at least boot protocol 2.09.
17 This device-tree is used as an extension to the "boot page". As such it
18 does not parse / consider data which is already covered by the boot
|
| /Documentation/devicetree/bindings/arm/hisilicon/controller/ |
| D | hip04-bootwrapper.yaml | 7 title: Bootwrapper boot method
12 description: Bootwrapper boot method (software protocol on SMP)
19 boot-method:
22 Address and size of boot method.
32 - boot-method
|
| /Documentation/devicetree/bindings/mfd/ |
| D | rockchip,rk808.yaml | 156 regulator-boot-on;
164 regulator-boot-on;
172 regulator-boot-on;
178 regulator-boot-on;
186 regulator-boot-on;
194 regulator-boot-on;
202 regulator-boot-on;
210 regulator-boot-on;
218 regulator-boot-on;
226 regulator-boot-on;
[all …]
|
| D | rockchip,rk806.yaml | 161 regulator-boot-on;
173 regulator-boot-on;
185 regulator-boot-on;
198 regulator-boot-on;
210 regulator-boot-on;
222 regulator-boot-on;
234 regulator-boot-on;
247 regulator-boot-on;
259 regulator-boot-on;
268 regulator-boot-on;
[all …]
|
| /Documentation/firmware-guide/acpi/ |
| D | debug.rst | 16 Boot- and run-time configuration
20 you're interested in. At boot-time, use the acpi.debug_layer and
21 acpi.debug_level kernel command line options. After boot, you can use the
32 You can set the debug_layer mask at boot-time using the acpi.debug_layer
33 command line argument, and you can change it after boot by writing values
66 You can set the debug_level mask at boot-time using the acpi.debug_level
67 command line argument, and you can change it after boot by writing values
118 AML) during boot::
126 Enable all ACPI_DB_INFO messages after boot::
|
| /Documentation/trace/ |
| D | boottime-trace.rst | 4 Boot-time tracing
12 Boot-time tracing allows users to trace boot-time process including
19 Options in the Boot Config
22 Here is the list of available options list for boot time tracing in
23 boot config file [1]_. All options are under "ftrace." or "kernel."
33 Ftrace global options have "kernel." prefix in boot config, which means
65 Enable/Disable tracing on this instance when starting boot-time tracing.
82 Enable given events on boot. You can use a wild card in EVENT.
85 Set TRACER to current tracer on boot. (e.g. function)
195 All boot-time tracing options starting with ``ftrace`` will be enabled at the
[all …]
|
12345678910>>...29