Home
last modified time | relevance | path

Searched +full:mode +full:- +full:loader (Results 1 – 25 of 38) sorted by relevance

12

/Documentation/arch/arm/
Dbooting.rst9 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 ---------------------------
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 -----------------------------
51 The boot loader should initialise and enable one serial port on the
56 As an alternative, the boot loader can pass the relevant 'console='
[all …]
Duefi.rst7 maintained by the UEFI Forum - http://www.uefi.org/.
19 - UEFI Runtime Services
20 - Retrieving various configuration information through the standardised
25 - CONFIG_EFI=y
26 - CONFIG_EFIVAR_FS=y or m
29 in a Flattened Device Tree (FDT) - so is only available with CONFIG_OF.
34 PE/COFF executable, including a loader application that makes it possible to
39 booting in non-UEFI environments.
46 When booting in UEFI mode, the stub deletes any memory nodes from a provided DT.
55 linux,uefi-system-table 64-bit Physical address of the UEFI System Table.
[all …]
/Documentation/arch/x86/
Dboot.rst1 .. SPDX-License-Identifier: GPL-2.0
12 real-mode DOS as a mainstream operating system.
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
40 Protocol 2.05 (Kernel 2.6.20) Make protected mode kernel relocatable.
54 Protocol 2.09 (Kernel 2.6.26) Added a field of 64-bit physical
59 pref_address fields. Added extended boot loader IDs.
68 Protocol 2.13 (Kernel 3.14) Support 32- and 64-bit flags being set in
[all …]
Dshstk.rst1 .. SPDX-License-Identifier: GPL-2.0
4 Control-flow Enforcement Technology (CET) Shadow Stack
10 Control-flow Enforcement Technology (CET) covers several related x86 processor
20 control-protection fault. IBT verifies indirect CALL/JMP targets are intended
22 Stack and Indirect Branch Tracking. Today in the 64-bit kernel, only userspace
45 from readelf/llvm-readelf output::
47 readelf -n <application> | grep -a SHSTK
52 Typically this would be done in dynamic loader or static runtime objects, as is
58 Elf features should be enabled by the loader using the below arch_prctl's. They
60 on a per-thread basis. The enablement status is inherited on clone, so if the
[all …]
/Documentation/devicetree/bindings/power/reset/
Dreboot-mode.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/power/reset/reboot-mode.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Generic reboot mode core map
10 - Andy Yan <andy.yan@rock-chips.com>
13 This driver get reboot mode arguments and call the write
18 All mode properties are vendor specific, it is a indication to tell
20 as mode-xxx = <magic> (xxx is mode name, magic should be a non-zero value).
23 - normal: Normal reboot mode, system reboot with command "reboot".
[all …]
Dsyscon-reboot-mode.yaml1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/power/reset/syscon-reboot-mode.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Generic SYSCON reboot mode driver
10 - Sebastian Reichel <sre@kernel.org>
13 This driver gets reboot mode magic value from reboot-mode driver
17 parental dt-node plus the offset. So the SYSCON reboot-mode node
18 should be represented as a sub-node of a "syscon", "simple-mfd" node.
22 const: syscon-reboot-mode
[all …]
/Documentation/devicetree/bindings/clock/
Dqcom,sc7280-lpasscc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/clock/qcom,sc7280-lpasscc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Taniya Das <quic_tdas@quicinc.com>
16 See also:: include/dt-bindings/clock/qcom,lpass-sc7280.h
21 - qcom,sc7280-lpasscc
25 - description: gcc_cfg_noc_lpass_clk from GCC
27 clock-names:
29 - const: iface
[all …]
Dqcom,sc7280-lpasscorecc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/clock/qcom,sc7280-lpasscorecc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Taniya Das <quic_tdas@quicinc.com>
17 include/dt-bindings/clock/qcom,lpasscorecc-sc7280.h
18 include/dt-bindings/clock/qcom,lpassaudiocc-sc7280.h
23 clock-names: true
29 - qcom,sc7280-lpassaoncc
30 - qcom,sc7280-lpassaudiocc
[all …]
/Documentation/devicetree/bindings/sram/
Dqcom,imem.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Bjorn Andersson <bjorn.andersson@linaro.org>
19 - enum:
20 - qcom,apq8064-imem
21 - qcom,msm8226-imem
22 - qcom,msm8974-imem
23 - qcom,qcs404-imem
24 - qcom,qdu1000-imem
[all …]
/Documentation/arch/arm64/
Dbooting.rst13 (EL0 - EL3), with EL0, EL1 and EL2 having a secure and a non-secure
15 level and exists only in secure mode. Both are architecturally optional.
17 For the purposes of this document, we will use the term `boot loader`
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
59 ------------------------------
[all …]
Dpointer-authentication.rst7 Date: 2017-07-19
14 ---------------------
27 of high-order bits of the pointer, which varies dependent on the
36 The extension provides five separate keys to generate PACs - two for
42 -------------
69 ---------
89 --------------
102 on VHE mode to be present.
112 ---------------------------
133 The idea is that a dynamic loader or early startup code would issue this
/Documentation/userspace-api/
Dno_new_privs.rst5 The execve system call can grant a newly-started program privileges that
12 - The dynamic loader handles ``LD_*`` environment variables differently if
15 - chroot is disallowed to unprivileged processes, since it would allow
19 - The exec code has special handling for ptrace.
21 These are all ad-hoc fixes. The ``no_new_privs`` bit (since Linux 3.5) is a
37 in ``no_new_privs`` mode. (This means that setting up a general-purpose
39 interfere with LSM-based sandboxing.)
47 - Filters installed for the seccomp mode 2 sandbox persist across
48 execve and can change the behavior of newly-executed programs.
52 - By itself, ``no_new_privs`` can be used to reduce the attack surface
[all …]
/Documentation/sound/
Dalsa-configuration.rst2 Advanced Linux Sound Architecture - Driver Configuration guide
38 ----------
47 limiting card index for auto-loading (1-8);
49 For auto-loading more than one card, specify this option
50 together with snd-card-X aliases.
63 Module snd-pcm-oss
64 ------------------
86 regarding opening the device. When this option is non-zero,
90 Module snd-rawmidi
91 ------------------
[all …]
/Documentation/devicetree/bindings/net/can/
Dfsl,flexcan.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 Flexcan CAN controller on Freescale's ARM and PowerPC system-on-a-chip (SOC).
11 - Marc Kleine-Budde <mkl@pengutronix.de>
14 - $ref: can-controller.yaml#
19 - enum:
20 - fsl,imx95-flexcan
21 - fsl,imx93-flexcan
22 - fsl,imx8qm-flexcan
[all …]
/Documentation/arch/arm/samsung/
Dbootloader-interface.rst14 In the document "boot loader" means any of following: U-boot, proprietary
19 1. Non-Secure mode
37 2. Secure mode
65 3. Other (regardless of secure/non-secure mode)
72 0x0908 Non-zero Secondary CPU boot up indicator
79 AFTR - ARM Off Top Running, a low power mode, Cortex cores and many other
81 MCPM - Multi-Cluster Power Management
/Documentation/devicetree/bindings/powerpc/fsl/
Dmpc5200.txt2 ----------------------------
4 (c) 2006-2009 Secret Lab Technologies Ltd
8 ------------------
9 For mpc5200 on-chip devices, the format for each compatible value is
10 <chip>-<device>[-<mode>]. The OS should be able to match a device driver
21 "fsl,mpc5200-<device>".
26 devices have extra functions but still have a backwards compatible mode.
29 compatible = "fsl,mpc5200b-<device>","fsl,mpc5200-<device>";
34 ie. ethernet on mpc5200: compatible = "fsl,mpc5200-fec";
35 ethernet on mpc5200b: compatible = "fsl,mpc5200b-fec", "fsl,mpc5200-fec";
[all …]
/Documentation/admin-guide/
Dext4.rst1 .. SPDX-License-Identifier: GPL-2.0
9 (64 bit) in keeping with increasing disk capacities and state-of-the-art
12 Mailing list: linux-ext4@vger.kernel.org
23 - The latest version of e2fsprogs can be found at:
35 - Create a new filesystem using the ext4 filesystem type:
37 # mke2fs -t ext4 /dev/hda1
41 # tune2fs -O extents /dev/hda1
46 # tune2fs -I 256 /dev/hda1
48 - Mounting:
50 # mount -t ext4 /dev/hda1 /wherever
[all …]
Dsvga.rst4 Video Mode Selection Support 2.13
7 :Copyright: |copy| 1995--1999 Martin Mares, <mj@ucw.cz>
12 This small document describes the "Video Mode Selection" feature which
21 enter ``scan`` on the video mode prompt, pick the mode you want to use,
22 remember its mode ID (the four-digit hexadecimal number) and then
25 The video mode to be used is selected by a kernel parameter which can be
27 option of LILO (or some other boot loader you use) or by the "xrandr" utility
31 NORMAL_VGA - Standard 80x25 mode available on all display adapters.
33 EXTENDED_VGA - Standard 8-pixel font mode: 80x43 on EGA, 80x50 on VGA.
35 ASK_VGA - Display a video mode menu upon startup (see below).
[all …]
DREADME.rst11 --------------
14 Linus Torvalds with assistance from a loosely-knit team of hackers across
17 It has all the features you would expect in a modern fully-fledged Unix,
19 loading, shared copy-on-write executables, proper memory management,
22 It is distributed under the GNU General Public License v2 - see the
26 -----------------------------
28 Although originally developed first for 32-bit x86-based PCs (386 or higher),
31 IBM S/390, MIPS, HP PA-RISC, Intel IA-64, DEC VAX, AMD x86-64 Xtensa, and
34 Linux is easily portable to most general-purpose 32- or 64-bit architectures
40 userspace application - this is called UserMode Linux (UML).
[all …]
Dkernel-parameters.txt16 force -- enable ACPI if default was off
17 on -- enable ACPI but allow fallback to DT [arm64,riscv64]
18 off -- disable ACPI if default was on
19 noirq -- do not use ACPI for IRQ routing
20 strict -- Be less tolerant of platforms that are not
22 rsdt -- prefer RSDT over (default) XSDT
23 copy_dsdt -- copy DSDT to memory
24 nospcr -- disable console in ACPI SPCR table as
41 If set to vendor, prefer vendor-specific driver
45 If set to native, use the device's native backlight mode.
[all …]
/Documentation/admin-guide/pm/
Dsleep-states.rst1 .. SPDX-License-Identifier: GPL-2.0
13 Sleep states are global low-power states of the entire system in which user
28 Suspend-to-Idle
29 ---------------
31 This is a generic, pure software, light-weight variant of system suspend (also
34 I/O devices into low-power states (possibly lower-power than available in the
38 The system is woken up from this state by in-band interrupts, so theoretically
43 or :ref:`suspend-to-RAM <s2ram>`, or it can be used in addition to any of the
50 -------
58 I/O devices into low-power states, which is done for :ref:`suspend-to-idle
[all …]
/Documentation/admin-guide/kdump/
Dkdump.rst2 Documentation for Kdump - The kexec-based Crash Dumping Solution
11 Kdump uses kexec to quickly boot to a dump-capture kernel whenever a
14 the reboot and is accessible to the dump-capture kernel.
24 the dump-capture kernel. This ensures that ongoing Direct Memory Access
25 (DMA) from the system kernel does not corrupt the dump-capture kernel.
26 The kexec -p command loads the dump-capture kernel into this reserved
47 passed to the dump-capture kernel through the elfcorehdr= boot
51 With the dump-capture kernel, you can access the memory image through
52 /proc/vmcore. This exports the dump as an ELF-format file that you can
55 options, e.g with '-d 31' it will only write out kernel data. Further,
[all …]
/Documentation/networking/device_drivers/wifi/intel/
Dipw2200.rst1 .. SPDX-License-Identifier: GPL-2.0
11 - Intel(R) PRO/Wireless 2200BG Network Connection
12 - Intel(R) PRO/Wireless 2915ABG Network Connection
20 Copyright |copy| 2004-2006, Intel Corporation
37 2. Ad-Hoc Networking
39 3.1. iwconfig mode
78 the warranty and/or issues arising from regulatory non-compliance, and
83 modules, and accordingly, condition system-level regulatory approval
86 non-compliant.
113 -------------------------
[all …]
/Documentation/driver-api/pm/
Ddevices.rst1 .. SPDX-License-Identifier: GPL-2.0
10 :Copyright: |copy| 2010-2011 Rafael J. Wysocki <rjw@sisk.pl>, Novell Inc.
18 management (PM) code is also driver-specific. Most drivers will do very
22 This writeup gives an overview of how drivers interact with system-wide
25 background for the domain-specific work you'd do with any specific driver.
31 Drivers will use one or both of these models to put devices into low-power
36 Drivers can enter low-power states as part of entering system-wide
37 low-power states like "suspend" (also known as "suspend-to-RAM"), or
39 "suspend-to-disk").
42 by implementing various role-specific suspend and resume methods to
[all …]
/Documentation/i2c/
Dwriting-clients.rst19 it for non-exported symbols too. We will use the prefix ``foo_`` in this
28 routines, and should be zero-initialized except for fields with data you
29 provide. A client structure holds device-specific information like the
62 All other fields are for call-back functions which will be explained
70 structure at all. You should use this to keep device-specific data.
81 to NULL in remove() or if probe() failed anymore. The i2c-core does this
95 but many chips have some kind of register-value idea that can easily
103 if (reg < 0x10) /* byte-sized register */
105 else /* word-sized register */
111 if (reg == 0x10) /* Impossible to write - driver error! */
[all …]

12