Searched +full:right +full:- +full:most (Results 1 – 25 of 210) sorted by relevance
123456789
| /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 …]
|
| /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 …]
|
| D | 4.Coding.rst | 3 Getting the code right
6 While there is much to be said for a solid and community-oriented design
14 will shift toward doing things right and the tools which can help in that
19 ---------
25 :ref:`Documentation/process/coding-style.rst <codingstyle>`. For much of
26 that time, the policies described in that file were taken as being, at most,
38 strangely-formatted code.
43 giving up a degree of control in a number of ways - including control over
49 as a way of getting their name into the kernel changelogs - or both. But
59 80-column limit, for example), just do it.
[all …]
|
| D | management-style.rst | 8 mirror the :ref:`process/coding-style.rst <codingstyle>` document to some
35 ------------
37 Everybody thinks managers make decisions, and that decision-making is
55 painful ones. Making small and non-consequential decisions is fine, and
65 **two** inconsequential decisions - the wrong one **and** the right one.
72 you cannot escape. A cornered rat may be dangerous - a cornered manager
80 back-tracking is very easy: just tell everybody that you were an
89 - admitting you were an idiot is harder than it looks. We all like to
92 - having somebody tell you that what you worked on for the last year
101 admitting up-front that you don't have a friggin' clue, and telling
[all …]
|
| D | 5.Posting.rst | 13 :ref:`Documentation/process/submitting-patches.rst <submittingpatches>`
14 and :ref:`Documentation/process/submit-checklist.rst <submitchecklist>`.
18 ------------
24 consider posting in-progress work, or even making a git tree available so
30 patches which are known to be half-baked, but those who do will come in
31 with the idea that they can help you drive the work in the right direction.
35 -----------------------
40 - Test the code to the extent that you can. Make use of the kernel's
42 combinations of configuration options, use cross-compilers to build for
45 - Make sure your code is compliant with the kernel coding style
[all …]
|
| D | 3.Early-stage.rst | 3 Early-stage planning
7 to jump right in and start coding. As with any significant project,
14 ----------------------
28 the linux-kernel mailing list, where it immediately ran into problems.
52 more concerned about system stability, long-term maintenance, and finding
53 the right solution to the problem than they were with a specific module.
54 The moral of the story is to focus on the problem - not a specific solution
55 - and to discuss it with the development community before investing in the
61 - What, exactly, is the problem which needs to be solved?
63 - Who are the users affected by this problem? Which use cases should the
[all …]
|
| /Documentation/arch/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 …]
|
| D | entry_64.rst | 1 .. SPDX-License-Identifier: GPL-2.0
14 kernel code. Most of these entry points are registered in
16 for 64-bit, arch/x86/entry/entry_32.S for 32-bit and finally
17 arch/x86/entry/entry_64_compat.S which implements the 32-bit compatibility
18 syscall entry points and thus provides for 32-bit processes the
19 ability to execute syscalls when running on 64-bit kernels.
25 - system_call: syscall instruction from 64-bit code.
27 - entry_INT80_compat: int 0x80 from 32-bit or 64-bit code; compat syscall
30 - entry_INT80_compat, ia32_sysenter: syscall and sysenter from 32-bit
33 - interrupt: An array of entries. Every IDT vector that doesn't
[all …]
|
| /Documentation/arch/arm/google/ |
| D | chromebook-boot-flow.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 Most recent Chromebooks that use device tree are using the opensource
10 is up to depthcharge_ to pick the right device tree from the `FIT Image`_ and
16 - Board name, specified at depthcharge_ compile time. This is $(BOARD) below.
17 - Board revision number, determined at runtime (perhaps by reading GPIO
19 - SKU number, read from GPIO strappings at boot time. This is $(SKU) below.
23 - google,$(BOARD)-rev$(REV)-sku$(SKU)
24 - google,$(BOARD)-rev$(REV)
25 - google,$(BOARD)-sku$(SKU)
26 - google,$(BOARD)
[all …]
|
| /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 …]
|
| /Documentation/filesystems/iomap/ |
| D | porting.rst | 1 .. SPDX-License-Identifier: GPL-2.0
27 This worked well enough for direct/indirect-mapped filesystems such
28 as ext2, but is very inefficient for extent-based filesystems such
34 3. Direct access to storage on memory-like devices (fsdax) is only
40 No ->write_begin(), ->write_end() or direct_IO
49 Build the kernel, run fstests with the ``-g all`` option across a wide
53 The recommended approach is first to implement ``->iomap_begin`` (and
54 ``->iomap_end`` if necessary) to allow iomap to obtain a read-only
56 In most cases, this is a relatively trivial conversion of the existing
57 ``get_block()`` function for read-only mappings.
[all …]
|
| /Documentation/driver-api/media/ |
| D | v4l2-intro.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 ------------
7 hardware: most devices have multiple ICs, export multiple device nodes in
8 /dev, and create also non-V4L2 devices such as DVB, ALSA, FB, I2C and input
12 do audio/video muxing/encoding/decoding makes it more complex than most.
15 called 'sub-devices'.
22 connecting to sub-devices themselves. Some of this is quite complicated
23 to do right and many drivers never did do it correctly.
32 A good example to look at as a reference is the v4l2-pci-skeleton.c
38 -------------------------
[all …]
|
| D | rc-core.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 -------------------------
13 Also, on most hardware, keeping a key pressed for more than a few dozens of
23 infrared-based remote controllers, there's no key release event. Instead,
26 However, most of the remote controllers use infrared (IR) to transmit signals.
48 At receiver, a simple low-pass filter can be used to convert the received
64 without any receivers. Right now, all such devices work only in
78 The Kernel has support for mapping tables available on most media
86 .. kernel-doc:: include/media/rc-core.h
88 .. kernel-doc:: include/media/rc-map.h
|
| /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 …]
|
| /Documentation/devicetree/bindings/input/ |
| D | adc-joystick.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
2 # Copyright 2019-2020 Artur Rojek
4 ---
5 $id: http://devicetree.org/schemas/input/adc-joystick.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Artur Rojek <contact@artur-rojek.eu>
18 - $ref: input.yaml#
22 const: adc-joystick
24 io-channels:
31 https://github.com/devicetree-org/dt-schema/blob/master/schemas/iio/iio-consumer.yaml
[all …]
|
| /Documentation/timers/ |
| D | timers-howto.rst | 2 delays - Information on the various kernel delay / sleep mechanisms
8 This question is most often faced by driver writers who have to
9 deal with hardware delays and who may not be the most intimately
14 ----------------
16 The first, and most important, question you need to ask is "Is my
30 udelay is the generally preferred API; ndelay-level
31 precision may not actually exist on many non-PC devices.
38 NON-ATOMIC CONTEXT:
41 work correctly, using the "right" sleep function will
45 -- Backed by busy-wait loop:
[all …]
|
| /Documentation/driver-api/usb/ |
| D | dma.rst | 11 The big picture is that USB drivers can continue to ignore most DMA issues,
12 though they still must provide DMA-ready buffers (see
13 Documentation/core-api/dma-api-howto.rst). That's how they've worked through
14 the 2.4 (and earlier) kernels, or they can now be DMA-aware.
16 DMA-aware usb drivers:
18 - New calls enable DMA-aware drivers, letting them allocate dma buffers and
19 manage dma mappings for existing dma-ready buffers (see below).
21 - URBs have an additional "transfer_dma" field, as well as a transfer_flags
25 - "usbcore" will map this DMA address, if a DMA-aware driver didn't do
29 - There's a new "generic DMA API", parts of which are usable by USB device
[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.
21 KASAN support on Book3S is a bit tricky to get right:
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
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/sound/hd-audio/ |
| D | realtek-pc-beep.rst | 20 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
24 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
37 Amplify 1Ah loopback, right (R): 1 bit
38 Amplify the right channel of 1Ah before mixing it into outputs as specified
58 +--DIV--+--!DIV--+ {1Ah boost control}
60 +--(b == 0)--+--(b != 0)--+
70 +-----!h-----+-----S-----+
79 All Realtek HDA codecs have a vendor-defined widget with node ID 20h which
87 Realtek, is of note: unlike most registers, which seem to control detailed
111 Linux, it seems, has gone through most of them. For one, the register resets
[all …]
|
| /Documentation/i2c/ |
| D | fault-codes.rst | 5 This is a summary of the most important conventions for use of fault
10 ----------------------------------
14 some cases, such as re-initializing (and maybe resetting). After such
23 the right fault code, so that it can (in turn) behave correctly.
27 -------------------------
28 These are returned as negative numbers from most calls, with zero or
29 some positive number indicating a non-fault return. The specific
31 though most Linux systems use <asm-generic/errno*.h> numbering.
119 or SMBus (or chip-specific) protocol specifications. One
121 (from the SMBus slave) is outside the range 1-32 bytes.
|
| /Documentation/filesystems/ |
| D | dlmfs.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 dlmfs is built with OCFS2 as it requires most of its infrastructure.
14 :Tools web page: https://github.com/markfasheh/ocfs2-tools
29 - Right now it only works with the OCFS2 DLM, though support for other
48 place. Please download ocfs2-tools from the above url and configure a
53 ocfs2_hb_ctl (distributed with ocfs2-tools). Right now it requires
59 with ocfs2-tools.
68 'libo2dlm' (distributed with ocfs2-tools) which abstracts the file
76 Two levels of locks are supported - Shared Read, and Exclusive.
80 distributed with ocfs2-tools.
[all …]
|
| /Documentation/sound/cards/ |
| D | bt87x.rst | 19 does audio. snd-bt87x is a driver for the second function. It's a sound
21 playback). As most TV cards come with a short cable which can be plugged
22 into your sound card's line-in you probably don't need this driver if all
40 recorded data is not right, try to specify the ``digital_rate`` option with
44 <alsa-devel@alsa-project.org>, regardless of whether audio capture works
51 The chip knows two different modes (digital/analog). snd-bt87x
|
| /Documentation/filesystems/bcachefs/ |
| D | CodingStyle.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 Things don't always have to be perfect - nitpicking often does more harm than
12 good. But appreciate beauty when you see it - and let people know.
14 The code that you are afraid to touch is the code most in need of refactoring.
23 Assertions are one of our most important tools for writing reliable code. If in
26 you're not sure if it can happen and not sure how to handle it yet - make it a
33 expensive - but don't turn everything into a debug mode assertion, so that
52 elide - if we were working in a language with embedded correctness proofs that
56 invariants with runtime checks - much like the way people working in
60 Looking for ways to make your assertions simpler - and higher level - will
[all …]
|
| /Documentation/input/devices/ |
| D | joystick-parport.rst | 3 .. _joystick-parport:
9 :Copyright: |copy| 1998-2000 Vojtech Pavlik <vojtech@ucw.cz>
10 :Copyright: |copy| 1998 Andree Borrmann <a.borrmann@tu-bs.de>
18 Any information in this file is provided as-is, without any guarantee that
28 that, PCs usually lack the right ports to connect these devices to. Parallel
30 both output and input bits is the most suitable port on the PC for
36 Many console and 8-bit computer gamepads and joysticks are supported. The
40 ------------
59 for your pads, use either keyboard or joystick port, and make a pass-through
64 some data pin. For most gamepad and parport implementations only one pin is
[all …]
|
123456789