| /kernel/linux/linux-4.19/Documentation/input/ |
| D | gamepad.rst | 1 ---------------------------
3 ---------------------------
11 having user-space deal with different button-mappings for each gamepad, this
25 | <===DP===> |SE| |ST| (W) -|- (E) | |
35 D-Pad Left Right Action Pad
41 Most gamepads have the following features:
43 - Action-Pad
44 4 buttons in diamonds-shape (on the right side). The buttons are
45 differently labeled on most devices so we define them as NORTH,
47 - D-Pad (Direction-pad)
[all …]
|
| /kernel/linux/linux-5.10/Documentation/input/ |
| D | gamepad.rst | 1 ---------------------------
3 ---------------------------
11 having user-space deal with different button-mappings for each gamepad, this
25 | <===DP===> |SE| |ST| (W) -|- (E) | |
35 D-Pad Left Right Action Pad
41 Most gamepads have the following features:
43 - Action-Pad
44 4 buttons in diamonds-shape (on the right side). The buttons are
45 differently labeled on most devices so we define them as NORTH,
47 - D-Pad (Direction-pad)
[all …]
|
| /kernel/linux/linux-4.19/Documentation/ioctl/ |
| D | botching-up-ioctls.txt | 4 From: http://blog.ffwll.ch/2013/11/botching-up-ioctls.html
12 Which is nice, since there's no more insanity in the form of fake-generic, but
17 lessons learned while botching the job for the drm/i915 driver. Most of these
18 only cover technicalities and not the big-picture issues like what the command
24 -------------
27 will need to add a 32-bit compat layer:
32 * Align everything to the natural size and use explicit padding. 32-bit
33 platforms don't necessarily align 64-bit values to 64-bit boundaries, but
34 64-bit platforms do. So we always need padding to the natural size to get
35 this right.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | botching-up-ioctls.rst | 5 From: https://blog.ffwll.ch/2013/11/botching-up-ioctls.html
13 Which is nice, since there's no more insanity in the form of fake-generic, but
18 lessons learned while botching the job for the drm/i915 driver. Most of these
19 only cover technicalities and not the big-picture issues like what the command
25 -------------
28 will need to add a 32-bit compat layer:
33 * Align everything to the natural size and use explicit padding. 32-bit
34 platforms don't necessarily align 64-bit values to 64-bit boundaries, but
35 64-bit platforms do. So we always need padding to the natural size to get
36 this right.
[all …]
|
| D | applying-patches.rst | 11 This document is obsolete. In most cases, rather than using ``patch``
54 in the patch file when applying it (the ``-p1`` argument to ``patch`` does
57 To revert a previously applied patch, use the -R argument to patch.
60 patch -p1 < ../patch-x.y.z
64 patch -R -p1 < ../patch-x.y.z
76 patch -p1 < path/to/patch-x.y.z
82 Patch can also get the name of the file to use via the -i argument, like
85 patch -p1 -i path/to/patch-x.y.z
91 xzcat path/to/patch-x.y.z.xz | patch -p1
92 bzcat path/to/patch-x.y.z.gz | patch -p1
[all …]
|
| /kernel/linux/linux-4.19/Documentation/x86/ |
| D | kernel-stacks | 1 Kernel stacks on x86-64 bit
2 ---------------------------
4 Most of the text from Keith Owens, hacked by AK
31 per CPU interrupt nest counter. This is needed because x86-64 "IST"
42 An IST is selected by a non-zero value in the IST field of an
43 interrupt-gate descriptor. When an interrupt occurs and the hardware
47 will switch back to the per-thread stack. If software wants to allow
56 IST events with the same code to be nested. However in most cases, the
60 The currently assigned IST stacks are :-
64 Used for interrupt 8 - Double Fault Exception (#DF).
[all …]
|
| /kernel/linux/linux-5.10/Documentation/x86/ |
| D | kernel-stacks.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 Kernel stacks on x86-64 bit
10 Most of the text from Keith Owens, hacked by AK
37 per CPU interrupt nest counter. This is needed because x86-64 "IST"
48 An IST is selected by a non-zero value in the IST field of an
49 interrupt-gate descriptor. When an interrupt occurs and the hardware
53 will switch back to the per-thread stack. If software wants to allow
62 IST events with the same code to be nested. However in most cases, the
70 Used for interrupt 8 - Double Fault Exception (#DF).
79 Used for non-maskable interrupts (NMI).
[all …]
|
| /kernel/linux/linux-4.19/arch/ia64/include/asm/uv/ |
| D | uv_hub.h | 23 * M - The low M bits of a physical address represent the offset
28 * N - Number of bits in the node portion of a socket physical
31 * NASID - network ID of a router, Mbrick or Cbrick. Nasid values of
33 * equal to 0. Most addressing macros that target UV hub chips
34 * right shift the NASID by 1 to exclude the always-zero bit.
37 * GNODE - NASID right shifted by 1 bit. Most mmrs contain gnodes instead
40 * PNODE - the low N bits of the GNODE. The PNODE is the most useful variant
45 * +--------------------------------+---------------------+
47 * +--------------------------------+---------------------+
48 * |<-------53 - M bits --->|<--------M bits ----->
[all …]
|
| /kernel/linux/linux-5.10/arch/ia64/include/asm/uv/ |
| D | uv_hub.h | 23 * M - The low M bits of a physical address represent the offset
28 * N - Number of bits in the node portion of a socket physical
31 * NASID - network ID of a router, Mbrick or Cbrick. Nasid values of
33 * equal to 0. Most addressing macros that target UV hub chips
34 * right shift the NASID by 1 to exclude the always-zero bit.
37 * GNODE - NASID right shifted by 1 bit. Most mmrs contain gnodes instead
40 * PNODE - the low N bits of the GNODE. The PNODE is the most useful variant
45 * +--------------------------------+---------------------+
47 * +--------------------------------+---------------------+
48 * |<-------53 - M bits --->|<--------M bits ----->
[all …]
|
| /kernel/linux/linux-4.19/fs/reiserfs/ |
| D | README | 21 a check in the mail to you (for non-trivial improvements) when he
25 right to decline to allow him to license your code contribution other
56 distributors wanting them out of sync.:-) Please try to remember to
64 recompile your kernel, most of the time. The errors you get will be
73 the software component development power of the internet. Be the most
92 to work the way he did, he is one of the most selfless men I know.
94 Yura helps with benchmarking, coding hashes, and block pre-allocation
131 Chris Mason dived right into our code, and in just a few months produced
148 Jeff Mahoney, of SuSE, contributed a few cleanup fixes, most notably
|
| /kernel/linux/linux-5.10/fs/reiserfs/ |
| D | README | 21 a check in the mail to you (for non-trivial improvements) when he
25 right to decline to allow him to license your code contribution other
56 distributors wanting them out of sync.:-) Please try to remember to
64 recompile your kernel, most of the time. The errors you get will be
73 the software component development power of the internet. Be the most
92 to work the way he did, he is one of the most selfless men I know.
94 Yura helps with benchmarking, coding hashes, and block pre-allocation
131 Chris Mason dived right into our code, and in just a few months produced
148 Jeff Mahoney, of SuSE, contributed a few cleanup fixes, most notably
|
| /kernel/linux/linux-5.10/Documentation/maintainer/ |
| D | rebasing-and-merging.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 Git source-code management system. Git is a powerful tool with a lot of
9 features; as is often the case with such tools, there are right and wrong
30 - Changing the parent (starting) commit upon which a series of patches is
36 - Changing the history of a set of patches by fixing (or deleting) broken
48 - History that has been exposed to the world beyond your private system
54 That said, there are always exceptions. Some trees (linux-next being
61 - Do not rebase a branch that contains history created by others. If you
67 - Do not reparent a tree without a good reason to do so. Just being on a
71 - If you must reparent a repository, do not pick some random kernel commit
[all …]
|
| /kernel/linux/linux-4.19/drivers/mtd/devices/ |
| D | Kconfig | 1 menu "Self-contained MTD device drivers"
11 These devices come in memory configurations from 32M - 1G. If you
40 tristate "DEC MS02-NV NVRAM module support"
43 This is an MTD driver for the DEC's MS02-NV (54-20948-01) battery
44 backed-up NVRAM module. The module was originally meant as an NFS
51 The module will be called ms02-nv.
58 Sometimes DataFlash chips are packaged inside MMC-format
76 one-time-programmable (OTP) data. The first half may be written
79 unique-to-each-chip bit pattern at the factory.
82 tristate "Support most SPI Flash chips (AT26DF, M25P, W25X, ...)"
[all …]
|
| /kernel/linux/linux-5.10/include/uapi/linux/ |
| D | falloc.h | 1 /* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
6 #define FALLOC_FL_PUNCH_HOLE 0x02 /* de-allocates range */
20 * granularity of the operation. Most will limit operations to
26 * considered an illegal operation - just use ftruncate(2) if you need
35 * unwritten extents - even though file system may choose to zero out the
48 * shifted towards right by len bytes to create a hole. As such, this
52 * of the operation. Most will limit operations to filesystem block size
57 * the file is considered an illegal operation - just use ftruncate(2) or
66 * copy-on-write.
69 * granularity of the operation. Most will limit operations to filesystem
[all …]
|
| /kernel/linux/linux-4.19/include/uapi/linux/ |
| D | falloc.h | 1 /* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
6 #define FALLOC_FL_PUNCH_HOLE 0x02 /* de-allocates range */
20 * granularity of the operation. Most will limit operations to
26 * considered an illegal operation - just use ftruncate(2) if you need
35 * unwritten extents - even though file system may choose to zero out the
48 * shifted towards right by len bytes to create a hole. As such, this
52 * of the operation. Most will limit operations to filesystem block size
57 * the file is considered an illegal operation - just use ftruncate(2) or
66 * copy-on-write.
69 * granularity of the operation. Most will limit operations to filesystem
[all …]
|
| /kernel/linux/linux-4.19/Documentation/process/ |
| D | applying-patches.rst | 11 This document is obsolete. In most cases, rather than using ``patch``
54 in the patch file when applying it (the ``-p1`` argument to ``patch`` does
57 To revert a previously applied patch, use the -R argument to patch.
60 patch -p1 < ../patch-x.y.z
64 patch -R -p1 < ../patch-x.y.z
76 patch -p1 < path/to/patch-x.y.z
82 Patch can also get the name of the file to use via the -i argument, like
85 patch -p1 -i path/to/patch-x.y.z
91 xzcat path/to/patch-x.y.z.xz | patch -p1
92 bzcat path/to/patch-x.y.z.gz | patch -p1
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/media/drivers/ |
| D | pvrusb2.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 ----------
13 Its history started with the reverse-engineering effort by Björn
29 1. Low level wire-protocol implementation with the device.
38 tear-down, arbitration, and interaction with high level
45 The most important shearing layer is between the top 2 layers. A
54 right now the V4L high level interface is the most complete, the
56 functions, and there's no reason I see right now why it shouldn't be
57 possible to produce a DVB high level interface that can sit right
61 --------
[all …]
|
| /kernel/linux/linux-4.19/Documentation/media/v4l-drivers/ |
| D | pvrusb2.rst | 7 ----------
11 Its history started with the reverse-engineering effort by Björn
27 1. Low level wire-protocol implementation with the device.
36 tear-down, arbitration, and interaction with high level
43 The most important shearing layer is between the top 2 layers. A
52 right now the V4L high level interface is the most complete, the
54 functions, and there's no reason I see right now why it shouldn't be
55 possible to produce a DVB high level interface that can sit right
59 --------
68 --------------------------------------
[all …]
|
| /kernel/linux/linux-5.10/tools/testing/selftests/kvm/lib/ |
| D | sparsebit.c | 1 // SPDX-License-Identifier: GPL-2.0-only
27 * sparsebit_alloc() and most also take a bit index. Frequently
30 * ---- Query Operations
37 * ---- Modifying Operations
67 * For the most part the internal implementation of sparsebit is
72 * set. It is also efficient in memory usage when most of the bits are
75 * At a high-level the state of the bit settings are maintained through
76 * the use of a binary-search tree, where each node contains at least
87 * node, while the mask member stores the setting of the first 32-bits.
99 * represent cases where most bits are set. For example, the case of all
[all …]
|
| /kernel/linux/linux-4.19/tools/testing/selftests/kvm/lib/ |
| D | sparsebit.c | 28 * sparsebit_alloc() and most also take a bit index. Frequently
31 * ---- Query Operations
38 * ---- Modifying Operations
68 * For the most part the internal implementation of sparsebit is
73 * set. It is also efficient in memory usage when most of the bits are
76 * At a high-level the state of the bit settings are maintained through
77 * the use of a binary-search tree, where each node contains at least
88 * node, while the mask member stores the setting of the first 32-bits.
100 * represent cases where most bits are set. For example, the case of all
103 * node 0 - idx: 0x0 mask: 0xffffffff num_after: 0xffffffffffffffc0
[all …]
|
| /kernel/linux/linux-5.10/net/wimax/ |
| D | wimax-internal.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
6 * Copyright (C) 2007 Intel Corporation <linux-wimax@intel.com>
7 * Inaky Perez-Gonzalez <inaky.perez-gonzalez@intel.com>
32 * (wimax_dev->mutex). As well, most operations need to call this
33 * function to check if the state is the right one.
35 * An error value will be returned if the state is not the right
42 if (wimax_dev->state == __WIMAX_ST_NULL) in wimax_dev_is_ready()
43 return -EINVAL; /* Device is not even registered! */ in wimax_dev_is_ready()
44 if (wimax_dev->state == WIMAX_ST_DOWN) in wimax_dev_is_ready()
45 return -ENOMEDIUM; in wimax_dev_is_ready()
[all …]
|
| /kernel/linux/linux-4.19/drivers/media/rc/keymaps/ |
| D | rc-kworld-plus-tv-analog.c | 1 // SPDX-License-Identifier: GPL-2.0+
2 // kworld-plus-tv-analog.h - Keytable for kworld_plus_tv_analog Remote Controller
4 // keymap imported from ir-keymaps.c
8 #include <media/rc-map.h>
17 { 0x16, KEY_CLOSECD }, /* -> ) */
23 { 0x03, KEY_4 }, /* Two keys have the same code: 3 and right */
41 /* Couldn't map key left/key right since those
51 Most of them conflict with digits.
|
| /kernel/linux/linux-5.10/drivers/media/rc/keymaps/ |
| D | rc-kworld-plus-tv-analog.c | 1 // SPDX-License-Identifier: GPL-2.0+
2 // kworld-plus-tv-analog.h - Keytable for kworld_plus_tv_analog Remote Controller
4 // keymap imported from ir-keymaps.c
8 #include <media/rc-map.h>
17 { 0x16, KEY_CLOSECD }, /* -> ) */
26 /* Two keys have the same code: 4 and right */
45 /* Couldn't map key left/key right since those
55 Most of them conflict with digits.
|
| /kernel/linux/linux-4.19/Documentation/media/kapi/ |
| D | v4l2-intro.rst | 2 ------------
5 hardware: most devices have multiple ICs, export multiple device nodes in
6 /dev, and create also non-V4L2 devices such as DVB, ALSA, FB, I2C and input
10 do audio/video muxing/encoding/decoding makes it more complex than most.
13 called 'sub-devices'.
20 connecting to sub-devices themselves. Some of this is quite complicated
21 to do right and many drivers never did do it correctly.
30 A good example to look at as a reference is the v4l2-pci-skeleton.c
36 -------------------------
42 2) A way of initializing and commanding sub-devices (if any).
[all …]
|
| /kernel/linux/linux-5.10/lib/ |
| D | btree.c | 1 // SPDX-License-Identifier: GPL-2.0-only
3 * lib/btree.c - Simple In-memory B+Tree
5 * Copyright (c) 2007-2008 Joern Engel <joern@purestorage.com>
9 * see http://programming.kicks-ass.net/kernel-patches/vma_lookup/btree.patch
27 * ~98% pointers - hard to beat. Very sparse radix trees contain only ~2%
35 * values are to the right, not to the left. All used slots within a node
36 * are on the left, all unused slots contain NUL values. Most operations
97 node = mempool_alloc(head->mempool, gfp); in btree_node_alloc()
109 return -1; in longcmp()
140 for (i = geo->keylen - 1; i >= 0; i--) { in dec_key()
[all …]
|