Searched full:early (Results 1 – 25 of 217) sorted by relevance
123456789
| /Documentation/driver-api/driver-model/ |
| D | platform.rst | 178 early during system boot.
190 Early Platform Devices and Drivers
192 The early platform interfaces provide platform data to platform device
193 drivers early on during the system boot. The code is built on top of the
194 early_param() command line parsing and can be executed very early on.
196 Example: "earlyprintk" class early serial console in 6 steps
198 1. Registering early platform device data
201 early_platform_add_devices(). In the case of early serial console this
203 at this point will later on be matched against early platform drivers.
209 User specified early platform devices will be registered at this point.
[all …]
|
| /Documentation/driver-api/early-userspace/ |
| D | early_userspace_support.rst | 2 Early userspace support
8 "Early userspace" is a set of libraries and programs that provide
25 two ways to add an early userspace image: specify an existing cpio
32 You can create a cpio archive that contains the early userspace image.
41 The kernel build process can also build an early userspace image from
68 early userspace image can be built by an unprivileged user.
88 early userspace useful. The klibc distribution is currently
111 move to early userspace:
124 For questions and help, you can sign up for the early userspace
|
| D | index.rst | 4 Early Userspace
|
| /Documentation/admin-guide/ |
| D | kernel-parameters.txt | 12 acpi= [HW,ACPI,X86,ARM64,RISCV64,EARLY]
33 acpi_apic_instance= [ACPI,IOAPIC,EARLY]
48 acpi_force_32bit_fadt_addr [ACPI,EARLY]
104 acpi_force_table_verification [HW,ACPI,EARLY]
105 Enable table checksum verification during early stage.
106 By default, this is disabled due to x86 early mapping
144 acpi_no_static_ssdt [HW,ACPI,EARLY]
145 Disable installation of static SSDTs at early boot time
158 acpi_rsdp= [ACPI,EFI,KEXEC,EARLY]
235 acpi_sci= [HW,ACPI,EARLY] ACPI System Control Interrupt trigger mode
[all …]
|
| D | braille-console.rst | 4 To get early boot messages on a braille device (before userspace screen
|
| /Documentation/core-api/ |
| D | debugging-via-ohci1394.rst | 34 Together with a early initialization of the OHCI-1394 controller for debugging,
36 buffer on to debug early boot problems in areas like ACPI where the system
48 completed, an initialization routine which runs pretty early has been
53 Remote debugging over FireWire early on boot) and pass the parameter
54 "ohci1394_dma=early" to the recompiled kernel on boot.
89 Step-by-step instructions for using firescope with early OHCI initialization:
147 4) Prepare for debugging with early OHCI-1394 initialization:
152 (Kernel hacking: Provide code for enabling DMA over FireWire early on boot)
164 CONFIG_PROVIDE_OHCI1394_DMA_INIT enabled, with the option ohci1394_dma=early.
|
| D | boot-time-mm.rst | 5 Early system initialization cannot use "normal" memory management
15 Once the early memory management is available it offers a variety of
|
| /Documentation/arch/riscv/ |
| D | boot.rst | 12 touching the early boot process. For the purposes of this document, the
13 ``early boot process`` refers to any code that runs before the final virtual
69 wins a lottery and executes the early boot code while the other harts are
105 Early Boot Requirements and Constraints
108 The RISC-V kernel's early boot process operates under the following constraints:
156 patching of early alternatives and the early parsing of the kernel command line.
|
| /Documentation/mm/ |
| D | hwpoison.rst | 62 early kill
81 Enable early kill mode globally
84 Set early/late kill mode/revert to system default
92 Early kill
116 some early filtering to avoid corrupted unintended pages in test suites.
|
| /Documentation/process/ |
| D | 3.Early-stage.rst | 3 Early-stage planning
9 line of code is written. Some time spent in early planning and
71 Early discussion
75 discussions with the community before launching into implementation. Early
122 avoided with some early discussion with the kernel developers.
170 If possible, posting your plans during the early stages can only be
211 disclose its plans early in the development process. Companies with
|
| D | development-process.rst | 22 3.Early-stage
|
| /Documentation/driver-api/usb/ |
| D | usb3-debug-port.rst | 35 EARLY PRINTK
38 DbC has been designed to log early printk messages. One use for
40 crashes very early before the regular console code is initialized.
65 During early boot of the debug target, DbC will be detected and
|
| /Documentation/translations/sp_SP/process/ |
| D | 3.Early-stage.rst | 3 :Original: Documentation/process/3.Early-stage.rst
|
| /Documentation/translations/zh_CN/process/ |
| D | development-process.rst | 20 3.Early-stage
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-tee | 15 tee-supplicant is needed in the early boot with initramfs.
|
| /Documentation/translations/zh_TW/process/ |
| D | development-process.rst | 23 3.Early-stage
|
| /Documentation/admin-guide/cifs/ |
| D | authors.rst | 11 Andrew Tridgell (Samba team) for his early suggestions about SMB/CIFS VFS
36 - Mark Hamzy (for some of the early cifs IPv6 work)
|
| /Documentation/arch/x86/ |
| D | microcode.rst | 18 Early load microcode
21 The kernel can update microcode very early during boot. Loading
22 microcode early can fix CPU issues before they are observed during
236 the final kernel image. The early loader finds them and applies them.
|
| D | earlyprintk.rst | 4 Early Printk
59 port and the NetChip device will only work as an early printk
110 this channel open beyond early bootup. This can be useful for
|
| /Documentation/filesystems/ |
| D | ramfs-rootfs-initramfs.rst | 113 see cpio(1) and Documentation/driver-api/early-userspace/buffer-format.rst).
167 Documentation/driver-api/early-userspace/early_userspace_support.rst for more details.)
253 designed to be a tiny C library to statically link early userspace
349 smooth transition and allowing early boot functionality to gradually move to
350 "early userspace" (I.E. initramfs).
352 The move to early userspace is necessary because finding and mounting the real
366 The kernel's current early boot code (partition detection, etc) will probably
|
| /Documentation/devicetree/ |
| D | usage-model.rst | 107 machine during early boot so that it has the opportunity to run
173 that required special workaround code during early boot, then a new
206 During early boot, the architecture setup code calls of_scan_flat_dt()
210 during early boot. Typically the early_init_dt_scan_chosen() helper
216 On ARM, the function setup_machine_fdt() is responsible for early
222 After the board has been identified, and after the early configuration data
233 specific setup that needs to be executed early in the boot process,
|
| /Documentation/devicetree/bindings/firmware/ |
| D | nvidia,tegra210-bpmp.txt | 4 in Tegra210 SoC. It is designed to handle the early stages of the boot
|
| /Documentation/translations/it_IT/process/ |
| D | development-process.rst | 27 3.Early-stage
|
| /Documentation/devicetree/bindings/cache/ |
| D | l2c2x0.yaml | 24 early secure boot code. Thus no need to deal with their configuration
213 arm,early-bresp-disable:
214 description: Disable the CA9 optimization Early BRESP (PL310)
|
| /Documentation/arch/powerpc/ |
| D | elfnote.rst | 30 trying to access ultravisor resources. For instance, it may crash in early
|
123456789