| /linux-4.4.14/net/ipv6/netfilter/ |
| D | ip6t_frag.c | 63 pr_debug("ID %u %08X\n", ntohl(fh->identification), in frag_mt6()
64 ntohl(fh->identification)); in frag_mt6()
68 ntohl(fh->identification), in frag_mt6()
93 ntohl(fh->identification), in frag_mt6()
|
| D | nf_log_ipv6.c | 111 ntohl(fh->identification)); in dump_ipv6_packet()
|
| D | nf_conntrack_reasm.c | 604 fq = fq_find(net, fhdr->identification, user, &hdr->saddr, &hdr->daddr, in nf_ct_frag6_gather()
|
| D | Kconfig | 129 ip6tables is a general, extensible packet identification framework.
|
| /linux-4.4.14/Documentation/video4linux/bttv/ |
| D | Tuners | 15 SAMSUNG Tuner identification: (e.g. TCPM9091PD27)
42 Philips Tuner identification: (e.g. FM1216MF)
65 Temic Tuner identification: (.e.g 4006FH5)
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/ |
| D | versatile-sysreg.txt | 5 platform functions like board detection and identification, software
|
| D | vexpress-sysreg.txt | 5 platform functions like board detection and identification, software
|
| D | cpus.txt | 50 identification register.
59 identification.
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-class-net-janz-ican3 | 18 Read-only: 32 byte string identification of the ICAN3 module
|
| D | sysfs-driver-genwqe | 4 Description: Unique bitstream identification e.g.
|
| /linux-4.4.14/Documentation/devicetree/bindings/power/ |
| D | rx51-battery.txt | 12 * "bsi" - The ADC channel for battery size identification
|
| /linux-4.4.14/Documentation/fmc/ |
| D | 00-INDEX | 26 - how identification and matching works
|
| D | fmc-write-eeprom.txt | 13 other than the identification, later versions of this packages added
|
| D | carrier.txt | 13 The contents of the EEPROM within the FMC are used for identification
115 * mezzanine_name: filled by fmc-bus during identification.
|
| D | mezzanine.txt | 93 identification numbers. For PIC, for example, `0x0400' represents
|
| D | identifiers.txt | 5 identification information in an I2C EEPROM. The information must be
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | ds1621 | 76 Since there is no version or vendor identification register, there is
77 no unique identification for these devices. Therefore, explicit device
78 instantiation is required for correct device identification and functionality
|
| D | adm9240 | 34 identification code as well as the chip revision/stepping level.
|
| /linux-4.4.14/Documentation/acpi/ |
| D | enumeration.txt | 376 identification string in the Device Tree (DT) namespace, especially if that ID
380 In ACPI, the device identification object called _CID (Compatible ID) is used to
390 existing DT-compatible device identification in ACPI and to satisfy the above
395 device identification algorithm. If the "compatible" property is not present
400 driver) and the identification strings from the "compatible" property value will
405 the identification strings listed by the "compatible" property value (if present
|
| D | gpio-properties.txt | 61 In those cases ACPI device identification objects, _HID, _CID, _CLS, _SUB, _HRV,
|
| D | namespace.txt | 261 is derived from the _HID/_CID identification objects present under
295 The linking mechanism relies on device identification provided by the
|
| /linux-4.4.14/net/ipv6/ |
| D | udp_offload.c | 117 fptr->identification = skb_shinfo(skb)->ip6_frag_id; in udp6_ufo_fragment()
|
| D | ip6_output.c | 664 fh->identification = frag_id; in ip6_fragment()
691 fh->identification = frag_id; in ip6_fragment()
801 fh->identification = frag_id; in ip6_fragment()
|
| D | reassembly.c | 555 fq = fq_find(net, fhdr->identification, &hdr->saddr, &hdr->daddr, in ipv6_frag_rcv()
|
| /linux-4.4.14/drivers/staging/iio/Documentation/ |
| D | inkernel.txt | 20 consumer_dev_name allows identification of the consumer device.
|
| /linux-4.4.14/Documentation/virtual/kvm/ |
| D | s390-diag.txt | 61 General register 2 contains a subchannel-identification word denoting
|
| /linux-4.4.14/drivers/firmware/ |
| D | Kconfig | 114 bool "Export DMI identification via sysfs to userspace"
118 Say Y here if you want to query SMBIOS/DMI system identification
|
| /linux-4.4.14/tools/usb/usbip/ |
| D | README | 24 Contains USB device identification data.
|
| /linux-4.4.14/Documentation/trace/ |
| D | stm.txt | 47 with "user" identification string will be allocated a master and
|
| /linux-4.4.14/net/ipv4/netfilter/ |
| D | Kconfig | 182 iptables is a general, extensible packet identification framework.
394 arptables is a general, extensible packet identification framework.
|
| /linux-4.4.14/drivers/s390/char/ |
| D | Kconfig | 87 identification. This is commonly used for workload management and
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | ceph.txt | 62 the identification of large disk space consumers relatively quick, as
|
| D | xfs-self-describing-metadata.txt | 333 identification of the buffer - that they contain inodes or dquots, and that
|
| D | ext2.txt | 125 such as a volume name, a unique identification number, the inode size,
|
| D | coda.txt | 281 structure contains the identification of P, the message sequence
|
| /linux-4.4.14/net/bridge/netfilter/ |
| D | Kconfig | 32 ebtables is a general, extensible frame/packet identification
|
| /linux-4.4.14/ |
| D | REPORTING-BUGS | 106 summary from [1.]>" for easy identification by the developers.
|
| /linux-4.4.14/Documentation/networking/ |
| D | lapb-module.txt | 107 generated by the device driver to allow for the unique identification of the
|
| D | openvswitch.txt | 138 flow identification is a unique flow identifier, or "UFID". UFIDs are optional
|
| D | scaling.txt | 204 identification of large flows and fewer false positives. The default
|
| /linux-4.4.14/arch/arm/boot/dts/ |
| D | tegra30-cardhu.dtsi | 14 * The identification of board is done in two ways, by looking the sticker
|
| /linux-4.4.14/Documentation/ioctl/ |
| D | hdio.txt | 28 HDIO_GET_IDENTITY get IDE identification info
234 HDIO_GET_IDENTITY get IDE identification info
|
| /linux-4.4.14/Documentation/ide/ |
| D | ide.txt | 99 probe/identification sequence. For example:
|
| D | ChangeLog.ide-cd.1994-2004 | 105 * 3.15a July 9, 1996 -- Improved Sanyo 3 CD changer identification
|
| /linux-4.4.14/Documentation/fb/ |
| D | api.txt | 157 char id[16]; /* identification string eg "TT Builtin" */
|
| /linux-4.4.14/include/net/ |
| D | ipv6.h | 109 __be32 identification; member
|
| /linux-4.4.14/Documentation/crypto/ |
| D | asymmetric-keys.txt | 8 - Key identification.
|
| /linux-4.4.14/Documentation/serial/ |
| D | driver | 297 indicates that the port requires detection and identification.
|
| /linux-4.4.14/Documentation/i2c/ |
| D | writing-clients | 214 (typically using device-specific, dedicated identification registers),
|
| /linux-4.4.14/Documentation/input/ |
| D | multi-touch-protocol.txt | 334 unique identification of a contact maintained over an extended period of
|
| /linux-4.4.14/Documentation/blockdev/ |
| D | paride.txt | 142 protocol identification number and, for some devices, the drive's
|
| /linux-4.4.14/Documentation/ |
| D | xillybus.txt | 208 * channelnum: The pipe's identification number in communication between the
|
| D | kernel-parameters.txt | 2307 [NFSv4.1] Send client implementation identification
2309 If zero, no implementation identification information
2311 The default is to send the implementation identification
|
| /linux-4.4.14/Documentation/usb/ |
| D | WUSB-Design-overview.txt | 370 descriptor that gives us the status of the transfer, its identification
|
| /linux-4.4.14/Documentation/devicetree/ |
| D | usage-model.txt | 91 1) platform identification,
|
| /linux-4.4.14/drivers/media/i2c/ |
| D | Kconfig | 170 seeing radio station identification transmitted using this
|
| /linux-4.4.14/Documentation/scsi/ |
| D | ChangeLog.megaraid | 25 Fix: Made change in the function inserting identification machanism
|
| D | ChangeLog.1992-1997 | 328 Improvements in HBA identification. Various other minor stuff.
405 configurable. Improvements in HBA identification.
|
| /linux-4.4.14/Documentation/isdn/ |
| D | README.HiSax | 266 programs and for identification when using a line monitor
|
| D | INTERFACE | 202 identification of the driver by the user. Eg.: it is shown in the
|
| /linux-4.4.14/Documentation/PCI/ |
| D | pci.txt | 553 All PCI layer functions use this identification and it's the only
|
| /linux-4.4.14/Documentation/spi/ |
| D | spi-summary | 331 basic device identification probes, so they should hotplug normally.
|
| /linux-4.4.14/Documentation/sysctl/ |
| D | kernel.txt | 134 x86 bootloader identification
|