Home
last modified time | relevance | path

Searched +full:non +full:- +full:compliant (Results 1 – 25 of 43) sorted by relevance

12

/Documentation/devicetree/bindings/interrupt-controller/
Dopencores,or1k-pic.txt5 - compatible : should be "opencores,or1k-pic-level" for variants with
6 level triggered interrupt lines, "opencores,or1k-pic-edge" for variants with
7 edge triggered interrupt lines or "opencores,or1200-pic" for machines
8 with the non-spec compliant or1200 type implementation.
10 "opencores,or1k-pic" is also provided as an alias to "opencores,or1200-pic",
13 - interrupt-controller : Identifies the node as an interrupt controller
14 - #interrupt-cells : Specifies the number of cells needed to encode an
19 intc: interrupt-controller {
20 compatible = "opencores,or1k-pic-level";
21 interrupt-controller;
[all …]
/Documentation/x86/i386/
DIO-APIC.rst1 .. SPDX-License-Identifier: GPL-2.0
4 IO-APIC
9 Most (all) Intel-MP compliant SMP boards have the so-called 'IO-APIC',
12 IO-APIC, interrupts from hardware will be delivered only to the
15 Linux supports all variants of compliant SMP boards, including ones with
16 multiple IO-APICs. Multiple IO-APICs are used in high-end servers to
20 usually worked around by the kernel. If your MP-compliant SMP board does
21 not boot Linux, then consult the linux-smp mailing list archives first.
23 If your box boots fine with enabled IO-APIC IRQs, then your
28 0: 1360293 IO-APIC-edge timer
[all …]
/Documentation/devicetree/bindings/pci/
Dhost-generic-pci.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pci/host-generic-pci.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Will Deacon <will@kernel.org>
13 Firmware-initialised PCI host controllers and PCI emulations, such as the
14 virtio-pci implementations found in kvmtool and other para-virtualised
21 Configuration Space is assumed to be memory-mapped (as opposed to being
26 For CAM, this 24-bit offset is:
41 - description:
[all …]
/Documentation/fb/
Duvesafb.rst2 uvesafb - A Generic Driver for VBE2+ compliant video cards
6 ---------------
8 uvesafb should work with any video card that has a Video BIOS compliant
30 --------------------------
36 - Lack of any type of acceleration.
37 - A strict and limited set of supported video modes. Often the native
42 ratio, which is what most BIOS-es are limited to.
43 - Adjusting the refresh rate is only possible with a VBE 3.0 compliant
44 Video BIOS. Note that many nVidia Video BIOS-es claim to be VBE 3.0
45 compliant, while they simply ignore any refresh rate settings.
[all …]
Dvesafb.rst20 * You can run XF68_FBDev on top of /dev/fb0 (=> non-accelerated X11
21 support for every VBE 2.0 compliant graphics board).
22 * Most important: boot logo :-)
33 Documentation/admin-guide/svga.rst for details.
81 "vga=mode-number" you have to transform the numbers to decimal.
88 XF68_FBDev should work just fine, but it is non-accelerated. Running
89 another (accelerated) X-Server like XF86_SVGA might or might not work.
90 It depends on X-Server and graphics board.
92 The X-Server must restore the video mode correctly, else you end up
103 * configure and load the DOS-Tools for the graphics board (if
[all …]
/Documentation/hwmon/
Dlineage-pem.rst1 Kernel driver lineage-pem
8 Prefix: 'lineage-pem'
10 Addresses scanned: -
16 Author: Guenter Roeck <linux@roeck-us.net>
20 -----------
25 Lineage CPL power entry modules are nominally PMBus compliant. However, most
27 and status reporting commands are non-standard. For this reason, a standard
32 -----------
41 $ modprobe lineage-pem
42 $ echo lineage-pem 0x40 > /sys/bus/i2c/devices/i2c-1/new_device
[all …]
Dpmbus-core.rst9 power-management protocol with a fully defined command language that facilitates
11 protocol is implemented over the industry-standard SMBus serial interface and
12 enables programming, control, and real-time monitoring of compliant power
18 promoted by the PMBus Implementers Forum (PMBus-IF), comprising 30+ adopters
22 commands, and manufacturers can add as many non-standard commands as they like.
23 Also, different PMBUs devices act differently if non-supported commands are
43 PMBus device capabilities auto-detection
46 For generic PMBus devices, code in pmbus.c attempts to auto-detect all supported
47 PMBus commands. Auto-detection is somewhat limited, since there are simply too
50 pages (see the PMBus specification for details on multi-page PMBus devices).
[all …]
/Documentation/core-api/
Ddebugging-via-ohci1394.rst2 Using physical DMA provided by OHCI-1394 FireWire controllers for debugging
6 ------------
8 Basically all FireWire controllers which are in use today are compliant
9 to the OHCI-1394 specification which defines the controller to be a PCI
12 PCI-Bus master DMA after applying filters defined by the OHCI-1394 driver.
15 ask the OHCI-1394 controller to perform read and write requests on
28 more common hardware such as x86, x86-64 and PowerPC.
34 Together with a early initialization of the OHCI-1394 controller for debugging,
41 -------
43 The firewire-ohci driver in drivers/firewire uses filtered physical
[all …]
/Documentation/filesystems/
Doverlayfs.rst1 .. SPDX-License-Identifier: GPL-2.0
10 overlay-filesystem functionality in Linux (sometimes referred to as
11 union-filesystems). An overlay-filesystem tries to present a
17 ---------------
25 While directories will report an st_dev from the overlay-filesystem,
26 non-directory objects may report an st_dev from the lower filesystem or
29 over the lifetime of a non-directory object. Many applications and
35 make the overlay mount more compliant with filesystem scanners and
40 underlying filesystem, the same compliant behavior could be achieved
48 feature with the "-o xino=on" overlay mount option. That is useful for the
[all …]
/Documentation/arm/
Duefi.rst7 maintained by the UEFI Forum - http://www.uefi.org/.
16 Booting on a platform with firmware compliant with the UEFI specification
19 - UEFI Runtime Services
20 - Retrieving various configuration information through the standardised
25 - CONFIG_EFI=y
26 - CONFIG_EFIVAR_FS=y or m
29 in a Flattened Device Tree (FDT) - so is only available with CONFIG_OF.
39 booting in non-UEFI environments.
55 linux,uefi-system-table 64-bit Physical address of the UEFI System Table.
57 linux,uefi-mmap-start 64-bit Physical address of the UEFI memory map,
[all …]
Dkernel_mode_neon.rst6 -------------
10 '-march=armv7-a -mfpu=neon -mfloat-abi=softfp'
18 ------------
25 non-preemptible section for reasons outlined below.
29 -------------------------
50 ----------------------------
67 --------------------
69 like IEEE-754 compliant underflow handling etc. When the VFP unit needs such
80 ---------------------------------------
84 instructions of its own at -O3 level if -mfpu=neon is selected, and even if the
[all …]
/Documentation/devicetree/bindings/dma/ti/
Dk3-udma.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/dma/ti/k3-udma.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Peter Ujfalusi <peter.ujfalusi@ti.com>
13 The UDMA-P is intended to perform similar (but significantly upgraded)
14 functions as the packet-oriented DMA used on previous SoC devices. The UDMA-P
16 The UDMA-P architecture facilitates the segmentation and reassembly of SoC DMA
17 data structure compliant packets to/from smaller data blocks that are natively
27 on the Rx PSI-L interface.
[all …]
/Documentation/devicetree/bindings/arm/
Dcoresight.txt3 CoreSight components are compliant with the ARM CoreSight architecture
11 * Required properties for all components *except* non-configurable replicators
12 and non-configurable funnels:
16 - Embedded Trace Buffer (version 1.0):
17 "arm,coresight-etb10", "arm,primecell";
19 - Trace Port Interface Unit:
20 "arm,coresight-tpiu", "arm,primecell";
22 - Trace Memory Controller, used for Embedded Trace Buffer(ETB),
26 "arm,coresight-tmc", "arm,primecell";
28 - Trace Programmable Funnel:
[all …]
/Documentation/hid/
Dhiddev.rst18 normalised event interface - see Documentation/input/input.rst
24 usb.c ---> hid-core.c ----> hid-input.c ----> [keyboard/mouse/joystick/event]
27 --> hiddev.c ----> POWER / MONITOR CONTROL
57 So you point your hiddev compliant user-space program at the correct
60 Assuming that you have a hiddev compliant user-space program, of
69 conveniently linked of http://www.linux-usb.org.
75 each of which can have one or more "usages". In the hid-core,
79 -------
83 the changed value. The hid-core.c module parses the report, and
103 --------
[all …]
/Documentation/leds/
Dleds-class.rst8 of the LED (taking a value 0-max_brightness). Most LEDs don't have hardware
9 brightness support so will just be turned on for non-zero brightness settings.
14 existing subsystems with minimal additional code. Examples are the disk-activity,
15 nand-disk and sharpsl-charge triggers. With led triggers disabled, the code
48 - devicename:
57 - color:
59 include/dt-bindings/leds/common.h.
61 - function:
63 include/dt-bindings/leds/common.h.
66 to linux-leds@vger.kernel.org.
[all …]
/Documentation/process/
Dembargoed-hardware-issues.rst7 -----
23 -------
31 Linux kernel security team (:ref:`Documentation/admin-guide/
34 The team can be contacted by email at <hardware-security@kernel.org>. This
43 - PGP: https://www.kernel.org/static/files/hardware-security.asc
44 - S/MIME: https://www.kernel.org/static/files/hardware-security.crt
55 - Linus Torvalds (Linux Foundation Fellow)
56 - Greg Kroah-Hartman (Linux Foundation Fellow)
57 - Thomas Gleixner (Linux Foundation Fellow)
59 Operation of mailing-lists
[all …]
/Documentation/networking/device_drivers/ethernet/dec/
Dde4x5.rst1 .. SPDX-License-Identifier: GPL-2.0
10 - DE425 TP/COAX EISA
11 - DE434 TP PCI
12 - DE435 TP/COAX/AUI PCI
13 - DE450 TP/COAX/AUI PCI
14 - DE500 10/100 PCI Fasternet
20 - DC21040 (no SROM)
21 - DC21041[A]
22 - DC21140[A]
23 - DC21142
[all …]
/Documentation/translations/it_IT/process/
Dlicense-rules.rst1 .. SPDX-License-Identifier: GPL-2.0
3 .. include:: ../disclaimer-ita.rst
5 :Original: :ref:`Documentation/process/license-rules.rst <kernel_licensing>`
14 versione della licenza *GNU General Public License* (GPL-2.0), di cui una
15 copia è disponibile nel file LICENSES/preferred/GPL-2.0; a questo si
17 LICENSES/exceptions/Linux-syscall-note; tutto ciò è descritto nel file COPYING.
20 debba essere licenziato per far si che sia chiaro e non ambiguo. Questo non
25 devono essere compatibili con la GPL-2.0::
27 GPL-1.0+ : GNU General Public License v1.0 o successiva
28 GPL-2.0+ : GNU General Public License v2.0 o successiva
[all …]
/Documentation/admin-guide/device-mapper/
Ddm-zoned.rst2 dm-zoned
5 The dm-zoned device mapper target exposes a zoned block device (ZBC and
6 ZAC compliant devices) as a regular block device without any write
7 pattern constraints. In effect, it implements a drive-managed zoned
10 host-managed zoned block devices and can mitigate the potential
11 device-side performance degradation due to excessive random writes on
12 host-aware zoned block devices.
21 http://www.t13.org/Documents/UploadedDocuments/docs2015/di537r05-Zoned_Device_ATA_Command_Set_ZAC.p…
23 The dm-zoned implementation is simple and minimizes system overhead (CPU
25 host-managed disk with 256 MB zones, dm-zoned memory usage per disk
[all …]
/Documentation/networking/
Dcan.rst2 SocketCAN - Controller Area Network
20 .. _socketcan-motivation:
29 functionality. Usually, there is only a hardware-specific device
32 Queueing of frames and higher-level transport protocols like ISO-TP
34 character-device implementations support only one single process to
47 protocol family module and also vice-versa. Also, the protocol family
57 communicate using a specific transport protocol, e.g. ISO-TP, just
60 CAN-IDs, frames, etc.
62 Similar functionality visible from user-space could be provided by a
74 * **Abstraction:** In most existing character-device implementations, the
[all …]
/Documentation/translations/zh_CN/process/
Dlicense-rules.rst1 .. SPDX-License-Identifier: GPL-2.0
3 .. include:: ../disclaimer-zh_CN.rst
5 :Original: :ref:`Documentation/process/license-rules.rst <kernel_licensing>`
13 Linux内核根据LICENSES/preferred/GPL-2.0中提供的GNU通用公共许可证版本2
14 （GPL-2.0）的条款提供，并在LICENSES/exceptions/Linux-syscall-note中显式
21 具有不同的与GPL-20兼容的许可证::
23 GPL-1.0+ : GNU通用公共许可证v1.0或更高版本
24 GPL-2.0+ : GNU通用公共许可证v2.0或更高版本
25 LGPL-2.0 : 仅限GNU库通用公共许可证v2
26 LGPL-2.0+: GNU 库通用公共许可证v2或更高版本
[all …]
/Documentation/admin-guide/
Dsvga.rst7 :Copyright: |copy| 1995--1999 Martin Mares, <mj@ucw.cz>
22 remember its mode ID (the four-digit hexadecimal number) and then
31 NORMAL_VGA - Standard 80x25 mode available on all display adapters.
33 EXTENDED_VGA - Standard 8-pixel font mode: 80x43 on EGA, 80x50 on VGA.
35 ASK_VGA - Display a video mode menu upon startup (see below).
37 0..35 - Menu item number (when you have used the menu to view the list of
41 modes are listed in a "first detected -- first displayed" manner. It's
44 0x.... - Hexadecimal video mode ID (also displayed on the menu, see below
46 hexadecimal numbers -- you have to convert it to decimal manually.
59 Video adapter: <name-of-detected-video-adapter>
[all …]
/Documentation/PCI/
Dpci.rst1 .. SPDX-License-Identifier: GPL-2.0
7 :Authors: - Martin Mares <mj@ucw.cz>
8 - Grant Grundler <grundler@parisc-linux.org>
11 Since each CPU architecture implements different chip-sets and PCI devices
18 by Jonathan Corbet, Alessandro Rubini, and Greg Kroah-Hartman.
26 "Linux PCI" <linux-pci@atrey.karlin.mff.cuni.cz> mailing list.
38 supporting hot-pluggable PCI, CardBus, and Express-Card in a single driver].
45 - Enable the device
46 - Request MMIO/IOP resources
47 - Set the DMA mask size (for both coherent and streaming DMA)
[all …]
/Documentation/networking/device_drivers/wifi/intel/
Dipw2100.rst1 .. SPDX-License-Identifier: GPL-2.0
10 - Intel(R) PRO/Wireless 2100 Network Connection
12 Copyright |copy| 2003-2006, Intel Corporation
16 :Version: git-1.1.5
23 2. Release git-1.1.5 Current Features
64 the warranty and/or issues arising from regulatory non-compliance, and
69 modules, and accordingly, condition system-level regulatory approval
72 non-compliant.
81 https://www.intel.com/support/wireless/sb/CS-006408.htm
97 2. Release git-1.1.5 Current Supported Features
[all …]
/Documentation/netlabel/
Ddraft-ietf-cipso-ipsecurity-01.txt27 Please check the I-D abstract listing contained in each Internet Draft
46 mandatory access controls and multi-level security. These systems are
88 once in a datagram. All multi-octet fields in the option are defined to be
91 +----------+----------+------//------+-----------//---------+
93 +----------+----------+------//------+-----------//---------+
124 corresponding ASCII representations. Non-related groups of systems may
148 actual security information to be passed. All multi-octet fields in a tag
171 +----------+----------+--------//--------+
173 +----------+----------+--------//--------+
207 This is referred to as the "bit-mapped" tag type. Tag type 1 is included
[all …]

12