/openbmc/linux/Documentation/input/ |
H A 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 …]
|
/openbmc/linux/Documentation/process/ |
H A 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 …]
|
H A 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 …]
|
H A 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 …]
|
/openbmc/linux/Documentation/arch/x86/ |
H A 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 …]
|
/openbmc/openbmc/poky/bitbake/lib/toaster/tests/functional/ |
H A D | test_project_page_tab_config.py | 4 # Copyright (C) 2023 Savoir-faire Linux 6 # SPDX-License-Identifier: GPL-2.0-only 31 self.wait_until_visible('#config-nav') 35 search_box = self.find('#build-input') 37 self.find('#build-button').click() 38 self.wait_until_present('#latest-builds') 43 '//div[@id="latest-builds"]/div', 53 '//span[@class="cancel-build-btn pull-right alert-link"]', 65 '//div[@id="project-topbar"]//li' 69 config_nav = self.find('#config-nav') [all …]
|
/openbmc/linux/arch/ia64/include/asm/uv/ |
H A 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 …]
|
/openbmc/linux/Documentation/maintainer/ |
H A 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 …]
|
/openbmc/linux/fs/reiserfs/ |
H A 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
|
/openbmc/linux/Documentation/arch/arm/google/ |
H A 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 …]
|
/openbmc/openbmc/meta-openembedded/meta-filesystems/recipes-filesystems/logfsprogs/logfsprogs/ |
H A D | 0001-btree-Avoid-conflicts-with-libc-namespace-about-setk.patch | 3 Date: Thu, 13 Jul 2017 18:41:53 -0700 10 Signed-off-by: Khem Raj <raj.khem@gmail.com> 11 --- 12 Upstream-Status: Pending 14 btree.c | 32 ++++++++++++++++---------------- 15 1 file changed, 16 insertions(+), 16 deletions(-) 17 diff --git a/btree.c b/btree.c 19 --- a/btree.c 21 @@ -123,7 +123,7 @@ static unsigned long bval(struct btree_geo *geo, unsigned long *node, int n) 22 return node[geo->no_pairs * geo->keylen + n]; [all …]
|
/openbmc/linux/include/uapi/linux/ |
H A 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 …]
|
/openbmc/linux/Documentation/driver-api/media/drivers/ |
H A 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 …]
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-navigation/gpsd/gpsd/ |
H A D | fix-pps_strerror_r.patch | 9 ambiguous options that could be both in CFLAGS and LINKFLAGS (e.g. -spec). 16 Upstream-Status: Submitted [https://gitlab.com/gpsd/gpsd/-/merge_requests/406] 17 Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org> 19 --- 20 SConscript | 11 ++++++----- 21 1 file changed, 6 insertions(+), 5 deletions(-) 23 diff --git a/SConscript b/SConscript 25 --- a/SConscript 27 @@ -585,8 +585,8 @@ env['SC_PYTHON'] = sys.executable # Path to SCons Python 31 -# Scons also uses different internal names than most other build-systems. [all …]
|
/openbmc/linux/tools/testing/selftests/kvm/lib/ |
H A 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 …]
|
/openbmc/linux/arch/openrisc/ |
H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0 4 # see Documentation/kbuild/kconfig-language.rst. 89 caches at relevant times. Most OpenRISC implementations support write- 138 bool "Have instruction l.ror for rotate right" 146 l.ror rotate right instruction. 151 bool "Have instruction l.rori for rotate right with immediate" 159 l.rori rotate right with immediate instruction. 179 int "Maximum number of CPUs (2-32)" 185 bool "Symmetric Multi-Processing support" 225 supply some command-line options at build time by entering them
|
/openbmc/qemu/util/ |
H A D | qtree.c | 2 * GLIB - Library of useful routines for C programming 3 * Copyright (C) 1995-1997 Peter Mattis, Spencer Kimball and Josh MacDonald 5 * SPDX-License-Identifier: LGPL-2.1-or-later 22 * Modified by the GLib Team and others 1997-2000. See the AUTHORS 36 * SECTION:trees-binary 43 * in order. This means that most of the operations (access, search, 73 * [balanced binary tree][glib-Balanced-Binary-Trees]. It should be 90 QTreeNode *right; /* right subtree */ member 91 gint8 balance; /* height (right) - height (left) */ 124 node->balance = 0; in q_tree_node_new() [all …]
|
/openbmc/linux/drivers/media/rc/keymaps/ |
H A 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.
|
/openbmc/linux/lib/ |
H A 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 …]
|
/openbmc/qemu/docs/ |
H A D | qcow2-cache.txt | 3 Copyright (C) 2015, 2018-2020 Igalia, S.L. 7 later. See the COPYING file in the top-level directory. 10 ------------ 12 performance significantly. However, setting the right cache sizes is 18 Please refer to the docs/interop/qcow2.txt file for an in-depth 23 -------- 30 The 'qemu-img create' command supports specifying the size using the 33 qemu-img create -f qcow2 -o cluster_size=128K hd.qcow2 4G 37 ------------- 38 The qcow2 format uses a two-level structure to map the virtual disk as [all …]
|
/openbmc/linux/Documentation/driver-api/media/ |
H A 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 …]
|
H A 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
|
/openbmc/linux/Documentation/driver-api/usb/ |
H A 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 …]
|
/openbmc/linux/Documentation/timers/ |
H A 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 …]
|
/openbmc/qemu/include/fpu/ |
H A D | softfloat-macros.h | 5 * IEC/IEEE Floating-point Arithmetic Package. Those parts of the code (and 9 * the SoftFloat-2a license 13 * taken to be licensed under the Softfloat-2a license unless specifically 19 This C source fragment is part of the SoftFloat IEC/IEEE Floating-point 25 National Science Foundation under grant MIP-9311980. The original version 26 of this code was written as part of a project to build a fixed-point vector 80 #include "fpu/softfloat-types.h" 81 #include "qemu/host-utils.h" 84 * shl_double: double-word merging left shift 85 * @l: left or most-significant word [all …]
|