Searched +full:boot +full:- +full:loader (Results 1 – 25 of 716) sorted by relevance
12345678910>>...29
| /kernel/linux/linux-6.6/arch/arm/boot/dts/intel/axm/ |
| D | axm5516-cpus.dtsi | 1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * arch/arm/boot/dts/axm5516-cpus.dtsi
10 #address-cells = <1>;
11 #size-cells = <0>;
13 cpu-map {
74 compatible = "arm,cortex-a15";
76 clock-frequency = <1400000000>;
77 cpu-release-addr = <0>; // Fixed by the boot loader
82 compatible = "arm,cortex-a15";
84 clock-frequency = <1400000000>;
[all …]
|
| /kernel/linux/linux-5.10/arch/arm/boot/dts/ |
| D | axm5516-cpus.dtsi | 1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * arch/arm/boot/dts/axm5516-cpus.dtsi
10 #address-cells = <1>;
11 #size-cells = <0>;
13 cpu-map {
74 compatible = "arm,cortex-a15";
76 clock-frequency= <1400000000>;
77 cpu-release-addr = <0>; // Fixed by the boot loader
82 compatible = "arm,cortex-a15";
84 clock-frequency= <1400000000>;
[all …]
|
| /kernel/linux/linux-5.10/Documentation/arm/ |
| D | booting.rst | 9 The following documentation is relevant to 2.4.18-rmk6 and beyond.
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
28 ---------------------------
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
44 -----------------------------
[all …]
|
| /kernel/linux/linux-6.6/Documentation/arch/arm/ |
| D | booting.rst | 9 The following documentation is relevant to 2.4.18-rmk6 and beyond.
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
28 ---------------------------
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
44 -----------------------------
[all …]
|
| /kernel/linux/linux-6.6/Documentation/arch/x86/ |
| D | boot.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 The Linux/x86 Boot Protocol
7 On the x86 platform, the Linux kernel uses a rather complicated boot
12 real-mode DOS as a mainstream operating system.
14 Currently, the following versions of the Linux/x86 boot protocol exist.
22 boot loader and the kernel. setup.S made relocatable,
28 Protocol 2.02 (Kernel 2.4.0-test3-pre3) New command line protocol.
31 safe for systems which use the EBDA from SMM or 32-bit
35 Protocol 2.03 (Kernel 2.4.18-pre1) Explicitly makes the highest possible
44 the boot command line.
[all …]
|
| D | microcode.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 The Linux Microcode Loader
7 :Authors: - Fenghua Yu <fenghua.yu@intel.com>
8 - Borislav Petkov <bp@suse.de>
9 - Ashok Raj <ashok.raj@intel.com>
13 updating the microcode on platforms beyond the OEM End-Of-Life support,
14 and updating the microcode on long-running systems without rebooting.
16 The loader supports three loading methods:
21 The kernel can update microcode very early during boot. Loading
23 kernel boot time.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/x86/ |
| D | boot.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 The Linux/x86 Boot Protocol
7 On the x86 platform, the Linux kernel uses a rather complicated boot
12 real-mode DOS as a mainstream operating system.
14 Currently, the following versions of the Linux/x86 boot protocol exist.
22 boot loader and the kernel. setup.S made relocatable,
28 Protocol 2.02 (Kernel 2.4.0-test3-pre3) New command line protocol.
31 safe for systems which use the EBDA from SMM or 32-bit
35 Protocol 2.03 (Kernel 2.4.18-pre1) Explicitly makes the highest possible
44 the boot command line.
[all …]
|
| D | microcode.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 The Linux Microcode Loader
7 :Authors: - Fenghua Yu <fenghua.yu@intel.com>
8 - Borislav Petkov <bp@suse.de>
12 updating the microcode on platforms beyond the OEM End-Of-Life support,
13 and updating the microcode on long-running systems without rebooting.
15 The loader supports three loading methods:
20 The kernel can update microcode very early during boot. Loading
22 kernel boot time.
24 The microcode is stored in an initrd file. During boot, it is read from
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | efi-stub.rst | 2 The EFI Boot Stub
8 along with the EFI-specific entry point that the firmware loader
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
18 kernel. The arm64 EFI stub lives in arch/arm64/kernel/efi-entry.S
19 and drivers/firmware/efi/libstub/arm64-stub.c.
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
[all …]
|
| D | initrd.rst | 8 initrd provides the capability to load a RAM disk by the boot loader.
15 where the kernel comes up with a minimum set of compiled-in drivers, and
19 discussion of the boot process can be found in [#f1]_.
23 ---------
27 1) the boot loader loads the kernel and the initial RAM disk
42 the usual boot sequence
51 Boot command-line options
52 -------------------------
70 Note: /dev/initrd is read-only and it can only be used once. As soon
76 initrd is mounted as root, and the normal boot procedure is followed,
[all …]
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/ |
| D | efi-stub.rst | 2 The EFI Boot Stub
8 along with the EFI-specific entry point that the firmware loader
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
13 drivers/firmware/efi/libstub/arm32-stub.c. EFI stub code that is shared
18 kernel. The arm64 EFI stub lives in arch/arm64/kernel/efi-entry.S
19 and drivers/firmware/efi/libstub/arm64-stub.c.
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
[all …]
|
| D | initrd.rst | 8 initrd provides the capability to load a RAM disk by the boot loader.
15 where the kernel comes up with a minimum set of compiled-in drivers, and
19 discussion of the boot process can be found in [#f1]_.
23 ---------
27 1) the boot loader loads the kernel and the initial RAM disk
42 the usual boot sequence
51 Boot command-line options
52 -------------------------
70 Note: /dev/initrd is read-only and it can only be used once. As soon
76 initrd is mounted as root, and the normal boot procedure is followed,
[all …]
|
| /kernel/linux/linux-6.6/arch/riscv/boot/ |
| D | Makefile | 2 # arch/riscv/boot/Makefile
5 # architecture-specific flags and dependencies.
14 # Based on the ia64 and arm64 boot/Makefile.
19 OBJCOPYFLAGS_Image :=-O binary -R .note -R .note.gnu.build-id -R .comment -S
20 OBJCOPYFLAGS_loader.bin :=-O binary
21 OBJCOPYFLAGS_xipImage :=-O binary -R .note -R .note.gnu.build-id -R .comment -S
23 targets := Image Image.* loader loader.o loader.lds loader.bin
24 targets := Image Image.* loader loader.o loader.lds loader.bin xipImage
39 …@ (! [ -f vmlinux.relocs ] && echo "vmlinux.relocs can't be found, please remove vmlinux and try a…
50 $(obj)/loader.o: $(src)/loader.S $(obj)/Image
[all …]
|
| /kernel/linux/linux-5.10/arch/riscv/boot/ |
| D | Makefile | 2 # arch/riscv/boot/Makefile
5 # architecture-specific flags and dependencies.
14 # Based on the ia64 and arm64 boot/Makefile.
19 OBJCOPYFLAGS_Image :=-O binary -R .note -R .note.gnu.build-id -R .comment -S
21 targets := Image loader
29 $(obj)/loader.o: $(src)/loader.S $(obj)/Image
31 $(obj)/loader: $(obj)/loader.o $(obj)/Image $(obj)/loader.lds FORCE
32 $(Q)$(LD) -T $(obj)/loader.lds -o $@ $(obj)/loader.o
46 $(obj)/loader.bin: $(obj)/loader FORCE
|
| /kernel/linux/linux-6.6/arch/xtensa/boot/boot-redboot/ |
| D | bootstrap.S | 1 /* SPDX-License-Identifier: GPL-2.0 */
8 * RB-Data: RedBoot data/bss
9 * P: Boot-Parameters
10 * L: Kernel-Loader
12 * The Linux-Kernel image including the loader must be loaded
13 * to a position so that the kernel and the boot parameters
16 * |_RB-Data_|_P_|__________|_L_|___Linux-Kernel___|______|
20 * |___Linux-Kernel___|_P_|_L_|___________________________|
22 * The loader copies the parameter to the position that will
38 /* this must be the first byte of the loader! */
[all …]
|
| /kernel/linux/linux-5.10/arch/xtensa/boot/boot-redboot/ |
| D | bootstrap.S | 1 /* SPDX-License-Identifier: GPL-2.0 */
7 * RB-Data: RedBoot data/bss
8 * P: Boot-Parameters
9 * L: Kernel-Loader
11 * The Linux-Kernel image including the loader must be loaded
12 * to a position so that the kernel and the boot parameters
15 * |_RB-Data_|_P_|__________|_L_|___Linux-Kernel___|______|
19 * |___Linux-Kernel___|_P_|_L_|___________________________|
21 * The loader copies the parameter to the position that will
37 /* this must be the first byte of the loader! */
[all …]
|
| /kernel/linux/linux-5.10/arch/riscv/ |
| D | Makefile | 2 # architecture-specific flags and dependencies. Remember to do have actions
11 OBJCOPYFLAGS := -O binary
14 LDFLAGS_vmlinux := --no-relax
18 KBUILD_CFLAGS_MODULE += -mcmodel=medany
26 KBUILD_CFLAGS += -mabi=lp64
27 KBUILD_AFLAGS += -mabi=lp64
29 KBUILD_LDFLAGS += -melf64lriscv
34 KBUILD_CFLAGS += -mabi=ilp32
35 KBUILD_AFLAGS += -mabi=ilp32
36 KBUILD_LDFLAGS += -melf32lriscv
[all …]
|
| /kernel/linux/linux-6.6/security/tomoyo/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
11 This selects TOMOYO Linux, pathname-based access control.
41 bool "Activate without calling userspace policy loader."
45 Say Y here if you want to activate access control as soon as built-in
47 operations which can lead to the hijacking of the boot sequence are
54 hijacking the boot sequence.
57 string "Location of userspace policy loader"
58 default "/sbin/tomoyo-init"
62 This is the default pathname of policy loader which is called before
67 string "Trigger for calling userspace policy loader"
[all …]
|
| /kernel/linux/linux-5.10/security/tomoyo/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
13 This selects TOMOYO Linux, pathname-based access control.
43 bool "Activate without calling userspace policy loader."
47 Say Y here if you want to activate access control as soon as built-in
49 operations which can lead to the hijacking of the boot sequence are
56 hijacking the boot sequence.
59 string "Location of userspace policy loader"
60 default "/sbin/tomoyo-init"
64 This is the default pathname of policy loader which is called before
69 string "Trigger for calling userspace policy loader"
[all …]
|
| /kernel/linux/linux-5.10/Documentation/arm64/ |
| D | booting.rst | 13 (EL0 - EL3), with EL0 and EL1 having a secure and a non-secure
14 counterpart. EL2 is the hypervisor level and exists only in non-secure
17 For the purposes of this document, we will use the term `boot loader`
21 preparing a minimal boot environment.
23 Essentially, the boot loader should provide (as a minimum) the
33 ---------------------------
37 The boot loader is expected to find and initialise all RAM that the
41 the RAM in the machine, or any other method the boot loader designer
46 -------------------------
50 The device tree blob (dtb) must be placed on an 8-byte boundary and must
[all …]
|
| /kernel/linux/linux-5.10/drivers/firmware/efi/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
45 Export efi runtime memory maps to /sys/firmware/efi/runtime-map.
49 See also Documentation/ABI/testing/sysfs-firmware-efi-runtime-map.
56 Saying Y here will enable "efi_fake_mem" boot option.
64 int "maximum allowable number of ranges in efi_fake_mem boot option"
69 Maximum allowable number of ranges in efi_fake_mem boot option.
70 Ranges can be set up to this value using comma-separated list.
86 resource, and set aside for direct-access (device-dax) by
89 device-dax kmem facility. Say N to have the kernel treat this
108 bool "Enable the DTB loader"
[all …]
|
| /kernel/linux/linux-6.6/arch/riscv/ |
| D | Makefile | 2 # architecture-specific flags and dependencies.
9 LDFLAGS_vmlinux := -z norelro
11 LDFLAGS_vmlinux += -shared -Bsymbolic -z notext --emit-relocs
12 KBUILD_CFLAGS += -fPIE
15 LDFLAGS_vmlinux += --no-relax
16 KBUILD_CPPFLAGS += -DCC_USING_PATCHABLE_FUNCTION_ENTRY
18 CC_FLAGS_FTRACE := -fpatchable-function-entry=4
20 CC_FLAGS_FTRACE := -fpatchable-function-entry=2
25 KBUILD_CFLAGS_MODULE += -mcmodel=medany
33 KBUILD_CFLAGS += -mabi=lp64
[all …]
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | sysfs-firmware-acpi | 6 information for firmware performance data for system boot,
10 boot:
14 loading the OS boot loader into memory.
17 launching the currently loaded OS boot loader
20 point when the OS loader calls the
24 just prior to the OS loader gaining control
36 since the last full boot sequence.
38 logged since the last full boot sequence,
49 to obtain a copy of the firmware boot splash and
51 by boot splash applications in order to interact with
[all …]
|
| /kernel/linux/linux-6.6/Documentation/networking/devlink/ |
| D | sfc.rst | 1 .. SPDX-License-Identifier: GPL-2.0
15 .. list-table:: devlink info versions implemented
18 * - Name
19 - Type
20 - Description
21 * - ``fw.mgmt.suc``
22 - running
23 - For boards where the management function is split between multiple
25 * - ``fw.mgmt.cmc``
26 - running
[all …]
|
| /kernel/linux/linux-6.6/drivers/firmware/efi/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
42 resource, and set aside for direct-access (device-dax) by
45 device-dax kmem facility. Say N to have the kernel treat this
59 attributes during boot via EFISTUB to ensure that memory
87 memory before executing it via LoadImage/StartImage EFI boot service
88 calls. For compatibility with non-EFI loaders, the payload can be
89 decompressed and executed by the loader as well, provided that the
90 loader implements the decompression algorithm and that non-EFI boot
95 bool "Enable the DTB loader"
117 bootloader. If the string matches one of the boot labels
[all …]
|
12345678910>>...29