Home
last modified time | relevance | path

Searched refs:protocols (Results 1 – 159 of 159) sorted by relevance

/linux-4.4.14/drivers/block/paride/
Dparide.c41 static struct pi_protocol *protocols[MAX_PROTOS]; variable
215 if (protocols[k] && !strcmp(pr->name, protocols[k]->name)) { in paride_register()
221 while ((k < MAX_PROTOS) && (protocols[k])) in paride_register()
227 protocols[k] = pr; in paride_register()
239 if (protocols[pr->index] != pr) { in paride_unregister()
243 protocols[pr->index] = NULL; in paride_unregister()
360 if (!protocols[0]) in pi_init()
367 (!protocols[s]) || (unit < 0) || in pi_init()
368 (unit >= protocols[s]->max_units)) { in pi_init()
374 struct pi_protocol *proto = protocols[p]; in pi_init()
DKconfig251 tristate "KingByte KBIC-951A/971A protocols"
255 port IDE protocols from KingByte Information Corp. KingByte's
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-class-rc18 What: /sys/class/rc/rcN/protocols
23 Reading this file returns a list of available protocols,
26 Enabled protocols are shown in [] brackets.
28 protocols.
30 protocols.
32 Writing "none" will disable all protocols.
69 Reading this file returns a list of available protocols to use
74 wakeup protocols.
76 wakeup protocols.
Dsysfs-bus-hsi11 the protocols available in the system. Bus drivers implement
12 those protocols.
Dsysfs-platform-kim40 When one of the protocols Bluetooth, FM or GPS wants to make
Dsysfs-block203 protocols also have inherent limits on the number of
/linux-4.4.14/drivers/media/rc/img-ir/
Dimg-ir-sony.c58 struct img_ir_filter *out, u64 protocols) in img_ir_sony_filter() argument
76 if (!(protocols & RC_BIT_SONY20)) in img_ir_sony_filter()
82 if (!(protocols & RC_BIT_SONY15)) in img_ir_sony_filter()
Dimg-ir-rc5.c44 struct img_ir_filter *out, u64 protocols) in img_ir_rc5_filter() argument
DKconfig18 testing, debug, and to make more protocols available.
34 NEC protocols in the ImgTec infrared decoder block.
Dimg-ir-rc6.c65 struct img_ir_filter *out, u64 protocols) in img_ir_rc6_filter() argument
Dimg-ir-jvc.c33 struct img_ir_filter *out, u64 protocols) in img_ir_jvc_filter() argument
Dimg-ir-sharp.c42 struct img_ir_filter *out, u64 protocols) in img_ir_sharp_filter() argument
Dimg-ir-sanyo.c54 struct img_ir_filter *out, u64 protocols) in img_ir_sanyo_filter() argument
Dimg-ir-nec.c55 struct img_ir_filter *out, u64 protocols) in img_ir_nec_filter() argument
Dimg-ir-hw.h182 struct img_ir_filter *out, u64 protocols);
/linux-4.4.14/net/netfilter/ipvs/
Dip_vs_proto.c357 char protocols[64]; in ip_vs_protocol_init() local
361 strcat(protocols, ", "); \ in ip_vs_protocol_init()
362 strcat(protocols, (p)->name); \ in ip_vs_protocol_init()
365 protocols[0] = '\0'; in ip_vs_protocol_init()
366 protocols[2] = '\0'; in ip_vs_protocol_init()
382 pr_info("Registered protocols (%s)\n", &protocols[2]); in ip_vs_protocol_init()
/linux-4.4.14/net/nfc/
Ddigital_core.c477 tm_protocols, ddev->protocols); in digital_start_poll()
479 matching_im_protocols = ddev->protocols & im_protocols; in digital_start_poll()
480 matching_tm_protocols = ddev->protocols & tm_protocols; in digital_start_poll()
775 ddev->protocols |= NFC_PROTO_JEWEL_MASK; in nfc_digital_allocate_device()
777 ddev->protocols |= NFC_PROTO_MIFARE_MASK; in nfc_digital_allocate_device()
779 ddev->protocols |= NFC_PROTO_FELICA_MASK; in nfc_digital_allocate_device()
781 ddev->protocols |= NFC_PROTO_NFC_DEP_MASK; in nfc_digital_allocate_device()
783 ddev->protocols |= NFC_PROTO_ISO15693_MASK; in nfc_digital_allocate_device()
785 ddev->protocols |= NFC_PROTO_ISO14443_MASK; in nfc_digital_allocate_device()
787 ddev->protocols |= NFC_PROTO_ISO14443_B_MASK; in nfc_digital_allocate_device()
[all …]
Ddigital_dep.c426 if ((ddev->protocols & NFC_PROTO_FELICA_MASK) && in digital_in_recv_atr_res()
/linux-4.4.14/arch/powerpc/sysdev/qe_lib/
DKconfig10 protocols: UART, BISYNC, QMC
17 protocols: HDLC, Ethernet, ATM, transparent
/linux-4.4.14/drivers/media/rc/
Drc-ir-raw.c236 u64 protocols; in ir_raw_get_allowed_protocols() local
238 protocols = available_protocols; in ir_raw_get_allowed_protocols()
240 return protocols; in ir_raw_get_allowed_protocols()
330 available_protocols |= ir_raw_handler->protocols; in ir_raw_handler_register()
346 available_protocols &= ~ir_raw_handler->protocols; in ir_raw_handler_unregister()
Dir-sharp-decoder.c178 .protocols = RC_BIT_SHARP,
Drc-main.c923 static int parse_protocol_change(u64 *protocols, const char *buf) in parse_protocol_change() argument
967 *protocols |= mask; in parse_protocol_change()
969 *protocols &= ~mask; in parse_protocol_change()
971 *protocols = mask; in parse_protocol_change()
1229 static RC_PROTO_ATTR(protocols, S_IRUGO | S_IWUSR,
Dir-sanyo-decoder.c182 .protocols = RC_BIT_SANYO,
Drc-core-priv.h26 u64 protocols; /* which are handled by this handler */ member
Dir-jvc-decoder.c177 .protocols = RC_BIT_JVC,
Dir-sony-decoder.c177 .protocols = RC_BIT_SONY12 | RC_BIT_SONY15 | RC_BIT_SONY20,
Dir-rc5-decoder.c188 .protocols = RC_BIT_RC5 | RC_BIT_RC5X | RC_BIT_RC5_SZ,
Dir-nec-decoder.c204 .protocols = RC_BIT_NEC,
Dir-xmp-decoder.c202 .protocols = RC_BIT_XMP,
Dir-rc6-decoder.c295 .protocols = RC_BIT_RC6_0 | RC_BIT_RC6_6A_20 |
Dir-lirc-codec.c424 .protocols = 0,
Dir-mce_kbd-decoder.c425 .protocols = RC_BIT_MCE_KBD,
/linux-4.4.14/drivers/nfc/st-nci/
Dcore.c130 u32 protocols; in st_nci_probe() local
137 protocols = NFC_PROTO_JEWEL_MASK in st_nci_probe()
145 ndlc->ndev = nci_allocate_device(&st_nci_ops, protocols, in st_nci_probe()
/linux-4.4.14/Documentation/i2c/
Dsummary12 a subset of I2C protocols and signaling. Many I2C devices will work on an
13 SMBus, but some SMBus protocols add semantics beyond what is required to
19 use its protocols on many I2C systems. However, there are systems that don't
Di2c-protocol86 Force a stop condition (P) after the message. Some I2C related protocols
Ddev-interface88 Note that only a subset of the I2C and SMBus protocols can be achieved by
/linux-4.4.14/drivers/nfc/nfcmrvl/
Dmain.c113 u32 protocols; in nfcmrvl_nci_register_dev() local
144 protocols = NFC_PROTO_JEWEL_MASK in nfcmrvl_nci_register_dev()
152 priv->ndev = nci_allocate_device(&nfcmrvl_nci_ops, protocols, in nfcmrvl_nci_register_dev()
/linux-4.4.14/tools/usb/usbip/libsrc/
Dnames.c99 static struct protocol *protocols[HASHSZ] = { NULL, }; variable
150 p = protocols[hashnum((classid << 16) | (subclassid << 8) in names_protocol()
292 p = protocols[h]; in new_protocol()
304 p->next = protocols[h]; in new_protocol()
305 protocols[h] = p; in new_protocol()
/linux-4.4.14/Documentation/
Dsmsc_ece1099.txt43 only supports four protocols.
45 The Write Byte, Read Byte, Send Byte, and Receive Byte protocols are the
46 only valid SMBus protocols for the device.
Dpnp.txt95 All Plug and Play drivers, protocols, and services meet at a central location
97 information between PnP drivers and PnP protocols. Thus it automatically
Dcrc32.txt9 protocols put the end-of-frame flag after the CRC.
/linux-4.4.14/Documentation/isdn/
DREADME.concap25 several different encapsulation protocols at once.
28 encapsulation protocols. The encapsulation protocol is configured by a
48 Many Encapsulation protocols used on top of WAN connections will not just
53 Such encapsulation protocols for WAN devices are typically more complex
54 than encapsulation protocols for lan devices. Thus, network interface
79 encapsulation protocols will need to control the connection. Therefore,
145 A Network interface using encapsulation protocols must also provide
228 protocols (e.g. by a member struct concap_proto* in struct net_device)
DREADME.avmb139 protocols (b1.t4 for Euro-ISDN). Install these file in /lib/isdn.
DREADME.hysdn52 handlers for various protocols like ppp and others as well as config info
DREADME310 requested protocols for the B-channel. If a net-interface, however
510 possible too. See README.x25 for x25 related l2 protocols.)
DREADME.sc56 protocols and offers channel bundling and MLPPP support. To use ISDN4Linux
DINTERFACE62 report the supported layer2 and layer3-protocols. For setting this
/linux-4.4.14/net/x25/
DKconfig8 X.25 is a set of standardized network protocols, similar in scope to
15 protocols: the higher level Packet Layer Protocol (PLP) (say Y here
/linux-4.4.14/net/irda/
DKconfig10 Say Y here if you want to build support for the IrDA (TM) protocols.
14 To use Linux support for the IrDA (tm) protocols, you will also need
27 comment "IrDA protocols"
/linux-4.4.14/drivers/infiniband/hw/mlx5/
DKconfig7 This is required to use InfiniBand protocols such as
/linux-4.4.14/drivers/infiniband/hw/mlx4/
DKconfig9 This is required to use InfiniBand protocols such as
/linux-4.4.14/net/netlabel/
DKconfig11 protocols such as CIPSO and RIPSO. For more information see
/linux-4.4.14/Documentation/devicetree/bindings/sound/
Dtpa6130a2.txt3 The tpa6130a2 serial control bus communicates through I2C protocols
Dtlv320aic32x4.txt3 The tlv320aic32x4 serial control bus communicates through I2C protocols
Dtas2552.txt3 The tas2552 serial control bus communicates through I2C protocols
Dtlv320aic3x.txt3 The tlv320aic3x serial control bus communicates through I2C protocols
Dtlv320aic31xx.txt3 The tlv320aic31xx serial control bus communicates through I2C protocols
/linux-4.4.14/Documentation/networking/
Dnfc.txt57 of the set of supported NFC protocols and the set of ops callbacks. The ops
88 protocols through NFC_ATTR_PROTOCOLS attribute. The device remains in polling
96 relevant information such as the supported NFC protocols.
Dirda.txt1 To use the IrDA protocols within Linux you will need to get a suitable copy
Dax25.txt1 To use the amateur radio protocols within Linux you will need to get a
Dopenvswitch.txt29 Network protocols evolve over time. New protocols become important
30 and existing protocols lose their prominence. For the Open vSwitch
32 versions to parse additional protocols as part of the flow key. It
34 protocols that have become obsolete. Therefore, the Netlink interface
Dieee802154.txt14 of the IEEE 802.15.4 and 6LoWPAN protocols. IEEE 802.15.4 is a stack
15 of protocols for organizing Low-Rate Wireless Personal Area Networks.
Dtcp-thin.txt4 protocols display what we call thin-stream properties. This means
Di40e.txt54 other protocols besides TCP. It's also safe to use with configurations that
Dipvs-sysctl.txt165 unrecognized protocols. This prevents us from routing tunneled
166 protocols like ipip, which is useful to prevent rescheduling
Dnetdevices.txt26 include any link layer protocol overhead. Upper layer protocols must
Dnf_conntrack-sysctl.txt79 protocols.
Dcan.txt34 4.3 connected transport protocols (SOCK_SEQPACKET)
35 4.4 unconnected transport protocols (SOCK_DGRAM)
63 The socketcan package is an implementation of CAN protocols
70 as similar as possible to the TCP/IP protocols to allow programmers,
84 Queueing of frames and higher-level transport protocols like ISO-TP
101 that any number of transport protocols can be loaded or unloaded
246 call. Currently, there are two CAN protocols to choose from, the raw
293 /* reserved for future CAN protocols address information */
846 4.3 connected transport protocols (SOCK_SEQPACKET)
847 4.4 unconnected transport protocols (SOCK_DGRAM)
Dray_cs.txt130 useful for debugging 802.11 lowlevel protocols that are not visible to
Dx25-iface.txt85 call in question. But many upper layer protocols are not designed to
Darcnet.txt269 LAN Manager and Windows for Workgroups: These programs use protocols that
307 The ARCnet driver v2.10 ALPHA supports three protocols, each on its own
313 protocol. arc0 is the fastest of the three protocols (for
358 two available protocols. As mentioned above, it's a good idea to use
Dbatman-adv.txt179 the virtual switch are completely transparent for all protocols
Dtimestamping.txt97 acknowledged. This only makes sense for reliable protocols. It is
200 byte range can coexist in multiple segments for protocols that
Dudplite.txt259 If you copy and paste the following line into /etc/protocols,
Ddecnet.txt35 network protocols.
Dixgbe.txt230 other protocols besides TCP. It's also safe to use with configurations that
Dip-sysctl.txt32 protocols for which pmtu events will be honored are TCP, SCTP
37 protocols should be discarded. If enabled globally this mode
38 could break other protocols.
499 This value overrides net.core.rmem_default used by other protocols.
648 value overrides net.core.wmem_default used by other protocols.
Dscaling.txt109 2) software filters can easily be added to hash over new protocols,
Dbonding.txt2335 If you are utilizing protocols other than TCP/IP, UDP for
/linux-4.4.14/Documentation/netlabel/
Dlsm_interface.txt11 use of a common code base for several different packet labeling protocols.
17 Since NetLabel supports multiple different packet labeling protocols and LSMs
/linux-4.4.14/Documentation/w1/masters/
Domap-hdq16 Semiconductor 1-Wire protocols. These protocols use a single wire for
/linux-4.4.14/net/phonet/
DKconfig6 tristate "Phonet protocols family"
/linux-4.4.14/drivers/nfc/
Dport100.c1031 struct port100_protocol *protocols; in port100_in_set_framing() local
1041 protocols = in_protocols[param]; in port100_in_set_framing()
1044 while (protocols[num_protocols].number != PORT100_IN_PROT_END) in port100_in_set_framing()
1056 memcpy(skb_put(skb, size), protocols, size); in port100_in_set_framing()
1189 struct port100_protocol *protocols; in port100_tg_set_framing() local
1199 protocols = tg_protocols[param]; in port100_tg_set_framing()
1202 while (protocols[num_protocols].number != PORT100_TG_PROT_END) in port100_tg_set_framing()
1214 memcpy(skb_put(skb, size), protocols, size); in port100_tg_set_framing()
Dnfcwilink.c502 __u32 protocols; in nfcwilink_probe() local
512 protocols = NFC_PROTO_JEWEL_MASK in nfcwilink_probe()
519 protocols, in nfcwilink_probe()
DKconfig34 device. Such device supports 5 different protocols: ISO14443A,
Dpn533.c3120 u32 protocols; in pn533_probe() local
3191 protocols = PN533_ALL_PROTOCOLS; in pn533_probe()
3195 protocols = PN533_NO_TYPE_B_PROTOCOLS; in pn533_probe()
3199 protocols = PN533_NO_TYPE_B_PROTOCOLS; in pn533_probe()
3228 dev->nfc_dev = nfc_allocate_device(&pn533_nfc_ops, protocols, in pn533_probe()
/linux-4.4.14/drivers/uwb/
DKconfig12 10m). It serves as the transport layer for other protocols,
16 protocols (such as WUSB) might impose a master/slave
/linux-4.4.14/drivers/isdn/
DKconfig32 suitable for German BTX. On D-Channel, the protocols EDSS1
51 and data connections, controlling call options and protocols,
/linux-4.4.14/Documentation/devicetree/bindings/serial/
Ddigicolor-usart.txt4 UART. USART also support synchronous serial protocols like SPI and I2S. Use
/linux-4.4.14/drivers/staging/rdma/ipath/
DKconfig8 devices to be used with both kernel upper level protocols such
/linux-4.4.14/net/ax25/
DKconfig2 # Amateur Radio protocols and AX.25 device configuration
18 comment "Packet Radio protocols"
27 carry other protocols such as tcp/ip. To use it, you need a device
/linux-4.4.14/net/lapb/
DKconfig11 it is used to transport higher level protocols (mostly X.25 Packet
/linux-4.4.14/fs/cifs/
DKconfig26 protocols for CIFS including SMB3, which enables
180 family of protocols, including SMB3. SMB3 support is
182 options. These protocols are the successors to the popular
183 CIFS and SMB network file sharing protocols. SMB3 is the
Dcifssmb.c51 } protocols[] = { variable
64 } protocols[] = { variable
575 strncpy(pSMB->DialectsArray+count, protocols[i].name, 16); in CIFSSMBNegotiate()
576 count += strlen(protocols[i].name) + 1; in CIFSSMBNegotiate()
/linux-4.4.14/Documentation/nfc/
Dnfc-pn544.txt18 or the protocols are different.
Dnfc-hci.txt99 - target_from_gate() is an optional entrypoint to return the nfc protocols
/linux-4.4.14/net/l2tp/
DKconfig24 L2TPv3 allows other protocols as well as PPP to be carried
63 L2 protocols, including ATM, Frame Relay, HDLC and even raw
/linux-4.4.14/drivers/nfc/microread/
Dmicroread.c662 u32 protocols; in microread_probe() local
682 protocols = NFC_PROTO_JEWEL_MASK | in microread_probe()
690 quirks, protocols, llc_name, in microread_probe()
/linux-4.4.14/Documentation/usb/
Dohci.txt9 hardware register protocols used to talk to USB 1.1 host controllers. As
/linux-4.4.14/drivers/pnp/
DKconfig17 devices. You should then also say Y to all of the protocols below.
/linux-4.4.14/Documentation/memory-devices/
Dti-emif.txt26 supports one or more of DDR2, DDR3, and LPDDR2 SDRAM protocols.
/linux-4.4.14/include/net/nfc/
Ddigital.h205 u32 protocols; member
Dhci.h169 u32 protocols,
/linux-4.4.14/drivers/scsi/isci/
Dport.h136 struct sci_phy_proto protocols; member
Dphy.h453 struct sci_phy_proto *protocols);
Dport.c137 sci_port_get_protocols(iport, &prop->local.protocols); in sci_port_get_properties()
/linux-4.4.14/drivers/nfc/fdp/
Dfdp.c749 u32 protocols; in fdp_nci_probe() local
766 protocols = NFC_PROTO_JEWEL_MASK | in fdp_nci_probe()
774 ndev = nci_allocate_device(&nci_ops, protocols, tx_headroom, in fdp_nci_probe()
/linux-4.4.14/Documentation/devicetree/bindings/gpio/
Dspear_spics.txt7 desired by some of the device protocols above spi which expect (multiple)
/linux-4.4.14/Documentation/devicetree/bindings/memory-controllers/ti/
Demif.txt5 DDR2/DDR3/LPDDR2 protocols. This binding describes a given instance
/linux-4.4.14/drivers/infiniband/
DKconfig10 any protocols you wish to use as well as drivers for your
/linux-4.4.14/drivers/nfc/pn544/
Dpn544.c920 u32 protocols; in pn544_hci_probe() local
946 protocols = NFC_PROTO_JEWEL_MASK | in pn544_hci_probe()
954 protocols, llc_name, in pn544_hci_probe()
/linux-4.4.14/drivers/usb/
DREADME19 * Specifications for other protocols implemented by USB peripheral
/linux-4.4.14/drivers/nfc/st21nfca/
Dcore.c964 u32 protocols; in st21nfca_hci_probe() local
996 protocols = NFC_PROTO_JEWEL_MASK | in st21nfca_hci_probe()
1008 protocols, llc_name, in st21nfca_hci_probe()
/linux-4.4.14/Documentation/cgroups/
Dnet_prio.txt52 can then be managed by administrators or other networking protocols such as
Dmemory.txt318 * sockets memory pressure: some sockets protocols have memory pressure
/linux-4.4.14/net/atm/
DKconfig59 tristate "RFC1483/2684 Bridged protocols"
/linux-4.4.14/net/nfc/hci/
Dcore.c942 u32 protocols, in nfc_hci_allocate_device() argument
953 if (protocols == 0) in nfc_hci_allocate_device()
968 hdev->ndev = nfc_allocate_device(&hci_nfc_ops, protocols, in nfc_hci_allocate_device()
/linux-4.4.14/Documentation/filesystems/nfs/
Dnfsroot.txt142 which specify multiple autoconfiguration protocols,
143 requests are sent using all protocols, and the first one
146 Only autoconfiguration protocols that have been compiled
Drpc-server-gss.txt5 This document gives references to the standards and protocols used to
Dpnfs.txt95 (More protocols can be defined in the future.
/linux-4.4.14/net/
DKconfig63 These are the protocols used on the Internet and on most local
123 protocols, which a packet filter lacks. Moreover, proxy-based
153 protocols over the bridge, use ebtables (under bridge netfilter
/linux-4.4.14/Documentation/blockdev/
Dparide.txt70 support is available for almost all known adapter protocols:
95 of the parallel port communication protocols. If you do not know
193 this loads a base module which provides a registry for the protocols,
197 As you load each module, it will register the protocols that it supports,
/linux-4.4.14/Documentation/target/
Dtcmu-design.txt30 protocols. TCM also modularizes the data storage. There are existing
50 using standard protocols themselves.
58 the significant work to port the GLFS or RBD APIs and protocols to the
/linux-4.4.14/arch/unicore32/
DKconfig163 correct operation of some network protocols. With an IP-only
/linux-4.4.14/Documentation/infiniband/
Dcore_locking.txt6 protocols that use the midlayer.
/linux-4.4.14/drivers/memory/
DKconfig46 supports one or more of DDR2, DDR3, and LPDDR2 SDRAM protocols.
/linux-4.4.14/block/
DKconfig60 protocols (e.g. Task Management Functions and SMP in Serial
/linux-4.4.14/Documentation/spi/
Dspi-summary27 Unlike serial busses like USB or SMBus, even low level protocols for
31 - SPI may be used for request/response style device protocols, as with
50 SPI is only one of the names used by such four-wire protocols, and
52 half-duplex SPI, for request/response protocols), SSP ("Synchronous
54 related protocols.
Dspidev16 * Developing simple protocols used to talk to microcontrollers acting
/linux-4.4.14/drivers/message/fusion/
Dmptsas.c2981 u16 protocols; in mptsas_parse_device_info() local
2990 protocols = device_info->device_info & 0x78; in mptsas_parse_device_info()
2992 if (protocols & MPI_SAS_DEVICE_INFO_SSP_INITIATOR) in mptsas_parse_device_info()
2994 if (protocols & MPI_SAS_DEVICE_INFO_STP_INITIATOR) in mptsas_parse_device_info()
2996 if (protocols & MPI_SAS_DEVICE_INFO_SMP_INITIATOR) in mptsas_parse_device_info()
2998 if (protocols & MPI_SAS_DEVICE_INFO_SATA_HOST) in mptsas_parse_device_info()
3005 protocols = device_info->device_info & 0x780; in mptsas_parse_device_info()
3007 if (protocols & MPI_SAS_DEVICE_INFO_SSP_TARGET) in mptsas_parse_device_info()
3009 if (protocols & MPI_SAS_DEVICE_INFO_STP_TARGET) in mptsas_parse_device_info()
3011 if (protocols & MPI_SAS_DEVICE_INFO_SMP_TARGET) in mptsas_parse_device_info()
[all …]
/linux-4.4.14/drivers/i2c/
DKconfig88 tristate "SMBus-specific protocols" if !I2C_HELPER_AUTO
/linux-4.4.14/Documentation/block/
Ddata-integrity.txt12 protocols (SBC Data Integrity Field, SCC protection proposal) as well
94 transport protocols completely transparent to the application.
/linux-4.4.14/Documentation/filesystems/
D9p.txt114 afid security channel - used by Plan 9 authentication protocols
DLocking3 prototypes or locking protocols - update this file. And update the relevant
Dproc.txt66 It also only covers IPv4 networking, not IPv6 nor other protocols - sorry. But
/linux-4.4.14/Documentation/input/
Dntrig.txt7 and multi-touch events are translated to the appropriate protocols for
Dinput.txt204 ExplorerPS/2 (IntelliMouse Explorer) protocols, depending on what the
Dalps.txt62 v4 protocols.
/linux-4.4.14/crypto/
DKconfig259 IETF protocols.
485 in IETF protocols. This is the portable C implementation of Poly1305.
496 in IETF protocols. This is the x86_64 assembler implementation using SIMD
1238 Bernstein and further specified in RFC7539 for use in IETF protocols.
1253 Bernstein and further specified in RFC7539 for use in IETF protocols.
/linux-4.4.14/drivers/usb/gadget/legacy/
DKconfig254 This fabric is an USB gadget. Two USB protocols are supported that is
257 alternative interface 1. Both protocols can work on USB2.0 and USB3.0.
/linux-4.4.14/Documentation/networking/dsa/
Ddsa.txt67 Switch tagging protocols
70 DSA currently supports 4 different tagging protocols, and a tag-less mode as
71 well. The different protocols are implemented in:
/linux-4.4.14/Documentation/x86/
Dboot.txt95 0x10000 and end of low memory. Unfortunately, in protocols 2.00 and
208 (3) Ignored, but safe to set, for boot protocols 2.02-2.09.
549 ramdisk/ramfs contents. For boot protocols 2.02 or earlier, this
805 -> For the 2.00 and 2.01 boot protocols, the real-mode code
/linux-4.4.14/Documentation/hid/
Dhiddev.txt6 human interface device protocols for things that are not really human
/linux-4.4.14/net/ipv6/netfilter/
DKconfig24 which generalize ip_conntrack to support other layer 3 protocols.
/linux-4.4.14/Documentation/ide/
Dide.txt244 similar to SCSI protocols, created at the same time as the ATA2 standard.
/linux-4.4.14/net/ipv4/
DKconfig112 supplied on the kernel command line or by BOOTP or RARP protocols.
316 tristate "IP: Foo (IP protocols) over UDP"
/linux-4.4.14/net/ipv4/netfilter/
DKconfig24 which generalize ip_conntrack to support other layer 3 protocols.
/linux-4.4.14/drivers/net/wan/
DKconfig384 the asynchronous HDLS framing protocols in CCITT recommendation X.25.
/linux-4.4.14/drivers/spi/
DKconfig24 SPI is one of a family of similar protocols using a four wire
/linux-4.4.14/drivers/net/usb/
DKconfig271 transport for other protocols, usually an embedded AT channel.
/linux-4.4.14/net/netfilter/
DKconfig203 which generalize ip_conntrack to support other layer 3 protocols.
213 important VoIP protocols, it is widely used by voice hardware and
/linux-4.4.14/net/sched/
DKconfig202 testing applications or protocols.
/linux-4.4.14/drivers/gpio/
DKconfig69 non-sleeping contexts. They can make bitbanged serial protocols
/linux-4.4.14/
DCREDITS73 D: the humble start of an opening towards the IBM SNA protocols
396 D: AUN network protocols
3860 D: Minor debugging of other networking protocols.
/linux-4.4.14/Documentation/kbuild/
Dmakefiles.txt96 drivers, file systems, and network protocols. These people need to
/linux-4.4.14/arch/arm/
DKconfig1764 correct operation of some network protocols. With an IP-only
/linux-4.4.14/Documentation/s390/
DDebugging390.txt1380 logic to interface the channel paths & channel path IO protocols to
/linux-4.4.14/drivers/staging/speakup/
Dspkguide.txt1338 public has access to download using public-standard network protocols
/linux-4.4.14/Documentation/virtual/uml/
DUserModeLinux-HOWTO.txt381 as modules, especially filesystems and network protocols and filters,