| /dports/multimedia/libv4l/linux-5.13-rc2/Documentation/userspace-api/media/v4l/ |
| 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
22 .. c:macro:: VIDIOC_S_FMT
24 ``int ioctl(int fd, VIDIOC_S_FMT, struct v4l2_format *argp)``
63 application. When the application calls the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl with
70 prepare for data exchange. Finally the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl returns
74 application must implement the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and :ref:`VIDIOC_S_FMT <VIDIOC_G_…
76 EINVAL error code on a :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` attempt. When I/O is already in
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 | 27 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctls. Additionally the
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 …
|
| H A D | dev-output.rst | 75 of :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, and call the :ref:`VIDIOC_S_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…
89 and :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, even if :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ignores all
|
| H A D | dev-capture.rst | 78 of :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, and call the :ref:`VIDIOC_S_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…
92 and :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, even if :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ignores all
|
| H A D | dev-osd.rst | 23 the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl.
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…
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
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
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>`
207 after calling :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` are undefined. When clip lists are
228 its contents after calling :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` are
|
| H A D | io.rst | 25 initiating video overlay with the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`
35 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` and :ref:`VIDIOC_REQBUFS` would permit this to some
|
| /dports/multimedia/v4l-utils/linux-5.13-rc2/Documentation/userspace-api/media/v4l/ |
| 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
22 .. c:macro:: VIDIOC_S_FMT
24 ``int ioctl(int fd, VIDIOC_S_FMT, struct v4l2_format *argp)``
63 application. When the application calls the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl with
70 prepare for data exchange. Finally the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl returns
74 application must implement the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and :ref:`VIDIOC_S_FMT <VIDIOC_G_…
76 EINVAL error code on a :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` attempt. When I/O is already in
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 | 27 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctls. Additionally the
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 …
|
| H A D | dev-output.rst | 75 of :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, and call the :ref:`VIDIOC_S_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…
89 and :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, even if :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ignores all
|
| H A D | dev-capture.rst | 78 of :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, and call the :ref:`VIDIOC_S_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…
92 and :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, even if :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ignores all
|
| H A D | dev-osd.rst | 23 the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl.
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…
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
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
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>`
207 after calling :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` are undefined. When clip lists are
228 its contents after calling :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` are
|
| /dports/multimedia/v4l_compat/linux-5.13-rc2/Documentation/userspace-api/media/v4l/ |
| 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
22 .. c:macro:: VIDIOC_S_FMT
24 ``int ioctl(int fd, VIDIOC_S_FMT, struct v4l2_format *argp)``
63 application. When the application calls the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl with
70 prepare for data exchange. Finally the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl returns
74 application must implement the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and :ref:`VIDIOC_S_FMT <VIDIOC_G_…
76 EINVAL error code on a :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` attempt. When I/O is already in
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 | 27 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctls. Additionally the
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 …
|
| H A D | dev-output.rst | 75 of :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, and call the :ref:`VIDIOC_S_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…
89 and :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, even if :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ignores all
|
| H A D | dev-capture.rst | 78 of :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, and call the :ref:`VIDIOC_S_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…
92 and :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl, even if :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ignores all
|
| H A D | dev-osd.rst | 23 the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl.
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…
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
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
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>`
207 after calling :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` are undefined. When clip lists are
228 its contents after calling :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` are
|
| /dports/multimedia/v4l_compat/v4l-utils-4l-utils-1.20.0/utils/v4l2-ctl/ |
| H A D | v4l2-ctl-vbi.cpp | 210 ret = doioctl(fd, VIDIOC_S_FMT, &sliced_fmt); in vbi_set()
220 ret = doioctl(fd, VIDIOC_S_FMT, &sliced_fmt_out); in vbi_set()
234 ret = doioctl(fd, VIDIOC_S_FMT, &fmt); in vbi_set()
248 ret = doioctl(fd, VIDIOC_S_FMT, &fmt); in vbi_set()
|
| H A D | v4l2-ctl-sdr.cpp | 91 ret = doioctl(fd, VIDIOC_S_FMT, &in_vfmt); in sdr_set()
116 ret = doioctl(fd, VIDIOC_S_FMT, &in_vfmt); in sdr_set()
|
| /dports/multimedia/libv4l/v4l-utils-4l-utils-1.20.0/utils/v4l2-ctl/ |
| H A D | v4l2-ctl-vbi.cpp | 210 ret = doioctl(fd, VIDIOC_S_FMT, &sliced_fmt); in vbi_set()
220 ret = doioctl(fd, VIDIOC_S_FMT, &sliced_fmt_out); in vbi_set()
234 ret = doioctl(fd, VIDIOC_S_FMT, &fmt); in vbi_set()
248 ret = doioctl(fd, VIDIOC_S_FMT, &fmt); in vbi_set()
|
| H A D | v4l2-ctl-sdr.cpp | 91 ret = doioctl(fd, VIDIOC_S_FMT, &in_vfmt); in sdr_set()
116 ret = doioctl(fd, VIDIOC_S_FMT, &in_vfmt); in sdr_set()
|
| /dports/multimedia/v4l-utils/v4l-utils-4l-utils-1.20.0/utils/v4l2-ctl/ |
| H A D | v4l2-ctl-vbi.cpp | 210 ret = doioctl(fd, VIDIOC_S_FMT, &sliced_fmt); in vbi_set()
220 ret = doioctl(fd, VIDIOC_S_FMT, &sliced_fmt_out); in vbi_set()
234 ret = doioctl(fd, VIDIOC_S_FMT, &fmt); in vbi_set()
248 ret = doioctl(fd, VIDIOC_S_FMT, &fmt); in vbi_set()
|
| H A D | v4l2-ctl-sdr.cpp | 91 ret = doioctl(fd, VIDIOC_S_FMT, &in_vfmt); in sdr_set()
116 ret = doioctl(fd, VIDIOC_S_FMT, &in_vfmt); in sdr_set()
|