Searched +full:x +full:- +full:rc (Results 1 – 25 of 48) sorted by relevance
12
| /Documentation/devicetree/bindings/media/ |
| D | video-interface-devices.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/media/video-interface-devices.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Jacopo Mondi <jacopo@jmondi.org> 11 - Sakari Ailus <sakari.ailus@linux.intel.com> 14 flash-leds: 15 $ref: /schemas/types.yaml#/definitions/phandle-array 17 An array of phandles, each referring to a flash LED, a sub-node of the LED 20 lens-focus: [all …]
|
| /Documentation/PCI/endpoint/ |
| D | pci-test-function.rst | 1 .. SPDX-License-Identifier: GPL-2.0 9 Traditionally PCI RC has always been validated by using standard 11 However with the addition of EP-core in linux kernel, it is possible 46 Bit 2 raise MSI-X IRQ 47 Bit 3 read command (read data from RC buffer) 48 Bit 4 write command (write data to RC buffer) 49 Bit 5 copy command (copy data from one RC buffer to another RC buffer) 72 This register contains the source address (RC buffer address) for the 77 This register contains the destination address (RC buffer address) for 90 MSI-X 2 [all …]
|
| /Documentation/security/ |
| D | sak.rst | 15 providing SAK. One is the ALT-SYSRQ-K sequence. You shouldn't use 24 once defined, SAK will kill a running X server. If the system is in 25 run level 5, the X server will restart. This is what you want to 28 What key sequence should you use? Well, CTRL-ALT-DEL is used to reboot 29 the machine. CTRL-ALT-BACKSPACE is magical to the X server. We'll 30 choose CTRL-ALT-PAUSE. 32 In your rc.sysinit (or rc.local) file, add the command:: 57 # ls -l /proc/[0-9]*/fd/* | grep console 58 l-wx------ 1 root root 64 Mar 18 00:46 /proc/579/fd/0 -> /dev/console 63 root 579 0.0 0.1 1088 436 ? S 00:43 0:00 gpm -t ps/2 [all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-rc | 1 What: /sys/class/rc/ 6 The rc/ class sub-directory belongs to the Remote Controller 10 What: /sys/class/rc/rc<N>/ 15 A /sys/class/rc/rcN directory is created for each remote 18 What: /sys/class/rc/rc<N>/protocols 33 Writing "-proto" will remove a protocol from the list of enabled 43 What: /sys/class/rc/rc<N>/filter 50 Use in combination with /sys/class/rc/rcN/filter_mask to set the 58 What: /sys/class/rc/rc<N>/filter_mask 64 Use in combination with /sys/class/rc/rcN/filter to set the bits [all …]
|
| D | sysfs-bus-platform-devices-ampere-smpro | 1 What: /sys/bus/platform/devices/smpro-errmon.*/error_[core|mem|pcie|other]_[ce|ue] 5 (RO) Contains the 48-byte Ampere (Vendor-Specific) Error Record printed 8 …+--------+---------------+-------------+----------------------------------------------------------… 10 …+--------+---------------+-------------+----------------------------------------------------------… 11 …| 00 | Error Type | 1 | See :ref:`the table below <smpro-error-types>` for detail… 12 …+--------+---------------+-------------+----------------------------------------------------------… 13 …| 01 | Subtype | 1 | See :ref:`the table below <smpro-error-types>` for detail… 14 …+--------+---------------+-------------+----------------------------------------------------------… 15 …| 02 | Instance | 2 | See :ref:`the table below <smpro-error-types>` for detail… 16 …+--------+---------------+-------------+----------------------------------------------------------… [all …]
|
| /Documentation/devicetree/bindings/pci/ |
| D | ti-pci.txt | 4 - compatible: Should be "ti,dra7-pcie" for RC (deprecated) 5 Should be "ti,dra7-pcie-ep" for EP (deprecated) 6 Should be "ti,dra746-pcie-rc" for dra74x/dra76 in RC mode 7 Should be "ti,dra746-pcie-ep" for dra74x/dra76 in EP mode 8 Should be "ti,dra726-pcie-rc" for dra72x in RC mode 9 Should be "ti,dra726-pcie-ep" for dra72x in EP mode 10 - phys : list of PHY specifiers (used by generic PHY framework) 11 - phy-names : must be "pcie-phy0", "pcie-phy1", "pcie-phyN".. based on the 13 - ti,hwmods : Name of the hwmod associated to the pcie, "pcie<X>", 14 where <X> is the instance number of the pcie from the HW spec. [all …]
|
| /Documentation/userspace-api/media/rc/ |
| D | rc-protos.rst | 1 .. SPDX-License-Identifier: GPL-2.0 OR GFDL-1.1-no-invariants-or-later 22 Some remotes have a pointer-type device which can used to control the 29 rc-5 (RC_PROTO_RC5) 30 ------------------- 38 .. flat-table:: rc5 bits scancode mapping 41 * - rc-5 bit 43 - scancode bit 45 - description 47 * - 1 49 - none [all …]
|
| D | rc-sysfs-nodes.rst | 1 .. SPDX-License-Identifier: GPL-2.0 OR GFDL-1.1-no-invariants-or-later 9 As defined at ``Documentation/ABI/testing/sysfs-class-rc``, those are 15 /sys/class/rc/ 18 The ``/sys/class/rc/`` class sub-directory belongs to the Remote 25 /sys/class/rc/rcN/ 28 A ``/sys/class/rc/rcN`` directory is created for each remote control 34 /sys/class/rc/rcN/protocols 45 Writing "-proto" will remove a protocol from the list of enabled 58 /sys/class/rc/rcN/filter 63 Use in combination with ``/sys/class/rc/rcN/filter_mask`` to set the [all …]
|
| D | lirc-dev-intro.rst | 1 .. SPDX-License-Identifier: GPL-2.0 OR GFDL-1.1-no-invariants-or-later 10 a bi-directional interface for transporting raw IR and decoded scancodes 12 (/dev/lircX, for X = 0, 1, 2, ...), with a number of standard struct 21 .. code-block:: none 24 rc rc0: lirc_dev: driver mceusb registered at minor = 0, raw IR receiver, raw IR transmitter 28 .. code-block:: none 30 $ ls -l /dev/lirc* 31 crw-rw---- 1 root root 248, 0 Jul 2 22:20 /dev/lirc0 33 Note that the package `v4l-utils <https://git.linuxtv.org/v4l-utils.git/>`_ 36 - ir-ctl: can receive raw IR and transmit IR, as well as query LIRC [all …]
|
| /Documentation/translations/it_IT/process/ |
| D | stable-kernel-rules.rst | 1 .. include:: ../disclaimer-ita.rst 3 :Original: :ref:`Documentation/process/stable-kernel-rules.rst <stable_kernel_rules>` 8 Tutto quello che volevate sapere sui rilasci -stable di Linux 12 "-stable": 14 - Questa patch o una equivalente deve esistere già nei sorgenti principali di 16 - Ovviamente dev'essere corretta e verificata. 17 - Non dev'essere più grande di 100 righe, incluso il contesto. 18 - Deve rispettare le regole scritte in 19 :ref:`Documentation/translations/it_IT/process/submitting-patches.rst <it_submittingpatches>` 20 - Deve correggere un vero baco che causi problemi agli utenti oppure aggiunge [all …]
|
| /Documentation/process/ |
| D | stable-kernel-rules.rst | 3 Everything you ever wanted to know about Linux -stable releases 7 "-stable" tree: 9 - It or an equivalent fix must already exist in Linux mainline (upstream). 10 - It must be obviously correct and tested. 11 - It cannot be bigger than 100 lines, with context. 12 - It must follow the 13 :ref:`Documentation/process/submitting-patches.rst <submittingpatches>` 15 - It must either fix a real bug that bothers people or just add a device ID. 18 - It fixes a problem like an oops, a hang, data corruption, a real security 21 - Serious issues as reported by a user of a distribution kernel may also [all …]
|
| D | applying-patches.rst | 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 96 gunzip or xz on the file -- like this:: [all …]
|
| /Documentation/scsi/ |
| D | NinjaSCSI.rst | 1 .. SPDX-License-Identifier: GPL-2.0 4 WorkBiT NinjaSCSI-3/32Bi driver for Linux 10 This is Workbit corp.'s(http://www.workbit.co.jp/) NinjaSCSI-3 17 :pcmcia-cs: 3.1.27 18 :gcc: gcc-2.95.4 19 :PC card: I-O data PCSC-F (NinjaSCSI-3), 20 I-O data CBSC-II in 16 bit mode (NinjaSCSI-32Bi) 21 :SCSI device: I-O data CDPS-PX24 (CD-ROM drive), 22 Media Intelligent MMO-640GT (Optical disk drive) 27 (a) Check your PC card is true "NinjaSCSI-3" card. [all …]
|
| /Documentation/driver-api/media/ |
| D | dtv-frontend.rst | 1 .. SPDX-License-Identifier: GPL-2.0 4 ------------------------ 9 The Digital TV Frontend kABI defines a driver-internal interface for 10 registering low-level, hardware specific driver to a hardware independent 29 .name = "foo DVB-T/T2/C driver", 70 .name = "Bar DVB-S/S2 demodulator", 91 /* Satellite-specific */ 100 #) For satellite digital TV standards (DVB-S, DVB-S2, ISDB-S), the 129 ``DVBFE_ALGO_SW``, meaning that the dvb-core will do a zigzag when tuning, 131 then, it will do ``f`` + |delta|, ``f`` - |delta|, ``f`` + 2 x |delta|, [all …]
|
| /Documentation/admin-guide/media/ |
| D | dvb-usb-af9015-cardlist.rst | 1 .. SPDX-License-Identifier: GPL-2.0 3 dvb-usb-af9015 cards list 8 .. flat-table:: 9 :header-rows: 1 11 :stub-columns: 0 13 * - Card name 14 - USB IDs 15 * - AVerMedia A309 16 - 07ca:a309 17 * - AVerMedia AVerTV DVB-T Volar X [all …]
|
| D | dvb-usb-rtl28xxu-cardlist.rst | 1 .. SPDX-License-Identifier: GPL-2.0 3 dvb-usb-rtl28xxu cards list 8 .. flat-table:: 9 :header-rows: 1 11 :stub-columns: 0 13 * - Card name 14 - USB IDs 15 * - ASUS My Cinema-U3100Mini Plus V2 16 - 1b80:d3a8 17 * - Astrometa DVB-T2 [all …]
|
| /Documentation/maintainer/ |
| D | configure-git.rst | 7 Documentation/maintainer/pull-requests.rst) should be signed with the 9 ``-u <key-id>`` to ``git tag``. However, since you would *usually* use the same 10 key for the project, you can set it in the configuration and use the ``-s`` 11 flag. To set the default ``key-id`` use:: 28 rc file):: 34 ---------------------------------------- 44 Link: https://lore.kernel.org/r/<message-id> 50 $ cat >.git/hooks/applypatch-msg <<'EOF' 52 . git-sh-setup 53 perl -pi -e 's|^Message-I[dD]:\s*<?([^>]+)>?$|Link: https://lore.kernel.org/r/$1|g;' "$1" [all …]
|
| /Documentation/arch/s390/ |
| D | s390dbf.rst | 6 - arch/s390/kernel/debug.c 7 - arch/s390/include/asm/debug.h 10 ------------ 24 ------- 31 which are written by event- and exception-calls. 33 An event-call writes the specified debug entry to the active debug 39 An exception-call writes the specified debug entry to the log and 48 There are four versions for the event- and exception-calls: One for 50 and one for sprintf-like formatted strings. 54 - Timestamp [all …]
|
| /Documentation/userspace-api/ |
| D | mseal.rst | 1 .. SPDX-License-Identifier: GPL-2.0 12 the memory has to be marked with X bit, or else an exception will happen. 17 such an attacker primitive can break control-flow integrity guarantees 18 since read-only memory that is supposed to be trusted can become writable 29 ----------------------- 34 - The start address must be in an allocated VMA. 35 - The start address must be page aligned. 36 - The end address (**addr** + **len**) must be in an allocated VMA. 37 - no gap (unallocated memory) between start and end address. 44 - **0**: Success. [all …]
|
| /Documentation/translations/zh_TW/process/ |
| D | 5.Posting.rst | 1 .. SPDX-License-Identifier: GPL-2.0 3 .. include:: ../disclaimer-zh_TW.rst 25 :ref:`Documentation/translations/zh_CN/process/submitting-patches.rst <tw_submittingpatches>` 26 和 :ref:`Documentation/translations/zh_CN/process/submit-checklist.rst <tw_submitchecklist>`。 29 -------- 41 ------------ 45 - 儘可能地測試代碼。利用內核的調試工具,確保內核使用了所有可能的配置選項組合 48 - 確保您的代碼符合內核代碼風格指南。 50 - 您的更改是否具有性能影響?如果是這樣,您應該運行基準測試來顯示您的變更的 53 - 確保您有權發佈代碼。如果這項工作是爲僱主完成的,僱主對這項工作具有所有權, [all …]
|
| D | 2.Process.rst | 1 .. SPDX-License-Identifier: GPL-2.0 3 .. include:: ../disclaimer-zh_TW.rst 27 ---- 41 每個5.x版本都是一個主要的內核版本,具有新特性、內部API更改等等。一個典型的5.x 54 釋放第一個“rc”內核。例如,對於目標爲5.6的內核,在合併窗口結束時發生的釋放 55 將被稱爲5.6-rc1。-rc1 版本是一個信號,表示合併新特性的時間已經過去,穩定下一 65 新的-rc內核;在內核被認爲足夠穩定並最終發佈前,一般會達到-rc6到-rc9之間。 72 九月 30 5.4-rc1 合併窗口關閉 73 十月 6 5.4-rc2 74 十月 13 5.4-rc3 [all …]
|
| /Documentation/translations/zh_CN/process/ |
| D | 5.Posting.rst | 1 .. include:: ../disclaimer-zh_CN.rst 22 :ref:`Documentation/translations/zh_CN/process/submitting-patches.rst <cn_submittingpatches>` 23 和 :ref:`Documentation/translations/zh_CN/process/submit-checklist.rst <cn_submitchecklist>`。 26 -------- 38 ------------ 42 - 尽可能地测试代码。利用内核的调试工具,确保内核使用了所有可能的配置选项组合 45 - 确保您的代码符合内核代码风格指南。 47 - 您的更改是否具有性能影响?如果是这样,您应该运行基准测试来显示您的变更的 50 - 确保您有权发布代码。如果这项工作是为雇主完成的,雇主对这项工作具有所有权, 56 -------- [all …]
|
| D | 2.Process.rst | 1 .. include:: ../disclaimer-zh_CN.rst 24 ---- 38 每个5.x版本都是一个主要的内核版本,具有新特性、内部API更改等等。一个典型的5.x 51 释放第一个“rc”内核。例如,对于目标为5.6的内核,在合并窗口结束时发生的释放 52 将被称为5.6-rc1。-rc1 版本是一个信号,表示合并新特性的时间已经过去,稳定下一 62 新的-rc内核;在内核被认为足够稳定并最终发布前,一般会达到-rc6到-rc9之间。 69 九月 30 5.4-rc1 合并窗口关闭 70 十月 6 5.4-rc2 71 十月 13 5.4-rc3 72 十月 20 5.4-rc4 [all …]
|
| /Documentation/ABI/stable/ |
| D | sysfs-driver-ib_srp | 1 What: /sys/class/infiniband_srp/srp-<hca>-<port_number>/add_target 4 Contact: linux-rdma@vger.kernel.org 7 a comma-separated list of login parameters to this sysfs 10 * id_ext, a 16-digit hexadecimal number specifying the eight 11 byte identifier extension in the 16-byte SRP target port 14 * ioc_guid, a 16-digit hexadecimal number specifying the eight 15 byte I/O controller GUID portion of the 16-byte target port 17 * dgid, a 32-digit hexadecimal number specifying the 19 * pkey, a four-digit hexadecimal number specifying the 21 * service_id, a 16-digit hexadecimal number specifying the [all …]
|
| /Documentation/networking/device_drivers/hamradio/ |
| D | z8530drv.rst | 1 .. SPDX-License-Identifier: GPL-2.0 5 SCC.C - Linux driver for Z8530 based HDLC cards for AX.25 14 1. ftp://ftp.ccac.rwth-aachen.de/pub/jr/z8530drv-utils_3.0-3.tar.gz 16 2. ftp://ftp.pspt.fi/pub/ham/linux/ax25/z8530drv-utils_3.0-3.tar.gz 40 use a 2.x version (available from above sites) or read the 41 AX.25-HOWTO on how to emulate a KISS TNC on network device drivers. 54 please read 'man insmod' that comes with module-init-tools. 56 You should include the insmod in one of the /etc/rc.d/rc.* files, 64 of your rc.*-files. This has to be done BEFORE you can 92 - this is just a delimiter to make sccinit a bit simpler to [all …]
|
12