| /linux-3.4.99/arch/cris/arch-v10/kernel/ |
| D | io_interface_mux.c | 121 static struct interface interfaces[] = { variable
618 if (interfaces[ioif].used) { in cris_request_io_interface()
621 interfaces[ioif].name, in cris_request_io_interface()
623 interfaces[ioif].owner); in cris_request_io_interface()
630 group_set = interfaces[ioif].groups; in cris_request_io_interface()
636 if_group_use = interfaces[ioif].group_a; in cris_request_io_interface()
639 if_group_use = interfaces[ioif].group_b; in cris_request_io_interface()
642 if_group_use = interfaces[ioif].group_c; in cris_request_io_interface()
645 if_group_use = interfaces[ioif].group_d; in cris_request_io_interface()
648 if_group_use = interfaces[ioif].group_e; in cris_request_io_interface()
[all …]
|
| /linux-3.4.99/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.
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
30 these interfaces, so that the kernel developers can easily
[all …]
|
| /linux-3.4.99/Documentation/networking/ |
| D | ipv6.txt | 31 No IPv6 addresses will be added to interfaces, and
39 on all interfaces. This might be used when one does not wish
46 IPv6 address autoconfiguration is disabled on all interfaces.
49 will be added to interfaces.
52 IPv6 address autoconfiguration is enabled on all interfaces.
58 Specifies whether to disable IPv6 on all interfaces.
64 IPv6 is enabled on all interfaces.
69 IPv6 is disabled on all interfaces.
71 No IPv6 addresses will be added to interfaces.
|
| D | proc_net_tcp.txt | 1 This document describes the interfaces /proc/net/tcp and /proc/net/tcp6.
2 Note that these interfaces are deprecated in favor of tcp_diag.
4 These /proc interfaces provide information about currently active TCP
|
| D | batman-adv.txt | 32 batman advanced will scan your systems interfaces to search for
33 compatible interfaces. Once found, it will create subfolders in
40 ably is not supported. Not supported interfaces are: loopback,
41 non-ethernet and batman's own interfaces.
44 new interfaces to verify the compatibility. There is no need to
53 Repeat this step for all interfaces you wish to add. Now batman
111 All interfaces added to batman advanced are not relevant any
125 ously assigned to interfaces now used by batman advanced, e.g.
172 values are only applied on primary interfaces
223 interfaces to the kernel module settings.
|
| /linux-3.4.99/Documentation/scsi/ |
| D | bnx2fc.txt | 4 cooperates with all interfaces provided by the Linux ecosystem for FC/FCoE and
10 depend on the state of the network interfaces to operate. As such, the network
12 It is recommended that the network interfaces be configured to be brought up
15 Furthermore, the Broadcom FCoE offload solution creates VLAN interfaces to
17 eth0.1001-fcoe). Do not delete or disable these interfaces or FCoE operation
25 2. Configure the interfaces on which bnx2fc driver has to operate on.
29 c. Repeat this for all the interfaces where FCoE has to be enabled.
37 the system, bnx2fc driver would automatically claim the interfaces, starts vlan
63 <INTERFACE>.<VLAN>-fcoe interfaces are automatically created.
66 create/destroy interfaces or to display lun/target information.
|
| /linux-3.4.99/drivers/i2c/algos/ |
| D | Kconfig | 9 tristate "I2C bit-banging interfaces"
12 tristate "I2C PCF 8584 interfaces"
15 tristate "I2C PCA 9564 interfaces"
|
| /linux-3.4.99/Documentation/ |
| D | stable_api_nonsense.txt | 8 realize that this article describes the _in kernel_ interfaces, not the
9 kernel to userspace interfaces. The kernel to userspace interface is
32 to worry about the in-kernel interfaces changing. For the majority of
44 So, there are two main topics here, binary kernel interfaces and stable
45 kernel source interfaces. They both depend on each other, but we will
97 current interfaces, or figure out a better way to do things. If they do
98 that, they then fix the current interfaces to work better. When they do
104 As a specific examples of this, the in-kernel USB interfaces have
118 which have had to maintain their older USB interfaces over time. This
120 interfaces and do things in improper ways, causing the stability of the
[all …]
|
| D | IPMI.txt | 36 The message handler does not provide any user-level interfaces.
97 IPMI users tie into this, and the IPMI physical interfaces (called
106 ipmi_si - A driver for various system interfaces. This supports KCS,
107 SMIC, and BT interfaces. Unless you have an SMBus interface or your
111 I2C kernel driver's SMBus interfaces to send and receive IPMI messages
134 linux/ipmi_smi.h - Contains the interface for system management interfaces
243 view of the IPMI interfaces. It allows multiple SMI interfaces to be
342 As mentioned before, multiple SMI interfaces may be registered to the
348 The ipmi_smi.h defines the interface for management interfaces, see
355 The SI driver allows up to 4 KCS or SMIC interfaces to be configured
[all …]
|
| /linux-3.4.99/net/mac80211/ |
| D | pm.c | 85 list_for_each_entry(sdata, &local->interfaces, list) { in __ieee80211_suspend()
94 list_for_each_entry(sdata, &local->interfaces, list) in __ieee80211_suspend()
114 list_for_each_entry(sdata, &local->interfaces, list) { in __ieee80211_suspend()
|
| D | chan.c | 17 list_for_each_entry(sdata, &local->interfaces, list) { in __ieee80211_get_channel_mode()
77 list_for_each_entry(tmp, &local->interfaces, list) { in ieee80211_set_channel_type()
|
| /linux-3.4.99/Documentation/aoe/ |
| D | mkdevs.sh | 28 rm -f $dir/interfaces
29 mknod -m 0200 $dir/interfaces c $MAJOR 4
|
| D | aoe.txt | 46 "echo eth2 eth4 > /dev/etherd/interfaces" tells the aoe driver to
106 option discussed below) instead of /dev/etherd/interfaces to limit
107 AoE traffic to the network interfaces in the given
112 interfaces. The aoetools package provides an aoe-discover script
120 all network interfaces may be used for ATA over Ethernet. Here is a
|
| /linux-3.4.99/Documentation/ABI/stable/ |
| D | sysfs-class-backlight | 49 interfaces are available for a single device, firmware
54 backlight state. Platform interfaces are mostly a
56 interfaces.
|
| /linux-3.4.99/drivers/net/can/usb/ |
| D | Kconfig | 1 menu "CAN USB interfaces"
17 tristate "PEAK PCAN-USB/USB Pro interfaces"
|
| /linux-3.4.99/sound/usb/ |
| D | Kconfig | 30 audio/MIDI interfaces.
43 interfaces or controllers US-122, US-224 and US-428.
54 Say Y here to include support for caiaq USB audio interfaces,
98 interfaces.
|
| /linux-3.4.99/net/8021q/ |
| D | Kconfig | 8 Select this and you will be able to create 802.1Q VLAN interfaces
9 on your ethernet interfaces. 802.1Q VLAN supports almost
|
| /linux-3.4.99/drivers/staging/tidspbridge/Documentation/ |
| D | README | 35 through standard driver interfaces. Therefore, to allow multiple GPP
39 Since driver interfaces are not always standard across GPP OS, and to provide
43 driver interfaces, applications (and even other device drivers) can use the
62 Tasks started by the RM Server communicate using the STRM and NODE interfaces
|
| /linux-3.4.99/Documentation/ide/ |
| D | ide.txt | 15 *** PCI versions of the CMD640 and RZ1000 interfaces are now detected
33 *** interfaces, one *MUST* use the "cmd640.probe_vlb" kernel option.
56 It supports up to 9 IDE interfaces per default, on one or more IRQs (usually
66 To access devices on interfaces > ide0, device entries please make sure that
70 This driver automatically probes for most IDE interfaces (including all PCI
71 ones), for the drives/geometries attached to those interfaces, and for the IRQ
72 lines being used by the interfaces (normally 14, 15 for ide0/ide1).
74 Any number of interfaces may share a single IRQ if necessary, at a slight
144 be a separate MS-DOS driver just for the controller. IDE interfaces
|
| /linux-3.4.99/Documentation/virtual/kvm/ |
| D | review-checklist.txt | 29 10. User/kernel interfaces and guest/host interfaces must be 64-bit clean
|
| /linux-3.4.99/Documentation/video4linux/ |
| D | README.pvrusb2 | 39 interfaces appropriately as devices are hotplugged in the
42 3. High level interfaces which glue the driver to various published
89 interfaces tie into the driver through this module. This module
92 instances of multiple interfaces (thus you can for example change
122 interfaces (e.g. V4L, sysfs, etc), and in fact even those high
123 level interfaces are restricted to the API defined in
127 controlling the hardware. High level interfaces (e.g. V4L, sysfs)
163 through one of the high level interfaces).
|
| /linux-3.4.99/Documentation/watchdog/ |
| D | wdt.txt | 10 All the interfaces provide /dev/watchdog, which when open must be written
46 The external event interfaces on the WDT boards are not currently supported.
|
| /linux-3.4.99/sound/soc/blackfin/ |
| D | Kconfig | 9 You will also need to select the audio interfaces to support below.
54 interfaces are connected to the first SPORT port on the BF5XX board.
80 You will also need to select the audio interfaces to support below.
110 You will also need to select the audio interfaces to support below.
|
| /linux-3.4.99/Documentation/x86/ |
| D | pat.txt | 22 attributes at the page level. In order to avoid aliasing, these interfaces
23 should be used thoughtfully. Below is a table of interfaces available,
122 interfaces. Users writing to /proc/mtrr are suggested to use above interfaces.
|
| /linux-3.4.99/drivers/gpu/drm/udl/ |
| D | Kconfig | 12 Say M/Y to add support for these devices via drm/kms interfaces.
|