Searched refs:UAPI (Results 1 – 25 of 28) sorted by relevance
12
| /linux-6.6.21/Documentation/userspace-api/media/ |
| D | Makefile | 7 UAPI = $(srctree)/include/uapi/linux macro
24 $(BUILDDIR)/ca.h.rst: ${UAPI}/dvb/ca.h ${PARSER} $(SRC_DIR)/ca.h.rst.exceptions
27 $(BUILDDIR)/dmx.h.rst: ${UAPI}/dvb/dmx.h ${PARSER} $(SRC_DIR)/dmx.h.rst.exceptions
30 $(BUILDDIR)/frontend.h.rst: ${UAPI}/dvb/frontend.h ${PARSER} $(SRC_DIR)/frontend.h.rst.exceptions
33 $(BUILDDIR)/net.h.rst: ${UAPI}/dvb/net.h ${PARSER} $(SRC_DIR)/net.h.rst.exceptions
36 $(BUILDDIR)/videodev2.h.rst: ${UAPI}/videodev2.h ${PARSER} $(SRC_DIR)/videodev2.h.rst.exceptions
39 $(BUILDDIR)/media.h.rst: ${UAPI}/media.h ${PARSER} $(SRC_DIR)/media.h.rst.exceptions
42 $(BUILDDIR)/cec.h.rst: ${UAPI}/cec.h ${PARSER} $(SRC_DIR)/cec.h.rst.exceptions
45 $(BUILDDIR)/lirc.h.rst: ${UAPI}/lirc.h ${PARSER} $(SRC_DIR)/lirc.h.rst.exceptions
|
| /linux-6.6.21/Documentation/userspace-api/ |
| D | iommu.rst | 8 IOMMU UAPI is used for virtualization cases where communications are
37 3. Extensions to the UAPI shall not break existing userspace
41 Although the data structures defined in IOMMU UAPI are self-contained,
42 there are no user API functions introduced. Instead, IOMMU UAPI is
47 When IOMMU UAPI gets extended, the data structures can *only* be
59 Version field is only reserved for the unlikely event of UAPI upgrade
71 When IOMMU UAPI extension results in some structure size increase,
72 IOMMU UAPI code shall handle the following cases:
75 2. An older user with older kernel header (smaller UAPI size) running on a
76 newer kernel (larger UAPI size)
[all …]
|
| /linux-6.6.21/Documentation/translations/zh_TW/process/ |
| D | license-rules.rst | 36 用戶空間API（UAPI）頭文件描述了用戶空間程序與內核的接口，這是一種特殊情況。
38 擴展到任何使用它與內核通信的軟體。由於UAPI頭文件必須包含在創建在Linux內核
97 當需要修正的許可證時，應使用WITH。 例如，linux內核UAPI文件使用表達式::
265 包含Linux內核的COPYING文件中記錄的Linux系統調用例外，該文件用於UAPI
|
| /linux-6.6.21/Documentation/translations/zh_CN/process/ |
| D | license-rules.rst | 33 用户空间API（UAPI）头文件描述了用户空间程序与内核的接口，这是一种特殊情况。
35 扩展到任何使用它与内核通信的软件。由于UAPI头文件必须包含在创建在Linux内核
94 当需要修正的许可证时，应使用WITH。 例如，linux内核UAPI文件使用表达式::
262 包含Linux内核的COPYING文件中记录的Linux系统调用例外，该文件用于UAPI
|
| /linux-6.6.21/tools/net/ynl/generated/ |
| D | Makefile | 22 all: protos.a $(HDRS) $(SRCS) $(KHDRS) $(KSRCS) $(UAPI) regen
|
| /linux-6.6.21/include/uapi/asm-generic/ |
| D | Kbuild | 4 # (This file is not included when SRCARCH=um since UML does not support UAPI.)
|
| /linux-6.6.21/Documentation/security/tpm/ |
| D | tpm_vtpm_proxy.rst | 44 UAPI chapter
|
| /linux-6.6.21/tools/bpf/bpftool/Documentation/ |
| D | bpftool-feature.rst | 81 as provided from libbpf (for all object types) or from the BPF UAPI
|
| D | bpftool-map.rst | 82 UAPI header for existing flags).
|
| /linux-6.6.21/Documentation/process/ |
| D | license-rules.rst | 32 The User-space API (UAPI) header files, which describe the interface of
36 communicate with the kernel. Because the UAPI headers must be includable
109 For example, the linux kernel UAPI files use the expression::
349 file of the Linux kernel, which is used for UAPI header files.
|
| D | deprecated.rst | 352 use in UAPI headers.) Those cases are when the flexible array is either
|
| /linux-6.6.21/Documentation/bpf/ |
| D | bpf_design_QA.rst | 319 the kernel will preserve backwards compatibility, as they are part of UAPI.
321 For kptrs, they are also part of UAPI, but only with respect to the kptr
323 pointer in your struct are NOT part of the UAPI contract. The supported types can
329 and added to bpf.h UAPI header, such types can and will arbitrarily change their
|
| D | drgn.rst | 8 kernel data structures. drgn is not relying on kernel UAPI to read the data.
|
| D | bpf_prog_run.rst | 23 to be defined in the UAPI header, aliased to the same value.
|
| D | bpf_devel_QA.rst | 292 and maps that are active in the kernel. If UAPI changes related to BPF
298 A: For UAPI changes related to the XDP or tc layer (e.g. ``cls_bpf``),
301 useful to have UAPI changes properly designed to be usable, but also
|
| /linux-6.6.21/Documentation/translations/it_IT/process/ |
| D | license-rules.rst | 38 I file d'intestazione per l'API verso lo spazio utente (UAPI) descrivono
43 d'intestazione UAPI devono poter essere inclusi nei sorgenti di un
121 licenza. Per esempio, la UAPI del kernel linux usa l'espressione::
362 per i file d'intestazione per la UAPI. Per esempio
|
| D | deprecated.rst | 388 intestazione UAPI). Uno è quando l'array flessibile è l'unico elemento di una
|
| /linux-6.6.21/drivers/firewire/ |
| D | Kconfig | 22 tristate "KUnit tests for layout of structure in UAPI" if !KUNIT_ALL_TESTS
|
| /linux-6.6.21/Documentation/block/ |
| D | ublk.rst | 104 command. It sets UAPI structure of ``ublksrv_ctrl_dev_info``,
240 UAPI structure of ``ublksrv_io_desc`` is defined for describing each IO from
|
| /linux-6.6.21/Documentation/admin-guide/media/ |
| D | rkisp1.rst | 21 in the UAPI and the revision of the ISP inside the running SoC can be read
|
| /linux-6.6.21/Documentation/driver-api/cxl/ |
| D | memory-devices.rst | 380 :doc: UAPI
|
| /linux-6.6.21/Documentation/gpu/ |
| D | drm-uapi.rst | 221 Requirements for KMS UAPI
240 Requirements for Render and Cross-Device UAPI
|
| D | drm-kms.rst | 300 Atomic Mode Setting IOCTL and UAPI Functions
|
| /linux-6.6.21/Documentation/networking/ |
| D | nexthop-group-resilient.rst | 160 Netlink UAPI
|
| /linux-6.6.21/Documentation/gpu/rfc/ |
| D | i915_vm_bind.rst | 242 VM_BIND UAPI
|
12