/dports/multimedia/libv4l/linux-5.13-rc2/Documentation/userspace-api/media/v4l/ |
H A D | dev-output.rst | 65 and call the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl with a pointer 75 of :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, and call the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` 77 parameters and finally return the actual parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` 80 Like :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` the :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl 87 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` and :ref:`VIDIOC_TRY_FMT <VI… 88 details. Video output devices must implement both the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` 89 and :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, even if :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ignores all 90 requests and always returns default parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does. 91 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` is optional.
|
H A D | dev-capture.rst | 68 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl with a pointer to this 78 of :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, and call the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` 80 parameters and finally return the actual parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` 83 Like :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` the :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl 90 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` and :ref:`VIDIOC_TRY_FMT <VI… 91 details. Video capture devices must implement both the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` 92 and :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, even if :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ignores all 93 requests and always returns default parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does. 94 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` is optional.
|
H A D | vidioc-g-fmt.rst | 7 ioctl VIDIOC_G_FMT, VIDIOC_S_FMT, VIDIOC_TRY_FMT 13 VIDIOC_G_FMT - VIDIOC_S_FMT - VIDIOC_TRY_FMT - Get or set the data format, try a format 18 .. c:macro:: VIDIOC_G_FMT 20 ``int ioctl(int fd, VIDIOC_G_FMT, struct v4l2_format *argp)`` 50 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl with a pointer to this structure the driver fills 70 prepare for data exchange. Finally the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl returns 71 the current format parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does. Very simple, 74 application must implement the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and :ref:`VIDIOC_S_FMT <VIDIOC_G_… 80 The :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl is equivalent to :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` … 88 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` returns for the same input or output. [all …]
|
H A D | format.rst | 26 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and 27 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctls. Additionally the 28 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl can be used to examine 34 The :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl is a major turning-point in the 37 change controls or modify other properties. The first :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` 53 When applications omit the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl its locking side 64 *may* support a switch using :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`. 67 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. Implementation of … 68 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` is highly recommended but optional.
|
H A D | dev-osd.rst | 23 the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. 123 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl. The driver fills the 130 substructure and call the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. 132 the actual parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does. Like :ref:`VIDIOC_S_FMT <VIDIOC_G… 133 the :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl can be used to learn 135 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` this also works after the overlay has been enabled.
|
H A D | dev-overlay.rst | 26 the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. 111 (:ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`) or overlay 131 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl. The driver fills the 138 call the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. The driver 140 parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does. Like :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`, the 141 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl can be used to learn 143 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` this also works after the overlay has been enabled. 152 (:ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`) may fail with an ``EBUSY`` error 200 contents after calling :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` 228 its contents after calling :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` are [all …]
|
H A D | planar-apis.rst | 47 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`, :ref:`VIDIOC_TRY_FMT <VIDIO…
|
H A D | dev-raw-vbi.rst | 32 applications must call the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. 72 the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl with a pointer to this 81 of :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, and call the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` 95 VBI devices must implement both the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and 96 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, even if :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ignores all re… 97 and always returns default parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does. 98 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` is optional.
|
/dports/multimedia/v4l-utils/linux-5.13-rc2/Documentation/userspace-api/media/v4l/ |
H A D | dev-output.rst | 65 and call the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl with a pointer 75 of :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, and call the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` 77 parameters and finally return the actual parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` 80 Like :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` the :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl 87 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` and :ref:`VIDIOC_TRY_FMT <VI… 88 details. Video output devices must implement both the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` 89 and :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, even if :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ignores all 90 requests and always returns default parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does. 91 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` is optional.
|
H A D | dev-capture.rst | 68 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl with a pointer to this 78 of :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, and call the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` 80 parameters and finally return the actual parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` 83 Like :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` the :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl 90 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` and :ref:`VIDIOC_TRY_FMT <VI… 91 details. Video capture devices must implement both the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` 92 and :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, even if :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ignores all 93 requests and always returns default parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does. 94 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` is optional.
|
H A D | vidioc-g-fmt.rst | 7 ioctl VIDIOC_G_FMT, VIDIOC_S_FMT, VIDIOC_TRY_FMT 13 VIDIOC_G_FMT - VIDIOC_S_FMT - VIDIOC_TRY_FMT - Get or set the data format, try a format 18 .. c:macro:: VIDIOC_G_FMT 20 ``int ioctl(int fd, VIDIOC_G_FMT, struct v4l2_format *argp)`` 50 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl with a pointer to this structure the driver fills 70 prepare for data exchange. Finally the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl returns 71 the current format parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does. Very simple, 74 application must implement the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and :ref:`VIDIOC_S_FMT <VIDIOC_G_… 80 The :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl is equivalent to :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` … 88 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` returns for the same input or output. [all …]
|
H A D | format.rst | 26 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and 27 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctls. Additionally the 28 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl can be used to examine 34 The :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl is a major turning-point in the 37 change controls or modify other properties. The first :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` 53 When applications omit the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl its locking side 64 *may* support a switch using :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`. 67 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. Implementation of … 68 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` is highly recommended but optional.
|
H A D | dev-osd.rst | 23 the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. 123 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl. The driver fills the 130 substructure and call the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. 132 the actual parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does. Like :ref:`VIDIOC_S_FMT <VIDIOC_G… 133 the :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl can be used to learn 135 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` this also works after the overlay has been enabled.
|
H A D | dev-overlay.rst | 26 the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. 111 (:ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`) or overlay 131 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl. The driver fills the 138 call the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. The driver 140 parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does. Like :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`, the 141 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl can be used to learn 143 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` this also works after the overlay has been enabled. 152 (:ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`) may fail with an ``EBUSY`` error 200 contents after calling :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` 228 its contents after calling :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` are [all …]
|
H A D | planar-apis.rst | 47 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`, :ref:`VIDIOC_TRY_FMT <VIDIO…
|
/dports/multimedia/v4l_compat/linux-5.13-rc2/Documentation/userspace-api/media/v4l/ |
H A D | dev-output.rst | 65 and call the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl with a pointer 75 of :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, and call the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` 77 parameters and finally return the actual parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` 80 Like :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` the :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl 87 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` and :ref:`VIDIOC_TRY_FMT <VI… 88 details. Video output devices must implement both the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` 89 and :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, even if :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ignores all 90 requests and always returns default parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does. 91 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` is optional.
|
H A D | dev-capture.rst | 68 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl with a pointer to this 78 of :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, and call the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` 80 parameters and finally return the actual parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` 83 Like :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` the :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl 90 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` and :ref:`VIDIOC_TRY_FMT <VI… 91 details. Video capture devices must implement both the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` 92 and :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, even if :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ignores all 93 requests and always returns default parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does. 94 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` is optional.
|
H A D | vidioc-g-fmt.rst | 7 ioctl VIDIOC_G_FMT, VIDIOC_S_FMT, VIDIOC_TRY_FMT 13 VIDIOC_G_FMT - VIDIOC_S_FMT - VIDIOC_TRY_FMT - Get or set the data format, try a format 18 .. c:macro:: VIDIOC_G_FMT 20 ``int ioctl(int fd, VIDIOC_G_FMT, struct v4l2_format *argp)`` 50 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl with a pointer to this structure the driver fills 70 prepare for data exchange. Finally the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl returns 71 the current format parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does. Very simple, 74 application must implement the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and :ref:`VIDIOC_S_FMT <VIDIOC_G_… 80 The :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl is equivalent to :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` … 88 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` returns for the same input or output. [all …]
|
H A D | format.rst | 26 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and 27 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctls. Additionally the 28 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl can be used to examine 34 The :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl is a major turning-point in the 37 change controls or modify other properties. The first :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` 53 When applications omit the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl its locking side 64 *may* support a switch using :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`. 67 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. Implementation of … 68 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` is highly recommended but optional.
|
H A D | dev-osd.rst | 23 the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. 123 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl. The driver fills the 130 substructure and call the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. 132 the actual parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does. Like :ref:`VIDIOC_S_FMT <VIDIOC_G… 133 the :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl can be used to learn 135 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` this also works after the overlay has been enabled.
|
H A D | dev-overlay.rst | 26 the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. 111 (:ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`) or overlay 131 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl. The driver fills the 138 call the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl. The driver 140 parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does. Like :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`, the 141 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl can be used to learn 143 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` this also works after the overlay has been enabled. 152 (:ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`) may fail with an ``EBUSY`` error 200 contents after calling :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` 228 its contents after calling :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` are [all …]
|
H A D | planar-apis.rst | 47 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`, :ref:`VIDIOC_TRY_FMT <VIDIO…
|
/dports/multimedia/v4l_compat/v4l-utils-4l-utils-1.20.0/utils/v4l2-ctl/ |
H A D | v4l2-ctl-vbi.cpp | 231 doioctl(fd, VIDIOC_G_FMT, &fmt); in vbi_set() 245 doioctl(fd, VIDIOC_G_FMT, &fmt); in vbi_set() 262 if (doioctl(fd, VIDIOC_G_FMT, &sliced_fmt) == 0) in vbi_get() 268 if (doioctl(fd, VIDIOC_G_FMT, &sliced_fmt_out) == 0) in vbi_get() 274 if (doioctl(fd, VIDIOC_G_FMT, &raw_fmt) == 0) in vbi_get() 280 if (doioctl(fd, VIDIOC_G_FMT, &raw_fmt_out) == 0) in vbi_get()
|
/dports/multimedia/libv4l/v4l-utils-4l-utils-1.20.0/utils/v4l2-ctl/ |
H A D | v4l2-ctl-vbi.cpp | 231 doioctl(fd, VIDIOC_G_FMT, &fmt); in vbi_set() 245 doioctl(fd, VIDIOC_G_FMT, &fmt); in vbi_set() 262 if (doioctl(fd, VIDIOC_G_FMT, &sliced_fmt) == 0) in vbi_get() 268 if (doioctl(fd, VIDIOC_G_FMT, &sliced_fmt_out) == 0) in vbi_get() 274 if (doioctl(fd, VIDIOC_G_FMT, &raw_fmt) == 0) in vbi_get() 280 if (doioctl(fd, VIDIOC_G_FMT, &raw_fmt_out) == 0) in vbi_get()
|
/dports/multimedia/v4l-utils/v4l-utils-4l-utils-1.20.0/utils/v4l2-ctl/ |
H A D | v4l2-ctl-vbi.cpp | 231 doioctl(fd, VIDIOC_G_FMT, &fmt); in vbi_set() 245 doioctl(fd, VIDIOC_G_FMT, &fmt); in vbi_set() 262 if (doioctl(fd, VIDIOC_G_FMT, &sliced_fmt) == 0) in vbi_get() 268 if (doioctl(fd, VIDIOC_G_FMT, &sliced_fmt_out) == 0) in vbi_get() 274 if (doioctl(fd, VIDIOC_G_FMT, &raw_fmt) == 0) in vbi_get() 280 if (doioctl(fd, VIDIOC_G_FMT, &raw_fmt_out) == 0) in vbi_get()
|