Searched full:headers (Results 1 – 25 of 157) sorted by relevance
1234567
| /Documentation/kbuild/ |
| D | headers_install.rst | 2 Exporting kernel headers for use by userspace
13 from the "linux" subdirectory. The system's libc headers are usually
14 installed at the default location /usr/include and the kernel headers in
18 Kernel headers are backwards compatible, but not forwards compatible. This
19 means that a program built against a C library using older kernel headers
21 features), but a program built against newer kernel headers may not work on an
30 ARCH indicates which architecture to produce headers for, and defaults to the
31 current architecture. The linux/asm directory of the exported kernel headers
37 INSTALL_HDR_PATH indicates where to install the headers. It defaults to
41 headers are installed in 'INSTALL_HDR_PATH/include'.
|
| D | gcc-plugins.rst | 71 It should be always included instead of individual gcc headers.
78 These headers automatically generate the registration structures for
86 You must install the gcc plugin headers for your gcc version,
106 Run gcc (native or cross-compiler) to ensure plugin headers are detected::
|
| /Documentation/userspace-api/media/v4l/ |
| D | metafmt-uvc.rst | 15 This format describes standard UVC metadata, extracted from UVC packet headers
19 in those headers. See section "2.4.3.3 Video and Still Image Payload Headers" of
23 contain multiple headers, if multiple such headers have been transmitted by the
24 camera for the respective frame. However, the driver may drop headers when the
27 perform rate limiting when the device sends a large number of headers.
|
| /Documentation/networking/ |
| D | segmentation-offloads.rst | 69 contain additional headers such as an outer tunnel. In order to account
73 cases where there are more than just 1 set of headers. For example in the
74 case of IPIP and SIT we should have the network and transport headers moved
75 from the standard list of headers to "inner" header offsets.
77 Currently only two levels of headers are supported. The convention is to
78 refer to the tunnel headers as the outer headers, while the encapsulated
79 data is normally referred to as the inner headers. Below is the list of
80 calls to access the given headers:
103 headers will be left with a partial checksum and only the outer header
138 so that instead of having to rewrite the packet headers for each segment
[all …]
|
| D | mac80211-injection.rst | 16 ./Documentation/networking/radiotap-headers.rst.
20 radiotap headers and used to control injection:
71 facilitating replay of captured radiotap headers directly.
|
| D | xfrm_device.rst | 140 The stack has already inserted the appropriate IPsec headers in the
148 IPsec headers are still in the packet data; they are removed later up
153 get spi, protocol, and destination IP from packet headers
176 HW adds and deletes XFRM headers. So in RX path, XFRM stack is bypassed if HW
|
| D | openvswitch.rst | 17 on packet headers and metadata to sets of actions. The most common
52 headers but userspace stopped at the Ethernet type (because it
78 attributes, however, are extracted from headers within the packet,
80 headers.
176 encapsulated headers beyond the VLAN tag using the existing field
207 Don't drop packets in the kernel for malformed protocol headers, bad
|
| D | radiotap-headers.rst | 4 How to use radiotap headers
10 Radiotap headers are variable-length and extensible, you can get most of the
146 } /* while more rt headers */
|
| D | index.rst | 94 radiotap-headers
|
| D | netdev-features.rst | 112 whatever headers there might be.
123 replicates the network and UDP headers (fixing up the last one if less than
160 headers. Some drivers set this because the cards can't handle the bigger MTU.
|
| /Documentation/userspace-api/ |
| D | ELF.rst | 20 interpreter. Other PT_INTERP headers are ignored (since Linux 2.4.11).
26 (since Linux 2.6.6). Other PT_GNU_STACK headers are ignored.
33 program header of an executable is used. Other PT_GNU_PROPERTY headers
|
| /Documentation/trace/ |
| D | hisi-ptt.rst | 13 and trace the TLP headers (trace). The two functions are independent,
113 PTT trace is designed for dumping the TLP headers to the memory, which
115 Link. You can choose to filter the traced headers by either Requester ID,
117 device. It's also supported to trace the headers of certain type and of
130 This will trace the TLP headers downstream root port 0000:00:10.1 (event
137 The TLP headers to trace can be filtered by the Root Ports or the Requester ID
169 You can trace the TLP headers of certain types by specifying the `type`
177 You can specify multiple types when tracing inbound TLP headers, but can only
178 specify one when tracing outbound TLP headers.
183 You can trace the TLP headers from certain direction, which is relative
[all …]
|
| /Documentation/arch/sh/ |
| D | new-machine.rst | 19 in arch/sh/kernel/ directly, with board-specific headers ending up in
40 | `-- board-specific headers
42 | `-- board-specific headers
56 ... and so on. Headers for the companion chips are treated the same way as
57 board-specific headers. Thus, include/asm-sh/hd64461 is home to all of the
58 hd64461-specific headers.
80 | `-- SH-2 specific headers
82 | `-- SH-3 specific headers
84 `-- SH-4 specific headers
104 should also add a directory in include/asm-sh for headers localized to this
|
| /Documentation/networking/devlink/ |
| D | devlink-dpipe.rst | 69 * headers
91 * ``headers_get``: Receive a device's supported headers.
109 In a similar way to P4 headers and fields are used to describe a table's
110 behavior. There is a slight difference between the standard protocol headers
111 and specific ASIC metadata. The protocol headers should be declared in the
115 headers it implements. The headers and fields are identified by enumeration.
136 specified in order to distinguish multiple headers of the same type in a
|
| /Documentation/bpf/libbpf/ |
| D | libbpf_build.rst | 22 together with libbpf headers in a staging directory root/:
32 headers in a build directory /build/root/:
|
| /Documentation/admin-guide/perf/ |
| D | hisi-pcie-pmu.rst | 121 - 2'b10: Bandwidth of TLP headers
122 - 2'b11: Bandwidth of both TLP payloads and headers
124 For example, "len_mode=2" means only counting the bandwidth of TLP headers
126 headers and payloads. Default value if not specified is 2'b11.
|
| /Documentation/translations/zh_CN/doc-guide/ |
| D | index.rst | 18 parse-headers
|
| /Documentation/doc-guide/ |
| D | index.rst | 12 parse-headers
|
| /Documentation/userspace-api/media/dvb/ |
| D | headers.rst | 7 Digital TV uAPI headers
|
| /Documentation/translations/it_IT/doc-guide/ |
| D | index.rst | 17 parse-headers
|
| /Documentation/dev-tools/ |
| D | kselftest.rst | 39 $ make headers
261 * First use the headers inside the kernel source and/or git repo, and then the
262 system headers. Headers for the kernel release as opposed to headers
264 to find regressions. Use KHDR_INCLUDES in Makefile to include headers from
|
| /Documentation/gpu/rfc/ |
| D | index.rst | 14 kerneldoc in like with real uapi headers.
|
| /Documentation/hwmon/ |
| D | sch5636.rst | 28 temperatures. Note that the driver detects how many fan headers /
|
| /Documentation/devicetree/bindings/clock/ |
| D | samsung,exynos-clock.yaml | 17 dt-bindings/clock/ headers.
|
| D | samsung,exynos4412-isp-clock.yaml | 18 dt-bindings/clock/ headers.
|
1234567