Searched full:frames (Results 1 – 25 of 141) sorted by relevance
123456
| /Documentation/networking/ |
| D | can.rst | 31 receive raw CAN frames, directly to/from the controller hardware.
32 Queueing of frames and higher-level transport protocols like ISO-TP
45 network layer as a network device, so that CAN frames from the
54 frames on different or the same CAN IDs. Several sockets listening on
55 the same interface for frames with the same CAN ID are all passed the
56 same received matching CAN frames. An application wishing to
60 CAN-IDs, frames, etc.
93 CAN frames between them, (sophisticated) queueing of CAN frames, and
142 Local Loopback of Sent Frames
160 some kind of local loopback of the sent CAN frames on the appropriate
[all …]
|
| D | defza.txt | 31 all-multi mode is also supported for LLC frames and it is used if
33 supports separate enables for LLC and SMT frames, but this driver
49 7. Queueing incoming/outgoing SMT frames in the driver if the SMT
|
| D | af_xdp.rst | 18 redirect ingress frames to other XDP enabled netdevs, using the
20 XDP programs to redirect frames to a memory buffer in a user-space
44 to fill in with RX packet data. References to these frames will then
104 equal-sized frames. An UMEM is associated to a netdev and a specific
117 to transfer ownership of UMEM frames between the kernel and the
149 The Fill ring is used to transfer ownership of UMEM frames from
154 Frames passed to the kernel are used for the ingress path (RX rings).
167 The Completion Ring is used transfer ownership of UMEM frames from
171 Frames passed from the kernel to user-space are frames that has been
184 If no frames have been passed to kernel via the Fill ring, no
[all …]
|
| D | l2tp.txt | 43 The L2TP protocol separates control and data frames. The L2TP kernel
44 drivers handle only L2TP data frames; control frames are always
45 handled by userspace. L2TP control frames carry messages between L2TP
60 mechanism by which PPP frames carried through an L2TP session are
64 subsystem arranges for PPP control frames to be delivered to pppd,
65 while data frames are forwarded as usual.
70 such as "ip" and "ifconfig". If only IP frames are passed over the
72 peer. If non-IP frames are to be passed over the tunnel, the interface
79 present in data frames - it is inferred from the IP connection on
102 udp_encap_rcv() in net/ipv4/udp.c. PPP data frames are never passed
[all …]
|
| D | mac80211-auth-assoc-deauth.txt | 22 BA session stop & deauth/disassoc frames
78 (data frames)
87 mac80211->driver: flush frames
|
| D | altera_tse.txt | 44 Jumbo frames are not supported at this time.
136 Section 5.2.2.1.2. This statistics is the count of frames that are successfully
140 Section 5.2.2.1.5. This statistic is the count of frames that are successfully
145 802.3-2012, Section 5.2.2.1.6. This statistic is the count of frames that are
150 Section 5.2.2.1.7. This statistic is the count of frames that are not an
163 802.3-2012, Section 30.3.4.2. This statistic is a count of PAUSE frames
167 802.3-2012, Section 30.3.4.3. This statistic is a count of PAUSE frames
252 frames between the length of 1519 and the maximum frame length configured
|
| D | can_ucan_protocol.rst | 25 The device sends CAN data frames and CAN error frames
28 The driver sends CAN data frames on the out endpoint
248 reported by sending corresponding error frames (see
303 error frames (see ``uapi/linux/can/error.h``) and sends it using the
307 Although UCAN devices can suppress error frames completely, in Linux
320 - During Bus OFF no frames are sent by the device.
|
| /Documentation/media/v4l-drivers/ |
| D | ipu3.rst | 23 frames in a format that is specific to the IPU3 (for consumption by the IPU3
70 Capturing frames in raw Bayer format
73 CIO2 MIPI CSI2 receiver is used to capture frames (in packed raw Bayer format)
74 from the raw sensors connected to the CSI2 ports. The captured frames are used
81 -- The IPU3 CSI2 receiver outputs the captured frames from the sensor in packed
90 frames in packed raw Bayer format to IPU3 CSI2 receiver.
128 With the above command, 10 frames are captured at 2592x1944 resolution, with
131 The captured frames are available as /tmp/frame-#.bin files.
197 The frames (in packed raw Bayer format specific to the IPU3) received by the
223 focus, auto exposure and auto white balance) statistics for the frames that are
[all …]
|
| D | rcar-fdp1.rst | 20 conversion output frames are identical to the input frames.
|
| D | imx.rst | 10 handles the flow of image frames to and from capture devices and
22 The IDMAC is the DMA controller for transfer of image frames to and from
48 captured frames from sensors directly to memory concurrently via four
58 motion). The deinterlaced output frames from the VDIC can be sent to the
97 defined that allow sending frames to the VDIC subdev directly from the
98 CSI. There is also support in the future for sending frames to the
165 When the direct source pad is routed to the ipuX_ic_prp entity, frames
173 The second source pad sends video frames directly to memory buffers
206 The CSI supports cropping the incoming raw sensor frames. This is
302 How many frames to skip after a FIM reset or stream restart before
[all …]
|
| D | omap4_camera.rst | 37 which only the last one is supported, outputting YUV422 frames).
40 which only the OV5650 are supported, outputting RAW10 frames).
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | marvell,odmi-controller.txt | 17 - marvell,odmi-frames : Number of ODMI frames available. Each frame
36 marvell,odmi-frames = <4>;
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-hid-ntrig | 6 (RW) Number of contact frames ignored before acknowledging the
15 (RW) Number of empty (no contact) frames ignored before
19 number of empty frames. By holding off on deactivation for a few
20 frames false erroneous disconnects can be tolerated, where the
|
| /Documentation/networking/device_drivers/intel/ |
| D | fm10k.rst | 31 Control. It will not send pause frames. This may result in dropped frames.
60 Jumbo Frames
62 Jumbo Frames support is enabled by changing the Maximum Transmission Unit (MTU)
81 NOTE: The maximum MTU setting for Jumbo Frames is 15342. This value coincides
82 with the maximum Jumbo Frames size of 15364 bytes.
|
| D | ixgb.rst | 111 Ethernet PAUSE frames. There are hardware bugs associated with enabling
340 Jumbo Frames
342 The driver supports Jumbo Frames for all adapters. Jumbo Frames support is
349 The maximum MTU setting for Jumbo Frames is 16114. This value coincides
350 with the maximum Jumbo Frames size of 16128.
403 Jumbo Frames System Requirement
406 of RAM or less that are running Jumbo Frames. If you are using Jumbo
407 Frames, your system may require more than the advertised minimum
410 Performance Degradation with Jumbo Frames
412 Degradation in throughput performance may be observed in some Jumbo frames
[all …]
|
| /Documentation/networking/device_drivers/freescale/dpaa2/ |
| D | ethernet-driver.rst | 106 frames, but must be affine to the CPUs for the purpose of traffic distribution.
108 Frames are transmitted and received through hardware frame queues, which can be
110 enqueues TX frames on egress queues and after transmission is complete a TX
113 When frames are available on ingress queues, a data availability notification
115 queues in the same channel have available frames, only one notification is sent.
168 Hardware checksum offloading is supported for TCP and UDP over IPv4/6 frames.
175 Scatter-gather frames are supported on both RX and TX paths. On TX, SG support
178 The DPAA2 hardware can process jumbo Ethernet frames of up to 10K bytes.
|
| /Documentation/media/uapi/v4l/ |
| D | vidioc-g-parm.rst | 45 The current video standard determines a nominal number of frames per
46 second. If less than this number of frames is to be captured or output,
119 - This is the desired period between successive frames captured by
120 the driver, in seconds. The field is intended to skip frames on
172 - This is the desired period between successive frames output by the
176 The field is intended to repeat frames on the driver side in
254 successive fields or frames to remove color edge artifacts and
|
| D | streaming-par.rst | 20 The current video standard determines a nominal number of frames per
21 second. If less than this number of frames is to be captured or output,
|
| D | dev-decoder.rst | 10 H.264/HEVC stream, raw VP8/9 stream) and decodes them into raw video frames in
51 decoded frames; for encoders, the queue of buffers containing an encoded
76 the order in which frames are decoded; may differ from display order if the
85 the order in which frames must be displayed; for encoders, ``OUTPUT``
98 stream, which clears the list of earlier reference frames (DPBs).
101 an encoded frame that does not reference frames decoded earlier, i.e.
112 frames; ``V4L2_BUF_TYPE_VIDEO_OUTPUT`` or
135 resolution in pixels of source frames being source to the encoder and
391 No decoded frames are produced during this phase.
409 frame buffer resolution for the decoded frames.
[all …]
|
| D | dev-mem2mem.rst | 24 supports both output (sending frames from memory to the hardware)
25 and capture (receiving the processed frames from the hardware into
|
| /Documentation/networking/mac80211_hwsim/ |
| D | mac80211_hwsim.rst | 43 radio and copying all transmitted frames to all other radios that are
45 radio. Software encryption in mac80211 is used so that the frames are
50 mac80211. This interface can be used to monitor all transmitted frames
|
| /Documentation/media/uapi/dvb/ |
| D | video-fast-forward.rst | 54 - The number of frames to skip.
61 I-frames. This call can only be used if VIDEO_SOURCE_MEMORY is
|
| D | video-get-frame-count.rst | 54 - Returns the number of frames displayed since the decoder was
66 frames since the decoder was started.
|
| /Documentation/driver-api/nfc/ |
| D | nfc-hci.rst | 121 On the rx path, the driver is responsible to push incoming HCP frames to HCI
200 fast, cannot sleep. sends incoming frames to HCI where they are passed to
247 handles shdlc framing in and out. It uses the driver xmit to send frames and
248 receives incoming frames in an skb queue filled from the driver IRQ handler.
249 SHDLC I(nformation) frames payload are HCP fragments. They are aggregated to
250 form complete HCI frames, which can be a response, command, or event.
297 frames. This thread will also check the shdlc sticky status and report to HCI
|
| /Documentation/devicetree/bindings/media/i2c/ |
| D | melexis,mlx90640.txt | 5 userspace to render processed frames.
|
123456