/linux-6.12.1/Documentation/arch/riscv/ |
D | boot.rst | 1 .. SPDX-License-Identifier: GPL-2.0 4 RISC-V Kernel Boot Requirements and Constraints 10 This document describes what the RISC-V kernel expects from bootloaders and 12 touching the early boot process. For the purposes of this document, the 16 Pre-kernel Requirements and Constraints 19 The RISC-V kernel expects the following of bootloaders and platform firmware: 22 -------------- 24 The RISC-V kernel expects: 26 * ``$a0`` to contain the hartid of the current core. 27 * ``$a1`` to contain the address of the devicetree in memory. [all …]
|
/linux-6.12.1/include/linux/ |
D | crash_dump.h | 1 /* SPDX-License-Identifier: GPL-2.0 */ 12 #define ELFCORE_ADDR_MAX (-1ULL) 13 #define ELFCORE_ADDR_ERR (-2ULL) 35 * machine types, e.g. on bi-arch capable hardware. */ 42 * needed for 32-bit ELF or 64-bit ELF vmcores. In case of 32-bit 55 * is_kdump_kernel() checks whether this kernel is booting after a panic of 60 * return true if CONFIG_CRASH_DUMP=y and if kernel is booting after a panic 61 * of previous kernel. 70 /* is_vmcore_usable() checks if the kernel is booting after a panic and 73 * This makes use of the fact that due to alignment -2ULL is not [all …]
|
/linux-6.12.1/Documentation/admin-guide/nfs/ |
D | nfsroot.rst | 10 Updated 2006 by Nico Schottelius <nico-kernel-nfsroot@schottelius.org> 18 In order to use a diskless system, such as an X-terminal or printer server for 19 example, it is necessary for the root filesystem to be present on a non-disk 21 Documentation/filesystems/ramfs-rootfs-initramfs.rst), a ramdisk (see 22 Documentation/admin-guide/initrd.rst) or a filesystem mounted via NFS. The 24 of this text 'client' means the diskless system, and 'server' means the NFS 34 built-in during configuration. Once this has been selected, the nfsroot 38 along with the types of autoconfiguration to support. Selecting all of 48 told what root fs device to use. And in the case of nfsroot, where to find 49 both the server and the name of the directory on the server to mount as root. [all …]
|
/linux-6.12.1/drivers/pci/ |
D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0 17 # without PCI itself having to be defined 26 support for PCI-X and the foundations for PCI Express support. 45 bool "Message Signaled Interrupts (MSI and MSI-X)" 51 PCI bus instead of asserting a device IRQ pin. 53 Use of PCI MSI interrupts can be disabled at kernel boot time 74 Say Y here if you want the PCI core to produce a bunch of debug 76 problem with PCI support and want to see more of what is going on. 81 bool "Enable PCI resource re-allocation detection" 85 re-allocation needs to be enabled. You can always use pci=realloc=on [all …]
|
/linux-6.12.1/Documentation/arch/powerpc/ |
D | booting.rst | 1 .. SPDX-License-Identifier: GPL-2.0 3 DeviceTree Booting 4 ------------------ 6 During the development of the Linux/ppc64 kernel, and more specifically, the 7 addition of new platform types outside of the old IBM pSeries/iSeries pair, it 9 bootloader <-> kernel interfaces, in order to avoid the degeneration that had 13 doesn't follow them properly. In addition, since the advent of the arch/powerpc 14 merged architecture for ppc32 and ppc64, new 32-bit platforms and 32-bit 19 of a device-tree whose format is defined after Open Firmware specification. 21 doesn't require the device-tree to represent every device in the system and only [all …]
|
/linux-6.12.1/arch/arm/mach-s3c/ |
D | init.c | 1 // SPDX-License-Identifier: GPL-2.0 10 * NOTE: Code in this file is not used on S3C64xx when booting with 21 #include <linux/of.h> 35 for (; count != 0; count--, tab++) { in s3c_lookup_cpu() 36 if ((idcode & tab->idmask) == (tab->idcode & tab->idmask)) in s3c_lookup_cpu() 53 printk("CPU %s (id 0x%08lx)\n", cpu->name, idcode); in s3c_init_cpu() 55 if (cpu->init == NULL) { in s3c_init_cpu() 56 printk(KERN_ERR "CPU %s support not enabled\n", cpu->name); in s3c_init_cpu() 60 if (cpu->map_io) in s3c_init_cpu() 61 cpu->map_io(); in s3c_init_cpu() [all …]
|
/linux-6.12.1/Documentation/devicetree/bindings/soc/fsl/cpm_qe/ |
D | serial.txt | 4 - fsl,cpm1-smc-uart 5 - fsl,cpm2-smc-uart 6 - fsl,cpm1-scc-uart 7 - fsl,cpm2-scc-uart 8 - fsl,qe-uart 11 property as described in booting-without-of.txt, section IX.1 in the following 23 compatible = "fsl,mpc8272-scc-uart", 24 "fsl,cpm2-scc-uart"; 27 interrupt-parent = <&PIC>; 28 fsl,cpm-brg = <1>; [all …]
|
/linux-6.12.1/arch/powerpc/platforms/ |
D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0 33 In case of doubt, say Y 36 bool "ePAPR para-virtualization support" 38 Enables ePAPR para-virtualization support for guests. 40 In case of doubt, say Y 46 Support for running natively on the hardware, i.e. without 47 a hypervisor. This option is not user-selectable but should 51 bool "Support booting from Open Firmware or yaboot" 56 Support from booting from Open Firmware or yaboot using an 61 In case of doubt, say Y [all …]
|
/linux-6.12.1/Documentation/admin-guide/ |
D | ldm.rst | 2 LDM - Logical Disk Manager (Dynamic Disks) 5 :Author: Originally Written by FlatCap - Richard Russon <ldm@flatcap.org>. 9 -------- 13 1MiB journalled database at the end of the physical disk. The size of 14 partitions is limited only by disk space. The maximum number of partitions is 23 partitions and filesystems without the need to reboot. 26 assemble any multi-partition volumes, e.g. Stripes, RAID5. 29 dummy MSDOS partition containing one disk-sized partition. This is what is 32 A newer approach that has been implemented with Vista is to put LDM on top of a 37 ------- [all …]
|
D | efi-stub.rst | 8 along with the EFI-specific entry point that the firmware loader 10 arch/x86/boot/header.S and drivers/firmware/efi/libstub/x86-stub.c, 12 arch/arm/boot/compressed/efi-header.S and 13 drivers/firmware/efi/libstub/arm32-stub.c. EFI stub code that is shared 19 and drivers/firmware/efi/libstub/arm64-stub.c. 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 30 -------------------------- 33 System Partition (ESP) and renamed with the extension ".efi". Without 43 -------------------------------------------- [all …]
|
D | initrd.rst | 15 where the kernel comes up with a minimum set of compiled-in drivers, and 18 This document gives a brief overview of the use of initrd. A more detailed 19 discussion of the boot process can be found in [#f1]_. 23 --------- 51 Boot command-line options 52 ------------------------- 70 Note: /dev/initrd is read-only and it can only be used once. As soon 80 ---------------------- 83 archive. On such systems, the creation of a ramdisk image doesn't need to 88 find . | cpio --quiet -H newc -o | gzip -9 -n > /boot/imagefile.img [all …]
|
D | serial-console.rst | 7 kernel - by default it is not compiled in. For PC style serial ports 10 :menuselection:`Character devices --> Serial drivers --> 8250/16550 and compatible serial support -… 18 The format of this option is:: 29 defines the baudrate/parity/bits/flow control of 31 speed, P is parity (n/o/e), N is number of bits, 51 1. The output will appear only on the first device of each defined type. 58 for other reasons. For example, because of a typo or because 70 because of the default behavior when no console device is specified, 77 If no console device is specified, the first device found capable of 96 rm -f console tty0 [all …]
|
/linux-6.12.1/arch/riscv/ |
D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only 3 # For a description of the syntax of this configuration file, 4 # see Documentation/kbuild/kconfig-language.rst. 63 # LLD >= 14: https://github.com/llvm/llvm-project/issues/50505 192 select OF 215 # Shadow call stack requires rustc version 1.82+ due to use of the 216 # -Zsanitizer=shadow-call-stack flag. 226 depends on $(cc-option,-fpatchable-function-entry=8) 229 def_bool $(cc-option,-fsanitize=shadow-call-stack) 230 …# https://github.com/riscv-non-isa/riscv-elf-psabi-doc/commit/a484e843e6eeb51f0cb7b8819e50da6d2444… [all …]
|
/linux-6.12.1/arch/mips/generic/ |
D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0 7 Select this from your board if the board must use a legacy, non-UHI, 8 boot protocol. This will cause the kernel to scan through the list of 10 kernel is booted without being provided with an FDT via the UHI 18 YAMON-provided environment variables into a device tree properties. 20 comment "Legacy (non-UHI/non-FIT) Boards" 23 bool "Support MIPS SEAD-3 boards" 27 Enable this to include support for booting on MIPS SEAD-3 FPGA-based 85 This requires u-boot on the platform. 93 This requires u-boot on the platform. [all …]
|
/linux-6.12.1/arch/arm/mach-mvebu/ |
D | platsmp-a9.c | 1 // SPDX-License-Identifier: GPL-2.0-only 3 * Symmetric Multi Processing (SMP) support for Marvell EBU Cortex-A9 8 * Gregory CLEMENT <gregory.clement@free-electrons.com> 9 * Thomas Petazzoni <thomas.petazzoni@free-electrons.com> 14 #include <linux/of.h> 29 pr_info("Booting CPU %d\n", cpu); in mvebu_cortex_a9_boot_secondary() 32 * Write the address of secondary startup into the system-wide in mvebu_cortex_a9_boot_secondary() 60 * because of the boot of a kexec'ed kernel, the PMSU configuration 85 * by themselves, without any help from a still alive CPU. 106 CPU_METHOD_OF_DECLARE(mvebu_armada_375_smp, "marvell,armada-375-smp", [all …]
|
/linux-6.12.1/Documentation/fb/ |
D | vesafb.rst | 8 of the BIOS, and use this as framebuffer device /dev/fb0, like the m68k 19 without using tiny, unreadable fonts. 20 * You can run XF68_FBDev on top of /dev/fb0 (=> non-accelerated X11 22 * Most important: boot logo :-) 33 Documentation/admin-guide/svga.rst for details. 36 graphics mode). Which of them takes over the console depends on 53 The video mode number of the Linux kernel is the VESA mode number plus 69 To enable one of those modes you have to specify "vga=ask" in the 80 1. Note: LILO cannot handle hex, for booting directly with 81 "vga=mode-number" you have to transform the numbers to decimal. [all …]
|
/linux-6.12.1/Documentation/devicetree/bindings/net/ |
D | fsl-tsec-phy.txt | 5 the definition of the PHY node in booting-without-of.txt for an example 6 of how to define a PHY. 9 - reg : Offset and length of the register set for the device, and optionally 10 the offset and length of the TBIPA register (TBI PHY address 14 - compatible : Should define the compatible device type for the 16 - "fsl,gianfar-tbi" 17 - "fsl,gianfar-mdio" 18 - "fsl,etsec2-tbi" 19 - "fsl,etsec2-mdio" 20 - "fsl,ucc-mdio" [all …]
|
D | fsl,fman-mdio.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/net/fsl,fman-mdio.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Frank Li <Frank.Li@nxp.com> 18 - fsl,fman-mdio 19 - fsl,fman-xmdio 20 - fsl,fman-memac-mdio 22 Must include "fsl,fman-mdio" for 1 Gb/s MDIO from FMan v2. 23 Must include "fsl,fman-xmdio" for 10 Gb/s MDIO from FMan v2. [all …]
|
/linux-6.12.1/Documentation/filesystems/ |
D | virtiofs.rst | 1 .. SPDX-License-Identifier: GPL-2.0 6 virtiofs: virtio-fs host<->guest shared file system 9 - Copyright (C) 2019 Red Hat, Inc. 14 VIRTIO "virtio-fs" device for guest<->host file system sharing. It allows a 19 booting from a root file system located on the host, persistent storage for 22 Although it is possible to use existing network file systems for some of these 24 expose the storage network to the guest. The virtio-fs device was designed to 25 solve these problems by providing file system access without networking. 27 Furthermore the virtio-fs device takes advantage of the co-location of the 35 .. code-block:: sh [all …]
|
/linux-6.12.1/Documentation/arch/arm/ |
D | booting.rst | 2 Booting ARM Linux 9 The following documentation is relevant to 2.4.18-rmk6 and beyond. 28 --------------------------- 38 to automatically locate and size all RAM, or it may use knowledge of 44 ----------------------------- 60 Documentation/admin-guide/kernel-parameters.rst. 64 -------------------------- 69 MANDATORY except for DT-only platforms 73 looks at the connected hardware is beyond the scope of this document. 75 value to the kernel. (see linux/arch/arm/tools/mach-types). This [all …]
|
/linux-6.12.1/Documentation/arch/arm64/ |
D | arm-acpi.rst | 10 of rules defined in SBSA (Server Base System Architecture) [2]. 12 The Arm kernel implements the reduced hardware model of ACPI version 18 If an Arm system does not meet the requirements of the BSA and BBR, 23 industry-standard Arm systems, they also apply to more than one operating 24 system. The purpose of this document is to describe the interaction between 25 ACPI and Linux only, on an Arm system -- that is, what Linux expects of 26 ACPI and what ACPI can expect of Linux. 30 ---------------- 31 Before examining the details of the interface between ACPI and Linux, it is 33 exist in Linux for describing non-enumerable hardware, after all. In this [all …]
|
/linux-6.12.1/arch/arm/mach-omap2/ |
D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only 95 select PINCTRL_TI_IODELAY if OF && PINCTRL 149 Compile a kernel suitable for booting most boards 166 version 2 of the SmartReflex IP. 168 V2 is the update for the 45nm version of the IP used in OMAP3630 182 bool "Class 3 mode of Smartreflex Implementation" 185 Say Y to enable Class 3 implementation of Smartreflex 187 Class 3 implementation of Smartreflex employs continuous hardware 194 Without this option, L2 Auxiliary control register contents are 195 lost during off-mode entry on HS/EMU devices. This feature [all …]
|
/linux-6.12.1/drivers/base/ |
D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0 12 Before the switch to the netlink-based uevent source, this was 19 it is known to create out-of-memory situations during bootup. 44 functional /dev without any further help. It also allows simple 58 This option does not affect initramfs based booting, here 73 with the PROT_EXEC flag. This can break, for example, non-KMS 77 bool "Select only drivers that don't need compile-time external firmware" 96 Firmware should not be being built as part of kernel, these days 98 old drivers which enable building of its firmware at kernel build 134 Say Y here if you want the Driver core to produce a bunch of [all …]
|
/linux-6.12.1/arch/arm64/include/asm/ |
D | cpufeature.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */ 9 #include <asm/alternative-macros.h> 32 * The safe value of a CPUID feature field is dependent on the implications 33 * of the values assigned to it by the architecture. Based on the relationship 34 * between the values, the features are classified into 3 types - LOWER_SAFE, 37 * The lowest value of all the CPUs is chosen for LOWER_SAFE and highest 76 * sanitised value of the register. Only the bitfields 78 * @mask Mask of the features that are overridden by @val 80 * A @mask field set to full-1 indicates that the corresponding field 83 * A @mask field set to full-0 with the corresponding @val field set [all …]
|
/linux-6.12.1/Documentation/devicetree/ |
D | usage-model.rst | 1 .. SPDX-License-Identifier: GPL-2.0 11 This article describes how Linux uses the device tree. An overview of 19 is a description of hardware that is readable by an operating system 20 so that the operating system doesn't need to hard code details of the 24 nodes may have an arbitrary number of named properties encapsulating 26 links from one node to another outside of the natural tree structure. 28 Conceptually, a common set of usage conventions, called 'bindings', 34 maximize use of existing support code, but since property and node 37 however, of creating a new binding without first doing some homework 40 binding was created without first investigating how i2c devices were [all …]
|