Searched full:interfaces (Results 1 – 25 of 542) sorted by relevance
12345678910>>...22
| /Documentation/ABI/ |
| D | README | 2 userspace, and the relative stability of these interfaces. Due to the
4 interfaces should be used by userspace programs in different ways.
7 different subdirectories in this location. Interfaces may change levels
13 This directory documents the interfaces that the developer has
15 interfaces with no restrictions, and backward compatibility for
16 them will be guaranteed for at least 2 years. Most interfaces
21 This directory documents interfaces that are felt to be stable,
26 programs can start to rely on these interfaces, but they must be
27 aware of changes that can occur before these interfaces move to
28 be marked stable. Programs that use these interfaces are
[all …]
|
| /Documentation/networking/ |
| D | ipv6.rst | 37 No IPv6 addresses will be added to interfaces, and
45 on all interfaces. This might be used when one does not wish
52 IPv6 address autoconfiguration is disabled on all interfaces.
55 will be added to interfaces.
58 IPv6 address autoconfiguration is enabled on all interfaces.
64 Specifies whether to disable IPv6 on all interfaces.
70 IPv6 is enabled on all interfaces.
75 IPv6 is disabled on all interfaces.
77 No IPv6 addresses will be added to interfaces.
|
| D | 6lowpan.rst | 4 Netdev private dataroom for 6lowpan interfaces
7 All 6lowpan able net devices, means all interfaces with ARPHRD_6LOWPAN,
53 by ARPHRD_6LOWPAN interfaces.
|
| /Documentation/admin-guide/ |
| D | abi-testing.rst | 4 Documents interfaces that are felt to be stable,
11 Userspace programs can start to rely on these interfaces, but they must
12 be aware of changes that can occur before these interfaces move to
15 Programs that use these interfaces are strongly encouraged to add their
16 name to the description of these interfaces, so that the kernel
|
| D | abi-stable.rst | 4 Documents the interfaces that the developer has defined to be stable.
6 Userspace programs are free to use these interfaces with no
10 Most interfaces (like syscalls) are expected to never change and always
|
| /Documentation/scsi/ |
| D | bnx2fc.rst | 7 cooperates with all interfaces provided by the Linux ecosystem for FC/FCoE and
13 depend on the state of the network interfaces to operate. As such, the network
15 It is recommended that the network interfaces be configured to be brought up
18 Furthermore, the Broadcom FCoE offload solution creates VLAN interfaces to
20 eth0.1001-fcoe). Do not delete or disable these interfaces or FCoE operation
28 2. Configure the interfaces on which bnx2fc driver has to operate on.
33 c. Repeat this for all the interfaces where FCoE has to be enabled.
41 the system, bnx2fc driver would automatically claim the interfaces, starts vlan
69 <INTERFACE>.<VLAN>-fcoe interfaces are automatically created.
72 create/destroy interfaces or to display lun/target information.
|
| /Documentation/driver-api/ |
| D | firewire.rst | 8 The Linux FireWire subsystem adds some interfaces into the Linux system to
11 The main purpose of these interfaces is to access address space on each node
15 Two types of interfaces are added, according to consumers of the interface. A
16 set of userspace interfaces is available via `firewire character devices`. A set
17 of kernel interfaces is available via exported symbols in `firewire-core` module.
28 Firewire device probing and sysfs interfaces
37 Firewire core transaction interfaces
43 Firewire Isochronous I/O interfaces
|
| D | target.rst | 2 target and iSCSI Interfaces Guide
10 Target core device interfaces
16 Target core transport interfaces
44 iSCSI TCP interfaces
|
| D | s390-drivers.rst | 10 This document describes the interfaces available for device drivers that
11 drive s390 based channel attached I/O devices. This includes interfaces
12 for interaction with the hardware and interfaces for interacting with
13 the common driver core. Those interfaces are provided by the s390 common
121 Generic interfaces
124 The following section contains interfaces in use not only by drivers
|
| D | ipmi.rst | 35 The message handler does not provide any user-level interfaces.
98 IPMI users tie into this, and the IPMI physical interfaces (called
99 System Management Interfaces, or SMIs) also tie in here. This
107 ipmi_si - A driver for various system interfaces. This supports KCS,
108 SMIC, and BT interfaces. Unless you have an SMBus interface or your
112 I2C kernel driver's SMBus interfaces to send and receive IPMI messages
135 linux/ipmi_smi.h - Contains the interface for system management interfaces
244 view of the IPMI interfaces. It allows multiple SMI interfaces to be
249 Watching For Interfaces
256 watcher with ipmi_smi_watcher_register() to iterate over interfaces
[all …]
|
| /Documentation/devicetree/bindings/media/i2c/ |
| D | sony,imx214.txt | 22 - flash-leds: See ../video-interfaces.txt
23 - lens-focus: See ../video-interfaces.txt
27 Documentation/devicetree/bindings/media/video-interfaces.txt.
30 - data-lanes: check ../video-interfaces.txt
31 - link-frequencies: check ../video-interfaces.txt
32 - remote-endpoint: check ../video-interfaces.txt
|
| D | imx290.txt | 5 interfaces. The sensor output is available via CMOS logic parallel SDR output,
24 Documentation/devicetree/bindings/media/video-interfaces.txt.
27 - data-lanes: check ../video-interfaces.txt
28 - link-frequencies: check ../video-interfaces.txt
29 - remote-endpoint: check ../video-interfaces.txt
|
| D | nokia,smia.txt | 8 Documentation/devicetree/bindings/media/video-interfaces.txt .
12 Documentation/devicetree/bindings/media/video-interfaces.txt .
31 - flash-leds: See ../video-interfaces.txt
32 - lens-focus: See ../video-interfaces.txt
35 ../video-interfaces.txt .
|
| D | toshiba,et8ek8.txt | 6 Documentation/devicetree/bindings/media/video-interfaces.txt .
26 - flash-leds: See ../video-interfaces.txt
27 - lens-focus: See ../video-interfaces.txt
|
| /Documentation/process/ |
| D | stable-api-nonsense.rst | 15 Please realize that this article describes the **in kernel** interfaces, not
16 the kernel to userspace interfaces.
41 to worry about the in-kernel interfaces changing. For the majority of
53 So, there are two main topics here, binary kernel interfaces and stable
54 kernel source interfaces. They both depend on each other, but we will
101 Stable Kernel Source Interfaces
110 current interfaces, or figure out a better way to do things. If they do
111 that, they then fix the current interfaces to work better. When they do
117 As a specific examples of this, the in-kernel USB interfaces have
132 which have had to maintain their older USB interfaces over time. This
[all …]
|
| /Documentation/devicetree/bindings/media/ |
| D | samsung-s5k6a3.txt | 4 S5K6A3(YX) is a raw image sensor with MIPI CSI-2 and CCP2 image data interfaces
26 The common video interfaces bindings (see video-interfaces.txt) should be
33 video-interfaces.txt. The sensor supports only one data lane.
|
| D | samsung-s5c73m3.txt | 7 slave device nodes corresponding to these control bus interfaces are required
36 The common video interfaces bindings (see video-interfaces.txt) should be used
49 video-interfaces.txt. This sensor doesn't support data lane remapping
|
| /Documentation/usb/ |
| D | authorization.rst | 12 its interfaces are immediately made available to the users. With this
101 There is a similar approach to allow or deny specific USB interfaces.
112 The default value for new interfaces
115 Allow interfaces per default::
119 Deny interfaces per default::
124 So all interfaces would authorized per default.
130 For drivers that need multiple interfaces all needed interfaces should be
|
| /Documentation/networking/dsa/ |
| D | configuration.rst | 35 All other corresponding linux interfaces are called slave interfaces.
37 The slave interfaces depend on the master interface. They can only brought up,
40 In this documentation the following Ethernet interfaces are used:
57 Further Ethernet interfaces can be configured similar.
94 # bring up the slave interfaces
107 # bring up the slave interfaces
134 # bring up the slave interfaces
181 # bring up the slave interfaces
223 # bring up the slave interfaces
265 # bring up the slave interfaces
|
| D | bcm_sf2.rst | 13 ports, offering a range of built-in and customizable interfaces:
19 - several external MII/RevMII/GMII/RGMII interfaces
23 band back-pressure to the host CPU network interface when downstream interfaces
30 - ``SWITCH_REG``: external interfaces switch register
79 Multimedia over CoAxial (MoCA) interfaces
82 MoCA interfaces are fairly specific and require the use of a firmware blob which
89 The MoCA interfaces are supported using the PHY library's fixed PHY/emulated PHY
|
| /Documentation/devicetree/bindings/sound/ |
| D | fsl,audmix.txt | 5 audio interfaces. These are driven by two Synchronous Audio interface
8 from two interfaces into a single sample. Before mixing, audio samples of
10 Audio Mixer is also a serial audio interface. Like input interfaces it has
38 to SAI interfaces to be provided, the first SAI in the
|
| /Documentation/ABI/stable/ |
| D | sysfs-class-backlight | 50 interfaces are available for a single device, firmware
55 backlight state. Platform interfaces are mostly a
57 interfaces.
|
| /Documentation/driver-api/firmware/ |
| D | other_interfaces.rst | 1 Other Firmware Interfaces
4 DMI Interfaces
10 EDD Interfaces
|
| /Documentation/userspace-api/media/v4l/ |
| D | dv-timings.rst | 11 hardware interfaces such as High Definition TV interfaces (HDMI), VGA,
13 extend the API to select the video timings for these interfaces. Since
|
| /Documentation/devicetree/bindings/ata/ |
| D | cortina,gemini-sata-bridge.txt | 26 ata0 master and slave interfaces brought out
30 ata1 master and slave interfaces brought out
36 and whether master, slave or both interfaces get brought out.
|
12345678910>>...22