| /openbmc/linux/net/ipv6/netfilter/ |
| H A D | ip6t_frag.c | 60 pr_debug("ID %u %08X\n", ntohl(fh->identification), in frag_mt6()
61 ntohl(fh->identification)); in frag_mt6()
65 ntohl(fh->identification), in frag_mt6()
89 ntohl(fh->identification), in frag_mt6()
|
| /openbmc/u-boot/drivers/led/ |
| H A D | Kconfig | 109 int "identification"
143 int "identification"
178 int "identification"
213 int "identification"
248 int "identification"
283 int "identification"
334 int "Red LED identification"
348 int "Yellow LED identification"
362 int "Blue LED identification"
376 int "Green LED identification"
|
| /openbmc/openbmc/poky/meta/recipes-devtools/python/ |
| H A D | python3-magic_0.4.27.bb | 1 SUMMARY = "File type identification using libmagic"
3 identification library. It makes use of the local magic database and supports \
|
| /openbmc/openbmc/poky/meta/recipes-support/hwdata/ |
| H A D | hwdata_0.391.bb | 1 SUMMARY = "Hardware identification and configuration data"
2 DESCRIPTION = "hwdata contains various hardware identification and \
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-driver-input-exc3000 | 13 Description: Reports the model identification provided by the touchscreen, for example "Orion_13…
22 Description: Reports the type identification provided by the touchscreen, for example "PCAP82H80 Se…
|
| H A D | configfs-acpi | 40 - ASCII OEM identification
43 - ASCII OEM table identification
|
| H A D | sysfs-devices-soc | 30 this will contain the JEDEC JEP106 manufacturer’s identification
34 This manufacturer’s identification code is defined by one
38 the maximum number of identification codes, a continuation
|
| H A D | sysfs-class-net-janz-ican3 | 18 Read-only: 32 byte string identification of the ICAN3 module
|
| H A D | sysfs-ibft | 31 identification of the creator of the table which is useful in
|
| /openbmc/linux/Documentation/driver-api/media/drivers/ |
| H A D | tuners.rst | 21 - Samsung Tuner identification: (e.g. TCPM9091PD27)
51 Philips Tuner identification: (e.g. FM1216MF)
77 Temic Tuner identification: (.e.g 4006FH5)
|
| /openbmc/linux/tools/testing/selftests/drivers/net/mlxsw/ |
| H A D | devlink_trap_tunnel_vxlan.sh | 148 )"00:00:"$( : IP identification
204 )"00:00:"$( : IP identification
287 )"00:00:"$( : IP identification
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | DRL-1.1 | 7 identification of the authors(s) ("author" field) of the Rule and any others designated to receive …
15 identification of the authors(s) ("author" field) of the Rule and any others designated to receive …
|
| H A D | gnuplot | 8 …2. add special version identification to distinguish your version in addition to the base release …
|
| H A D | DRL-1.0 | 6 identification of the authors(s) ("author" field) of the Rule and any others designated to receive …
|
| /openbmc/openbmc/poky/meta/recipes-core/os-release/ |
| H A D | os-release.bb | 3 SUMMARY = "Operating system identification"
4 DESCRIPTION = "The /usr/lib/os-release file contains operating system identification data."
|
| /openbmc/linux/Documentation/devicetree/bindings/soc/xilinx/ |
| H A D | xlnx,vcu.txt | 17 - clock-names: The identification string, "aclk", is always required for
|
| /openbmc/linux/Documentation/firmware-guide/acpi/ |
| H A D | enumeration.rst | 453 The Device Tree protocol uses device identification based on the "compatible"
456 regarded as a device identification namespace analogous to the ACPI/PNP device
459 identification string in the Device Tree (DT) namespace, especially if that ID
463 In ACPI, the device identification object called _CID (Compatible ID) is used to
467 Moreover, the specification mandates that either a _HID or an _ADR identification
473 existing DT-compatible device identification in ACPI and to satisfy the above
478 device identification algorithm. If the "compatible" property is not present
483 driver) and the identification strings from the "compatible" property value will
488 the identification strings listed by the "compatible" property value (if present
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | ds1621.rst | 95 Since there is no version or vendor identification register, there is
96 no unique identification for these devices. Therefore, explicit device
97 instantiation is required for correct device identification and functionality
|
| /openbmc/u-boot/doc/ |
| H A D | README.fsl-esdhc | 4 Support Freescale adapter card type identification. This is implemented by
|
| /openbmc/qemu/docs/system/i386/ |
| H A D | hyperv.rst | 33 identification (CPUID 0x40000000..0x4000000A) to Hyper-V. KVM identification
125 This changes Hyper-V identification in CPUID 0x40000000.EBX-EDX from the default
130 identification when specified without some other enlightenment.
202 This changes Hyper-V version identification in CPUID 0x40000002.EAX-EDX from the
213 identification when specified without any other enlightenments.
|
| H A D | xen.rst | 31 When Xen support is enabled, QEMU changes hypervisor identification (CPUID
32 0x40000000..0x4000000A) to Xen. The KVM identification and features are not
33 advertised to a Xen guest. If Hyper-V is also enabled, the Xen identification
|
| /openbmc/openbmc/meta-openembedded/meta-oe/licenses/ |
| H A D | gnuplot | 17 * 2. add special version identification to distinguish your version
|
| /openbmc/linux/Documentation/devicetree/bindings/mtd/partitions/ |
| H A D | brcm,trx.txt | 9 identification fields, CRC32 checksum and the locations of embedded partitions.
|
| /openbmc/linux/Documentation/userspace-api/media/mediactl/ |
| H A D | media-ioc-setup-link.rst | 35 :c:type:`media_link_desc` with link identification
|
| /openbmc/linux/tools/perf/Documentation/ |
| H A D | jitdump-specification.txt | 44 * uint32_t pid : JIT runtime process identification (OS specific)
74 * uint32_t tid: OS thread identification of the runtime thread generating the jitted code
100 …* uint32_t tid : OS thread identification of the runtime thread generating the jitted code
|