Searched +full:re +full:- +full:started (Results 1 – 25 of 88) sorted by relevance
1234
| /Documentation/arch/arm/sa1100/ |
| D | serial_uart.rst | 7 > Date: Sun, 24 Sep 2000 21:40:27 -0700
11 > Subject: Re: device
20 > 204 char Low-density serial ports
25 > 205 char Low-density serial ports (alternate device)
32 by your SA1100-based device::
44 you might have a getty process started on ttyS0.
48 - replace occurrences of ttyS0 with ttySA0, ttyS1 with ttySA1, etc.
50 - don't forget to add 'ttySA0', 'console', or the appropriate tty name
|
| /Documentation/virt/kvm/s390/ |
| D | s390-pv-dump.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 -------
27 ------------
52 time of the export does not matter as no re-encryption is
64 step completes successfully a new dump initiation can be started.
|
| D | s390-pv-boot.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 -------
13 Documentation/virt/kvm/s390/s390-pv.rst for details."
15 On IPL (boot) a small plaintext bootloader is started, which provides
33 -------
46 The new PV load-device-specific-parameters field specifies all data
52 * AES-XTS Tweak prefix
63 contain the guest content. All non-specified pages will start out as
73 non-clearing IPL subcodes are not allowed.
76 Re-IPL into a protected mode is only possible via a detour into non
[all …]
|
| /Documentation/process/ |
| D | management-style.rst | 8 mirror the :ref:`process/coding-style.rst <codingstyle>` document to some
14 to do with reality. It started as a lark, but that doesn't mean that it
20 budget of your group, you're almost certainly not a kernel manager.
35 ------------
37 Everybody thinks managers make decisions, and that decision-making is
44 to decide on this", you're in trouble as a manager. The people you
46 you for a technical decision, you're screwed. You're clearly not
50 you, you're also screwed, although for a totally different reason.
55 painful ones. Making small and non-consequential decisions is fine, and
56 makes you look like you know what you're doing, so what a kernel manager
[all …]
|
| /Documentation/driver-api/surface_aggregator/ |
| D | internal.rst | 1 .. SPDX-License-Identifier: GPL-2.0+
54 internal-api
63 Lower-level packet transport is implemented in the *packet transport layer
68 packet payloads to higher-level layers.
71 around command-type packet payloads, i.e. requests (sent from host to EC),
90 Refer to Documentation/driver-api/surface_aggregator/client.rst for
93 that chapter and the Documentation/driver-api/surface_aggregator/ssh.rst
104 -------
153 ------------
163 re-submitted to this queue due to timeouts or NAK packets sent by the EC.
[all …]
|
| /Documentation/livepatch/ |
| D | callbacks.rst | 5 Livepatch (un)patch-callbacks provide a mechanism for livepatch modules
10 - Safe updates to global data
12 - "Patches" to init and probe functions
14 - Patching otherwise unpatchable code (i.e. assembly)
25 - Module init/exit code doesn't run when disabling and re-enabling a
28 - A module notifier can't stop a to-be-patched module from loading.
39 * Pre-patch
40 - before a klp_object is patched
42 * Post-patch
43 - after a klp_object has been patched and is active
[all …]
|
| /Documentation/virt/kvm/x86/ |
| D | running-nested-guests.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 can be KVM-based or a different hypervisor). The straightforward
12 .----------------. .----------------.
17 |----------------'--'----------------|
22 .------------------------------------------------------.
25 |------------------------------------------------------|
27 '------------------------------------------------------'
31 - L0 – level-0; the bare metal host, running KVM
33 - L1 – level-1 guest; a VM running on L0; also called the "guest
36 - L2 – level-2 guest; a VM running on L1, this is the "nested guest"
[all …]
|
| /Documentation/staging/ |
| D | crc32.rst | 5 A CRC is a long-division remainder. You add the CRC to the message,
11 protocols put the end-of-frame flag after the CRC.
15 - We're working in binary, so the digits are only 0 and 1, and
16 - When dividing polynomials, there are no carries. Rather than add and
21 To produce a 32-bit CRC, the divisor is actually a 33-bit CRC polynomial.
23 CRC is written in hex with the most significant bit omitted. (If you're
24 familiar with the IEEE 754 floating-point format, it's the same idea.)
28 the best error-detecting properties, this should correspond to the
29 order they're actually sent. For example, standard RS-232 serial is
30 little-endian; the most significant bit (sometimes used for parity)
[all …]
|
| /Documentation/bpf/libbpf/ |
| D | libbpf_overview.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 libbpf is a C-based library containing a BPF loader that takes compiled BPF
13 The following are the high-level features supported by libbpf:
15 * Provides high-level and low-level APIs for user space programs to interact
16 with BPF programs. The low-level APIs wrap all the bpf system call
17 functionality, which is useful when users need more fine-grained control
22 * Provides BPF-side APIS, including BPF helper definitions, BPF maps support,
24 * Supports BPF CO-RE mechanism, enabling BPF developers to write portable
48 (setting BPF program types, if necessary; pre-setting initial values for
87 * ``<name>__attach()`` – attaches all auto-attachable BPF programs (it’s
[all …]
|
| /Documentation/virt/kvm/arm/ |
| D | pkvm.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 ------------
9 Protected KVM (pKVM) is a KVM/arm64 extension which uses the two-stage
12 without relying on whizz-bang features in hardware, but still allowing room for
13 complementary technologies such as memory encryption and hardware-backed
19 introduced to manage manipulation of guest stage-2 page tables, creation of VM
22 at stage-2, providing the hypervisor code with a mechanism to restrict host
26 -------------
29 "``kvm-arm.mode=protected``" on the command-line. Once enabled, VMs can be spawned
30 in either protected or non-protected state, although the hypervisor is still
[all …]
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | rohm,bd99954.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Matti Vaittinen <mazziesaccount@gmail.com>
11 - Markus Laine <markus.laine@fi.rohmeurope.com>
12 - Mikko Mutanen <mikko.mutanen@fi.rohmeurope.com>
15 The ROHM BD99954 is a Battery Management LSI for 1-4 cell Lithium-Ion
16 secondary battery intended to be used in space-constraint equipment such
18 provides a Dual-source Battery Charger, two port BC1.2 detection and a
21 $ref: power-supply.yaml#
[all …]
|
| /Documentation/driver-api/md/ |
| D | md-cluster.rst | 5 The cluster MD is a shared-device RAID for a cluster, it supports
9 1. On-disk format
12 Separate write-intent-bitmaps are used for each cluster node.
13 The bitmaps record all writes that may have been started on that node,
14 and may not yet have finished. The on-disk layout is::
17 -------------------------------------------------------------------
26 - set the appropriate bit (if not already set)
27 - commit the write to all mirrors
28 - schedule the bit to be cleared after a timeout.
41 -------------------------------------
[all …]
|
| /Documentation/admin-guide/ |
| D | bcache.rst | 11 This is the git repository of bcache-tools:
12 https://git.kernel.org/pub/scm/linux/kernel/git/colyli/bcache-tools.git/
17 It's designed around the performance characteristics of SSDs - it only allocates
25 great lengths to protect your data - it reliably handles unclean shutdown. (It
27 writes as completed until they're on stable storage).
29 Writeback caching can use most of the cache for buffering writes - writing
36 average is above the cutoff it will skip all IO from that task - instead of
46 Getting started:
47 You'll need bcache util from the bcache-tools repository. Both the cache device
50 bcache make -B /dev/sdb
[all …]
|
| D | md.rst | 5 ---------------------------------
49 -1 linear mode
58 (raid-0 and raid-1 only)
78 --------------------------------------
87 that all auto-detected arrays are assembled as partitionable.
90 -------------------------------------------
102 mdadm --assemble --force ....
108 arrays to be started.
112 md-mod.start_dirty_degraded=1
116 ------------------
[all …]
|
| /Documentation/admin-guide/pm/ |
| D | suspend-flows.rst | 1 .. SPDX-License-Identifier: GPL-2.0
12 At least one global system-wide transition needs to be carried out for the
14 :doc:`sleep states <sleep-states>`. Hibernation requires more than one
16 referred to as *system-wide suspend* (or simply *system suspend*) states, need
27 significant differences between the :ref:`suspend-to-idle <s2idle>` code flows
28 and the code flows related to the :ref:`suspend-to-RAM <s2ram>` and
31 The :ref:`suspend-to-RAM <s2ram>` and :ref:`standby <standby>` sleep states
33 boils down to the platform-specific actions carried out by the suspend and
37 *platform-dependent suspend* states in what follows.
42 Suspend-to-idle Suspend Code Flow
[all …]
|
| /Documentation/i2c/ |
| D | fault-codes.rst | 10 ----------------------------------
14 some cases, such as re-initializing (and maybe resetting). After such
27 -------------------------
29 some positive number indicating a non-fault return. The specific
31 though most Linux systems use <asm-generic/errno*.h> numbering.
72 detected before any I/O operation was started. Use a more
119 or SMBus (or chip-specific) protocol specifications. One
121 (from the SMBus slave) is outside the range 1-32 bytes.
|
| /Documentation/userspace-api/media/v4l/ |
| D | userp.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
21 data are exchanged, these pointers and meta-information are passed in
23 :c:type:`v4l2_plane` in the multi-planar API case). The
33 .. code-block:: c
41 if (ioctl (fd, VIDIOC_REQBUFS, &reqbuf) == -1) {
74 application waits until a filled buffer can be dequeued, and re-enqueues
77 started. In the write loop, when the application runs out of free
85 <func-select>` or :c:func:`poll()` function are always
109 Anyway, the process of swapping, locking or generating scatter-gather
|
| D | dmabuf.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
30 devices, which may be V4L devices or other video-related devices (e.g.
34 such file descriptor are exchanged. The descriptors and meta-information
36 :c:type:`v4l2_plane` in the multi-planar API case). The
43 .. code-block:: c
52 if (ioctl(fd, VIDIOC_REQBUFS, &reqbuf) == -1) {
70 .. code-block:: c
82 if (ioctl(v4lfd, VIDIOC_QBUF, &buf) == -1) {
84 return -1;
93 .. code-block:: c
[all …]
|
| /Documentation/driver-api/dmaengine/ |
| D | dmatest.rst | 21 capability of the following: DMA_MEMCPY (memory-to-memory), DMA_MEMSET
22 (const-to-memory or memory-to-memory, when emulated), DMA_XOR, DMA_PQ.
28 Part 1 - How to build the test module
33 Device Drivers -> DMA Engine support -> DMA Test client
38 Part 2 - When dmatest is built as a module
57 Example of multi-channel test usage (new in the 5.0 kernel)::
68 For all tests, starting in the 5.0 kernel, either single- or multi-channel,
80 % ls -1 /sys/class/dma/
82 Once started a message like " dmatest: Added 1 threads using dma0chan0" is
84 pending thread is started once run is to 1.
[all …]
|
| /Documentation/rust/ |
| D | quick-start.rst | 1 .. SPDX-License-Identifier: GPL-2.0
6 This document describes how to get started with kernel development in Rust.
10 suitable -- the first section below explains this approach. An advantage of this
24 The rest of the document explains other aspects on how to get started.
28 -------------
36 pacman -S rust rust-src rust-bindgen
45 apt install rustc rust-src bindgen rustfmt rust-clippy
54 dnf install rust rust-src bindgen-cli rustfmt clippy
63 USE='rust-src rustfmt clippy' emerge dev-lang/rust dev-util/bindgen
76 nativeBuildInputs = with pkgs; [ rustc rust-bindgen rustfmt clippy ];
[all …]
|
| /Documentation/RCU/ |
| D | torture.rst | 1 .. SPDX-License-Identifier: GPL-2.0
15 command (perhaps grepping for "torture"). The test is started
19 Documentation/admin-guide/kernel-parameters.txt.
26 …rcu-torture:--- Start of test: nreaders=16 nfakewriters=4 stat_interval=30 verbose=0 test_no_idle_…
27 …rcu-torture: rtc: (null) ver: 155441 tfle: 0 rta: 155441 rtaf: 8884 rtf: 155440 rtmbe: 0…
28 rcu-torture: Reader Pipe: 727860534 34213 0 0 0 0 0 0 0 0 0
29 rcu-torture: Reader Batch: 727877838 17003 0 0 0 0 0 0 0 0 0
30 …rcu-torture: Free-Block Circulation: 155440 155440 155440 155440 155440 155440 155440 155440 1554…
31 …rcu-torture:--- End of test: SUCCESS: nreaders=16 nfakewriters=4 stat_interval=30 verbose=0 test_n…
37 be evident. ;-)
[all …]
|
| /Documentation/driver-api/virtio/ |
| D | writing_virtio_drivers.rst | 1 .. SPDX-License-Identifier: GPL-2.0
39 struct virtio_dummy_dev *dev = vq->vdev->priv;
43 while ((buf = virtqueue_get_buf(dev->vq, &len)) != NULL) {
55 return -ENOMEM;
58 dev->vq = virtio_find_single_vq(vdev, virtio_dummy_recv_cb, "input");
59 if (IS_ERR(dev->vq)) {
61 return PTR_ERR(dev->vq);
64 vdev->priv = dev;
74 struct virtio_dummy_dev *dev = vdev->priv;
78 * vdev->config->reset(vdev)
[all …]
|
| /Documentation/sound/soc/ |
| D | dpcm.rst | 18 DPCM re-uses all the existing component codec, platform and DAI drivers without
23 -------------------------------------
26 document for all examples :-
32 PCM0 <------------> * * <----DAI0-----> Codec Headset
34 PCM1 <------------> * * <----DAI1-----> Codec Speakers
36 PCM2 <------------> * * <----DAI2-----> MODEM
38 PCM3 <------------> * * <----DAI3-----> BT
40 * * <----DAI4-----> DMIC
42 * * <----DAI5-----> FM
53 Example - DPCM Switching playback from DAI0 to DAI1
[all …]
|
| /Documentation/arch/s390/ |
| D | 3270.rst | 17 Linux/390. A 3270 device is a block-mode rows-and-columns terminal of
21 You may have 3270s in-house and not know it. If you're using the
22 VM-ESA operating system, define a 3270 to your virtual machine by using
23 the command "DEF GRAF <hex-address>" This paper presumes you will be
26 - DEF GRAF 620
27 - DEF GRAF 621
28 - DEF GRAF 622
29 - DEF GRAF 623
31 Your network connection from VM-ESA allows you to use x3270, tn3270, or
32 another 3270 emulator, started from an xterm window on your PC or
[all …]
|
| /Documentation/driver-api/ |
| D | device_link.rst | 31 supplier is bound to a driver, and they're unbound before the supplier
57 device ``->probe`` callback or a boot-time PCI quirk.
61 ``->probe`` callback while the supplier hasn't started to probe yet: Had the
65 non-presence. [Note that it is valid to create a link from the consumer's
66 ``->probe`` callback while the supplier is still probing, but the consumer must
72 is added in the ``->probe`` callback of the supplier or consumer driver, it is
73 typically deleted in its ``->remove`` callback for symmetry. That way, if the
87 link is added from the consumer's ``->probe`` callback: ``DL_FLAG_RPM_ACTIVE``
93 Similarly, when the device link is added from supplier's ``->probe`` callback,
125 :c:func:`device_link_add()` may cause the PM-runtime usage counter of the
[all …]
|
1234