Searched full:boot (Results 1 – 25 of 535) sorted by relevance
12345678910>>...22
| /Documentation/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/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/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 arch/x86/boot/compressed/eboot.c,
12 arch/arm/boot/compressed/efi-header.S and
13 arch/arm/boot/compressed/efi-stub.c. EFI stub code that is shared
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.
[all …]
|
| D | initrd.rst | 8 initrd provides the capability to load a RAM disk by the boot loader.
19 discussion of the boot process can be found in [#f1]_.
27 1) the boot loader loads the kernel and the initial RAM disk
42 the usual boot sequence
51 Boot command-line options
76 initrd is mounted as root, and the normal boot procedure is followed,
88 find . | cpio --quiet -H newc -o | gzip -9 -n > /boot/imagefile.img
94 gzip -cd /boot/imagefile.img | cpio -imd --quiet
107 If the root file system is created during the boot procedure (i.e. if
178 Finally, you have to boot the kernel and load initrd. Almost all Linux
[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>;
|
| /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 | pfuze100.txt | 48 regulator-boot-on;
56 regulator-boot-on;
63 regulator-boot-on;
70 regulator-boot-on;
77 regulator-boot-on;
94 regulator-boot-on;
99 regulator-boot-on;
149 regulator-boot-on;
157 regulator-boot-on;
164 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 | 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;
|
| D | ltc3676.txt | 41 regulator-boot-on;
50 regulator-boot-on;
59 regulator-boot-on;
68 regulator-boot-on;
76 regulator-boot-on;
83 regulator-boot-on;
90 regulator-boot-on;
|
| D | mt6323-regulator.txt | 29 regulator-boot-on;
38 regulator-boot-on;
53 regulator-boot-on;
83 regulator-boot-on;
99 regulator-boot-on;
107 regulator-boot-on;
115 regulator-boot-on;
123 regulator-boot-on;
131 regulator-boot-on;
181 regulator-boot-on;
[all …]
|
| D | rohm,bd70528-regulator.txt | 23 regulator-boot-on;
30 regulator-boot-on;
37 regulator-boot-on;
44 regulator-boot-on;
50 regulator-boot-on;
|
| D | ltc3589.txt | 41 regulator-boot-on;
50 regulator-boot-on;
59 regulator-boot-on;
67 regulator-boot-on;
75 regulator-boot-on;
84 regulator-boot-on;
91 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/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.
89 | Kernel boot sector | The kernel legacy boot sector.
93 | Boot loader | <- Boot sector entry point 0000:7C00
103 0x100000 ("high memory"), and the kernel real-mode block (boot sector,
[all …]
|
| /Documentation/firmware-guide/acpi/ |
| D | debug.rst | 17 Boot- and run-time configuration
21 you're interested in. At boot-time, use the acpi.debug_layer and
22 acpi.debug_level kernel command line options. After boot, you can use the
33 You can set the debug_layer mask at boot-time using the acpi.debug_layer
34 command line argument, and you can change it after boot by writing values
81 You can set the debug_level mask at boot-time using the acpi.debug_level
82 command line argument, and you can change it after boot by writing values
133 AML) during boot::
145 Enable all ACPI_DB_INFO messages after boot::
|
| /Documentation/ia64/ |
| D | xen.rst | 39 # cp xen/xen.gz /boot/efi/efi/redhat/
41 /boot/efi/efi/redhat/vmlinuz-2.6.18.8-xen
47 # mkinitrd -f /boot/efi/efi/redhat/initrd-2.6.18.8-xen.img \
99 Boot Xen & Domain0
103 elilo of RHEL5 can boot Xen and Dom0.
106 and copy into /boot/efi/efi/redhat/::
108 # cp elilo-3.6-ia64.efi /boot/efi/efi/redhat/elilo.efi
112 # vi /boot/efi/efi/redhat/elilo.conf
169 # cp vmlinux.gz /boot/efi/efi/redhat/vmlinuz-2.6-pv_ops-xenU
171 # mkinitrd -f /boot/efi/efi/redhat/initrd-2.6-pv_ops-xenU.img \
[all …]
|
| /Documentation/devicetree/bindings/mfd/ |
| D | rk808.txt | 173 regulator-boot-on;
181 regulator-boot-on;
189 regulator-boot-on;
195 regulator-boot-on;
203 regulator-boot-on;
211 regulator-boot-on;
219 regulator-boot-on;
227 regulator-boot-on;
235 regulator-boot-on;
243 regulator-boot-on;
[all …]
|
| /Documentation/arm/samsung/ |
| D | bootloader-interface.rst | 2 Interface between kernel and boot loaders on Exynos boards
10 and boot loaders on Samsung Exynos based boards. This is not a definition
14 In the document "boot loader" means any of following: U-boot, proprietary
28 0x1c exynos4_secondary_startup Secondary CPU boot
29 0x1c + 4*cpu exynos4_secondary_startup (Exynos4412) Secondary CPU boot
44 0x00 exynos4_secondary_startup Secondary CPU boot
45 0x04 exynos4_secondary_startup (Exynos542x) Secondary CPU boot
46 4*cpu exynos4_secondary_startup (Exynos4412) Secondary CPU boot
60 0x0814 exynos4_secondary_startup (Exynos4210 r1.1) Secondary CPU boot
72 0x0908 Non-zero Secondary CPU boot up indicator
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-mic | 44 "ready" - The MIC device is ready to boot the card OS. On
45 reading this entry after an OSPM resume, a "boot" has to be
49 "online" - The MIC device has completed boot and is online
57 "boot" - Boot the card OS image specified by the combination
89 boot the card OS. This entry can be written to change the
112 OS boot can be found. The entry can be written to change
123 a) linux - Boot a Linux image.
124 b) flash - Boot an image for flash updates.
132 debugging purpose and early kernel boot messages, the user can
146 debugging purpose and early kernel boot messages, the user can
|
| D | sysfs-ibft | 5 files that expose the iSCSI Boot Firmware Table initiator data.
12 files that expose the iSCSI Boot Firmware Table target data.
13 Usually this contains the target's IP address, boot LUN,
22 files that expose the iSCSI Boot Firmware Table NIC data.
|
| D | sysfs-class-watchdog | 6 device at boot. It is equivalent to WDIOC_GETBOOTSTATUS of
84 alternate boot function was enabled with 'aspeed,alt-boot'
96 Clearing the boot code selection and timeout counter also
100 For alternate boot mode (booted from CS1 due to wdt2
105 When read, the current status of the boot code selection is
107 the boot code selection and the timeout counter, which results
|
12345678910>>...22