Searched +full:boot +full:- +full:up (Results 1 – 25 of 346) sorted by relevance
12345678910>>...14
| /Documentation/trace/ |
| D | debugging.rst | 11 - Written for: 6.12
14 ------------
21 $ sudo mount -t tracefs tracefs /sys/kernel/tracing
25 --------------------
57 ------------------------
61 It can be very useful in knowing what happened up to the point of the crash.
64 the ring buffer will be all the events that lead up to the crash.
76 Note, the tracing buffer is made up of per CPU buffers where each of these
77 buffers is broken up into sub-buffers that are by default PAGE_SIZE. The
82 -------------------------------
[all …]
|
| /Documentation/power/ |
| D | swsusp-dmcrypt.rst | 2 How to use dm-crypt and swsusp together
10 You know how dm-crypt works. If not, visit the following web page:
11 http://www.saout.de/misc/dm-crypt/
13 You did read Documentation/admin-guide/initrd.rst and know how an initrd works.
16 Now your system is properly set up, your disk is encrypted except for
17 the swap device(s) and the boot partition which may contain a mini
26 up dm-crypt and then asks swsusp to resume from the encrypted
29 The most important thing is that you set up dm-crypt in such
33 to always set up this swap device first with dmsetup, so that
36 brw------- 1 root root 254, 0 Jul 28 13:37 /dev/mapper/swap0
[all …]
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | fsl,mxs-pinctrl.txt | 6 voltage and pull-up.
9 - compatible: "fsl,imx23-pinctrl" or "fsl,imx28-pinctrl"
10 - reg: Should contain the register physical address and length for the
13 Please refer to pinctrl-bindings.txt in this directory for details of the
20 information about pull-up. For this reason, even seemingly boolean values are
26 One is to set up a group of pins for a function, both mux selection and pin
34 particular function, like SSP0 functioning as mmc0-8bit. That said, the
37 "pinctrl-*" phandle in client device node should only have one group node
41 Required subnode-properties:
42 - fsl,pinmux-ids: An integer array. Each integer in the array specify a pin
[all …]
|
| /Documentation/arch/powerpc/ |
| D | kasan.txt | 1 KASAN is supported on powerpc on 32-bit and Radix 64-bit only.
6 KASAN is supported on both hash and nohash MMUs on 32-bit.
23 - It would be good to support inline instrumentation so as to be able to catch
26 - Inline instrumentation requires a fixed offset.
28 - Book3S runs code with translations off ("real mode") during boot, including a
29 lot of generic device-tree parsing code which is used to determine MMU
32 - Some code - most notably a lot of KVM code - also runs with translations off
33 after boot.
35 - Therefore any offset has to point to memory that is valid with
38 One approach is just to give up on inline instrumentation. This way boot-time
[all …]
|
| /Documentation/admin-guide/ |
| D | kernel-parameters.rst | 3 The kernel's command-line parameters
12 The kernel parses parameters from the kernel command line up to "``--``";
16 Everything after "``--``" is passed as an argument to init.
32 log_buf_len=1M print-fatal-signals=1
36 log-buf-len=1M print_fatal_signals=1
38 Double-quotes can be used to protect spaces in values, e.g.::
43 ----------
52 <cpu number>-<cpu number>
57 <cpu number>,...,<cpu number>-<cpu number>
63 <cpu number>-<cpu number>:<used size>/<group size>
[all …]
|
| D | verify-bugs-and-bisect-regressions.rst | 1 .. 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
23 up in the reference section, then jump back to where you left off.
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
51 * **Preparations**: set up everything to build your own kernels::
55 # * Ensure Secure Boot permits booting self-compiled Linux kernels.
[all …]
|
| D | README.rst | 11 --------------
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 …]
|
| /Documentation/core-api/ |
| D | boot-time-mm.rst | 2 Boot time memory management
6 simply because it is not set up yet. But there is still need to
11 boot time memory management. The architecture specific initialization
12 must set it up in :c:func:`setup_arch` and tear it down in
26 .. kernel-doc:: mm/memblock.c
39 .. kernel-doc:: include/linux/memblock.h
40 .. kernel-doc:: mm/memblock.c
|
| /Documentation/arch/x86/x86_64/ |
| D | boot-options.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 AMD64 Specific Boot Options
39 Do not opt-in to Local MCE delivery. Use legacy method
49 Disable boot machine check logging.
55 Don't overwrite the bios-set CMCI threshold. This boot option
62 Force-enable recoverable machine check code paths
73 Use IO-APIC. Default
76 Don't use the IO-APIC.
85 See Documentation/arch/x86/i386/IO-APIC.rst
88 Don't set up the APIC timer
[all …]
|
| /Documentation/admin-guide/blockdev/ |
| D | ramdisk.rst | 14 -----------
18 in order to access the root filesystem (see Documentation/admin-guide/initrd.rst). It can
26 The RAM disk supports up to 16 RAM disks by default, and can be reconfigured
41 ---------------------------------
48 This parameter tells the RAM disk driver to set up RAM disks of N k size. The
63 ---------------
66 to set the boot device in a Linux kernel image.
68 Instead of using rdev, just place the boot device information on the
72 arch/x86/boot/Makefile and specify in initrd image by setting FDINITRD in
73 arch/x86/boot/Makefile.
[all …]
|
| /Documentation/devicetree/bindings/mfd/ |
| D | rohm,bd71837-pmic.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/mfd/rohm,bd71837-pmic.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Matti Vaittinen <mazziesaccount@gmail.com>
13 BD71837MWV is programmable Power Management ICs for powering single-core,
14 dual-core, and quad-core SoCs such as NXP-i.MX 8M. It is optimized for low
18 …/www.rohm.com/products/power-management/power-management-ic-for-system/industrial-consumer-applica…
35 clock-names:
38 "#clock-cells":
[all …]
|
| D | rohm,bd71847-pmic.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/mfd/rohm,bd71847-pmic.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Matti Vaittinen <mazziesaccount@gmail.com>
14 single-core, dual-core, and quad-core SoCs such as NXP-i.MX 8M. It is
18 …/www.rohm.com/products/power-management/power-management-ic-for-system/industrial-consumer-applica…
19 …//www.rohm.com/products/power-management/power-management-ic-for-system/industrial-consumer-applic…
24 - rohm,bd71847
25 - rohm,bd71850
[all …]
|
| /Documentation/arch/riscv/ |
| D | boot-image-header.rst | 2 Boot image header in RISC-V Linux
8 This document only describes the boot image header details for RISC-V Linux.
10 The following 64-byte header is present in decompressed Linux kernel image::
25 ARM64 header. Thus, both ARM64 & RISC-V header can be combined into one common
31 - This header is also reused to support EFI stub for RISC-V. EFI specification
37 - version field indicate header version number
47 - The "magic" field is deprecated as of version 0.2. In a future
48 release, it may be removed. This originally should have matched up
50 The "magic2" field replaces it, matching up with the ARM64 header.
52 - In current header, the flags field has only one field.
[all …]
|
| /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 | earlyprintk.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 Mini-HOWTO for using the earlyprintk=dbgp boot option with a
13 [host/target] <-------> [USB debug key] <-------> [client/console]
21 the lspci -vvv output::
23 # lspci -vvv
25 …roller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03) (prog-if 20 [EHCI])
27 …Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisIN…
28 …Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- I…
31 Region 0: Memory at fe227000 (32-bit, non-prefetchable) [size=1K]
33 Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
[all …]
|
| /Documentation/ABI/stable/ |
| D | sysfs-bus-mhi | 6 using a BHI (Boot Host Interface) register read after at least
7 one attempt to power up the device has been done. If read
17 obtained using a BHI (Boot Host Interface) register read after
18 at least one attempt to power up the device has been done. If
28 a reset of last resort, and will require a complete re-init.
30 non-responsive, or as a means of loading new firmware as a
37 Description: Writing a non-zero value to this file will force devices to
|
| /Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,pbs.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Qualcomm Technologies, Inc. Programmable Boot Sequencer
10 - Anjelique Melendez <quic_amelende@quicinc.com>
13 The Qualcomm Technologies, Inc. Programmable Boot Sequencer (PBS)
14 supports triggering power up and power down sequences for clients
20 - enum:
21 - qcom,pmi632-pbs
22 - const: qcom,pbs
[all …]
|
| /Documentation/devicetree/bindings/regulator/ |
| D | regulator-max77620.txt | 3 Device has multiple DCDC(sd[0-3] and LDOs(ldo[0-8]). The input supply
6 sub-node "regulators" which is child node of device node.
14 -------------------
18 in-sd0-supply: Input supply for SD0, INA-SD0 or INB-SD0 pins.
19 in-sd1-supply: Input supply for SD1.
20 in-sd2-supply: Input supply for SD2.
21 in-sd3-supply: Input supply for SD3.
22 in-ldo0-1-supply: Input supply for LDO0 and LDO1.
23 in-ldo2-supply: Input supply for LDO2.
24 in-ldo3-5-supply: Input supply for LDO3 and LDO5
[all …]
|
| D | richtek,rtq6752-regulator.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/regulator/richtek,rtq6752-regulator.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - ChiYuan Huang <cy_huang@richtek.com>
15 buck-boost. The device is suitable for automotive TFT-LCD panel.
20 - richtek,rtq6752
25 enable-gpios:
28 external pull up.
45 - compatible
[all …]
|
| /Documentation/accounting/ |
| D | delay-accounting.rst | 9 The per-task delay accounting functionality measures
18 g) write-protect copy
40 ---------
44 generic data structure to userspace corresponding to per-pid and per-tgid
53 cache, direct compact, write-protect copy, IRQ/SOFTIRQ etc.
60 When a task exits, records containing the per-task statistics
62 task of a thread group, the per-tgid statistics are also sent. More details
70 -----
77 Delay accounting is disabled by default at boot up.
82 to the kernel boot options. The rest of the instructions below assume this has
[all …]
|
| /Documentation/scsi/ |
| D | sym53c8xx_2.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 SYM-2 driver
11 95170 DEUIL LA BARRE - FRANCE
15 2004-10-09
38 10. Boot setup commands
54 10.4 SCSI BUS checking boot option
67 This driver supports the whole SYM53C8XX family of PCI-SCSI controllers.
68 It also support the subset of LSI53C10XX PCI-SCSI controllers that are based
72 with the FreeBSD SYM-2 driver. The 'glue' that allows this driver to work
81 - Wolfgang Stanglmeier <wolf@cologne.de>
[all …]
|
| D | ncr53c8xx.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 95170 DEUIL LA BARRE - FRANCE
38 10. Boot setup commands
57 10.2.17 Fix up PCI configuration space
63 10.3 Advised boot setup commands
64 10.4 PCI configuration fix-up boot option
65 10.5 Serial NVRAM support boot option
66 10.6 SCSI BUS checking boot option
67 10.7 IMMEDIATE ARBITRATION boot option
81 16.1 Synchronous timings for 53C875 and 53C860 Ultra-SCSI controllers
[all …]
|
| D | ChangeLog.ncr53c8xx | 1 Sat May 12 12:00 2001 Gerard Roudier (groudier@club-internet.fr)
2 * version ncr53c8xx-3.4.3b
3 - Ensure LEDC bit in GPCNTL is cleared when reading the NVRAM.
4 Fix sent by Stig Telfer <stig@api-networks.com>.
5 - Define scsi_set_pci_device() as nil for kernel < 2.4.4.
7 Mon Feb 12 22:30 2001 Gerard Roudier (groudier@club-internet.fr)
8 * version ncr53c8xx-3.4.3
9 - Call pci_enable_device() as AC wants this to be done.
10 - Get both the BAR cookies actual and PCI BAR values.
12 - Merge changes for linux-2.4 that declare the host template
[all …]
|
| /Documentation/ABI/testing/ |
| D | pstore | 15 # mount -t pstore -o kmsg_bytes=8000 - /sys/fs/pstore
17 $ ls -l /sys/fs/pstore/
19 -r--r--r-- 1 root root 7896 Nov 30 15:38 dmesg-erst-1
24 - "dmesg" - saved console log
25 - "mce" - architecture dependent data from fatal h/w error
29 device that it can reclaim the space for later re-use::
31 $ rm /sys/fs/pstore/dmesg-erst-1
35 soon after boot to free up space ready for the next
47 boot time.
|
| D | sysfs-bus-platform-devices-occ-hwmon | 1 What: /sys/bus/platform/devices/occ-hwmon.X/ffdc
11 POWER9 and up processors over the Self-Boot Engine (SBE) FIFO.
|
12345678910>>...14