Home
last modified time | relevance | path

Searched +full:boot +full:- +full:page +full:- +full:step (Results 1 – 24 of 24) sorted by relevance

/Documentation/devicetree/bindings/mtd/
Damlogic,meson-nand.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/mtd/amlogic,meson-nand.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - $ref: nand-controller.yaml
13 - liang.yang@amlogic.com
18 - amlogic,meson-gxl-nfc
19 - amlogic,meson-axg-nfc
24 reg-names:
26 - const: nfc
[all …]
Dbrcm,brcmnand.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Brian Norris <computersforpeace@gmail.com>
11 - Kamal Dasu <kdasu.kdev@gmail.com>
12 - William Zhang <william.zhang@broadcom.com>
15 The Broadcom Set-Top Box NAND controller supports low-level access to raw NAND
16 flash chips. It has a memory-mapped register interface for both control
27 -- Additional SoC-specific NAND controller properties --
35 interesting ways, sometimes with registers that lump multiple NAND-related
[all …]
/Documentation/arch/riscv/
Dboot.rst1 .. 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
13 ``early boot process`` refers to any code that runs before the final virtual
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:
30 ---------
[all …]
/Documentation/admin-guide/
Dquickly-build-trimmed-linux.rst1 .. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0)
9 testing purposes, but perfectly fine for day-to-day use, too.
15 section below: it contains a step-by-step guide, which is more detailed, but
20 If your system uses techniques like Secure Boot, prepare it to permit starting
21 self-compiled Linux kernels; install compilers and everything else needed for
26 git clone --depth 1 -b master \
34 make -j $(nproc --all)
37 command -v installkernel && sudo make modules_install install
43 git fetch --depth 1 origin
45 git checkout --force --detach origin/master
[all …]
Dverify-bugs-and-bisect-regressions.rst1 .. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0)
9 currently supported by developers -- to then explain how to locate the change
22 read and navigate this document -- especially when you want to look something
26 https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html
32 over to the* ':ref:`step-by-step guide <introguide_bissbs>`' *below. It utilizes
45 *segment 2*. Then you can submit a preliminary report -- or continue with
47 full-fledged regression report. In the following example 6.0.13 is assumed to be
55 # * Ensure Secure Boot permits booting self-compiled Linux kernels.
59 git clone -o mainline --no-checkout \
62 git remote add -t master stable \
[all …]
Dbug-bisect.rst1 .. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0)
9 change that broke something -- for example when some functionality stopped
13 kernel, better follow Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst
17 care about the result -- for example, because the problem happens after the
28 use as pristine base at each bisection step; ideally, you have also worked out
29 a fully reliable and straight-forward way to reproduce the regression, too.*
38 Instead of Git tags like 'v6.0' and 'v6.1' you can specify commit-ids, too.
46 2. Now build, install, and boot a kernel. This might fail for unrelated reasons,
49 go back to step 1.
68 test after this (roughly 10 steps)'. In that case go back to step 1.
[all …]
Dkernel-parameters.txt5 avoid prolonged boot times. The lazy option will add
10 at once during boot.
16 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
[all …]
Dspkguide.txt16 Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
25 http://linux-speakup.org/. Speakup is a set of patches to the standard
44 is to boot your system, and Speakup should come up talking. This
60 the default one, then you may issue the following command at the boot
61 prompt of your boot loader.
66 DoubleTalk LT at boot up. You may replace the ltlk synthesizer keyword
72 acntsa -- Accent SA
73 acntpc -- Accent PC
74 apollo -- Apollo
75 audptr -- Audapter
[all …]
Dreporting-issues.rst1 .. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0)
36 ensure it's vanilla (IOW: not patched and not using add-on modules). Also make
44 to pin-point the culprit with a bisection; if you succeed, include its
45 commit-id and CC everyone in the sign-off-by chain.
51 Step-by-step guide how to report issues to the kernel maintainers
58 step-by-step approach. It still tries to be brief for readability and leaves
59 out a lot of details; those are described below the step-by-step guide in a
89 kernel modules on-the-fly, which solutions like DKMS might be doing locally
169 --------------------------------------------------------------
179 line you care about: go to the `front page of kernel.org
[all …]
/Documentation/firmware-guide/acpi/apei/
Deinj.rst1 .. SPDX-License-Identifier: GPL-2.0
11 for early boot messages similar to this one::
15 which shows that the BIOS is exposing an EINJ table - it is the
43 - available_error_type
51 0x00000002 Processor Uncorrectable non-fatal
54 0x00000010 Memory Uncorrectable non-fatal
57 0x00000080 PCI Express Uncorrectable non-fatal
60 0x00000400 Platform Uncorrectable non-fatal
67 - error_type
72 - error_inject
[all …]
/Documentation/arch/x86/
Dpat.rst1 .. SPDX-License-Identifier: GPL-2.0
4 PAT (Page Attribute Table)
7 x86 Page Attribute Table (PAT) allows for setting the memory attribute at the
8 page level granularity. PAT is complementary to the MTRR settings which allows
10 more flexible than MTRR due to its capability to set attributes at page level
20 WB Write-back
22 WC Write-combined
23 WT Write-through
24 UC- Uncached Minus
32 attributes at the page level. In order to avoid aliasing, these interfaces
[all …]
Dsgx.rst1 .. SPDX-License-Identifier: GPL-2.0
13 * Privileged (ring-0) ENCLS functions orchestrate the construction of the
15 * Unprivileged (ring-3) ENCLU functions allow an application to enter and
34 Enclave Page Cache
37 SGX utilizes an *Enclave Page Cache (EPC)* to store pages that are associated
38 with an enclave. It is contained in a BIOS-reserved region of physical memory.
48 Enclave Page Types
49 ------------------
64 number for a page evicted from the EPC.
66 Enclave Page Cache Map
[all …]
Dtdx.rst1 .. SPDX-License-Identifier: GPL-2.0
18 CPU-attested software module called 'the TDX module' runs inside the new
22 TDX also leverages Intel Multi-Key Total Memory Encryption (MKTME) to
23 provide crypto-protection to the VMs. TDX reserves part of MKTME KeyIDs
32 TDX boot-time detection
33 -----------------------
36 boot. Below dmesg shows when TDX is enabled by BIOS::
41 ---------------------------------------
59 Besides initializing the TDX module, a per-cpu initialization SEAMCALL
103 ------------------------------------------
[all …]
Dboot.rst1 .. 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 …]
/Documentation/filesystems/
Dramfs-rootfs-initramfs.rst1 .. SPDX-License-Identifier: GPL-2.0
12 --------------
15 mechanisms (the page cache and dentry cache) as a dynamically resizable
16 RAM-based filesystem.
28 dentries and page cache as usual, but there's nowhere to write them to.
39 ------------------
45 fake block device into the page cache (and copying changes back out), as well
51 to avoid this copying by playing with the page tables, but they're unpleasantly
54 since all file access goes through the page and dentry caches. The RAM
57 Another reason ramdisks are semi-obsolete is that the introduction of
[all …]
Dfsverity.rst1 .. SPDX-License-Identifier: GPL-2.0
6 fs-verity: read-only file-based authenticity protection
12 fs-verity (``fs/verity/``) is a support layer that filesystems can
14 of read-only files. Currently, it is supported by the ext4, f2fs, and
15 btrfs filesystems. Like fscrypt, not too much filesystem-specific
16 code is needed to support fs-verity.
18 fs-verity is similar to `dm-verity
19 <https://www.kernel.org/doc/Documentation/device-mapper/verity.txt>`_
21 filesystems supporting fs-verity, userspace can execute an ioctl that
23 it to a filesystem-specific location associated with the file.
[all …]
/Documentation/core-api/
Ddma-isa-lpc.rst12 ------------------------
16 #include <linux/dma-mapping.h>
20 bus addresses (see Documentation/core-api/dma-api.rst for details).
28 -----------------
37 The DMA-able address space is the lowest 16 MB of _physical_ memory.
38 Also the transfer block may not cross page boundaries (which are 64
45 allocate the memory during boot-up it's a good idea to also pass
52 -------------------
66 --------
69 8-bit transfers and the upper four are for 16-bit transfers.
[all …]
/Documentation/virt/hyperv/
Dvmbus.rst1 .. SPDX-License-Identifier: GPL-2.0
5 VMBus is a software construct provided by Hyper-V to guest VMs. It
7 devices that Hyper-V presents to guest VMs. The control path is
11 and the synthetic device implementation that is part of Hyper-V, and
12 signaling primitives to allow Hyper-V and the guest to interrupt
17 establishes the VMBus control path with the Hyper-V host, then
21 Most synthetic devices offered by Hyper-V have a corresponding Linux
29 * PCI device pass-thru
34 * Key/Value Pair (KVP) exchange with Hyper-V
35 * Hyper-V online backup (a.k.a. VSS)
[all …]
/Documentation/security/
Dipe.rst1 .. SPDX-License-Identifier: GPL-2.0
3 Integrity Policy Enforcement (IPE) - Kernel Documentation
10 :doc:`IPE admin guide </admin-guide/LSM/ipe>`.
13 ---------------------
16 of a locked-down system. This system would be born-secure, and have
27 2. DM-Verity
29 Both options were carefully considered, however the choice to use DM-Verity
46 modify filesystem offline, the attacker could wipe all the xattrs -
50 With DM-Verity, as the xattrs are saved as part of the Merkel tree, if
51 offline mount occurs against the filesystem protected by dm-verity, the
[all …]
/Documentation/dev-tools/kunit/
Dstart.rst1 .. SPDX-License-Identifier: GPL-2.0
7 This page contains an overview of the kunit_tool and KUnit framework,
22 .. code-block:: bash
32 through the argument ``--build_dir``. Hence, before starting an
33 out-of-tree build, the source tree must be clean.
36 the kernel" section of the :doc:`admin-guide </admin-guide/README>`,
44 .. code-block::
54 the ``Building KUnit Kernel`` step may take a while.
57 Documentation/dev-tools/kunit/run_wrapper.rst.
60 ----------------------------
[all …]
/Documentation/driver-api/
Dvfio.rst2 VFIO - "Virtual Function I/O" [1]_
7 allotted. This includes x86 hardware with AMD-Vi and Intel VT-d,
12 safe [2]_, non-privileged, userspace drivers.
19 bare-metal device drivers [3]_.
22 field, also benefit from low-overhead, direct device access from
23 userspace. Examples include network adapters (often non-TCP/IP based)
36 ---------------------------
42 as allowing a device read-write access to system memory imposes the
55 For instance, an individual device may be part of a larger multi-
59 could be anything from a multi-function PCI device with backdoors
[all …]
/Documentation/driver-api/crypto/iaa/
Diaa-crypto.rst1 .. SPDX-License-Identifier: GPL-2.0
18 higher-level compression devices such as zswap.
25 represented by selecting the 'deflate-iaa' crypto compression
28 # echo deflate-iaa > /sys/module/zswap/parameters/compressor
38 'deflate-iaa'. (Because the IAA hardware has a 4k history-window
52 Cryptographic API -> Hardware crypto devices -> Support for Intel(R) IAA Compression Accelerator
59 …Cryptographic API -> Hardware crypto devices -> Support for Intel(R) IAA Compression -> Enable Int…
78 - Scalable
79 - Legacy
80 - No IOMMU
[all …]
/Documentation/virt/kvm/
Dapi.rst1 .. SPDX-License-Identifier: GPL-2.0
4 The Definitive KVM (Kernel-based Virtual Machine) API Documentation
13 - System ioctls: These query and set global attributes which affect the
17 - VM ioctls: These query and set attributes that affect an entire virtual
24 - vcpu ioctls: These query and set attributes that control the operation
32 - device ioctls: These query and set attributes that control the operation
80 facility that allows backward-compatible extensions to the API to be
104 the ioctl returns -ENOTTY.
122 -----------------------
139 -----------------
[all …]
/Documentation/trace/
Dkprobes.rst29 collect debugging and performance information non-disruptively. You
41 In the typical case, Kprobes-based instrumentation is packaged as
56 Kprobes -- e.g., the difference between a pre_handler and
62 -----------------------
74 Next, Kprobes single-steps its copy of the probed instruction.
75 (It would be simpler to single-step the actual instruction in place,
80 After the instruction is single-stepped, Kprobes executes the
85 -----------------------
105 -------------
114 is an arbitrary piece of code -- typically just a nop instruction.
[all …]