Searched full:format (Results 1 – 25 of 856) sorted by relevance
12345678910>>...35
| /Documentation/media/uapi/v4l/ |
| D | vidioc-subdev-g-fmt.rst | 19 VIDIOC_SUBDEV_G_FMT - VIDIOC_SUBDEV_S_FMT - Get or set the data format on a subdev pad 45 These ioctls are used to negotiate the frame format at specific subdev 48 To retrieve the current format applications set the ``pad`` field of a 53 driver fills the members of the ``format`` field. 55 To change the current format applications set both the ``pad`` and 56 ``which`` fields and all members of the ``format`` field. When they call 58 driver verifies the requested format, adjusts it based on the hardware 61 format as would be returned by a ``VIDIOC_SUBDEV_G_FMT`` call. 69 For instance, to try a format at the output pad of a sub-device, 70 applications would first set the try format at the sub-device input with [all …]
|
| D | pixfmt-reserved.rst | 13 Reserved Format Identifiers 18 register your own format, send an e-mail to the linux-media mailing list 21 format with other developers add a link to your documentation and send a 23 you think your format should be listed in a standard format section 48 - Compressed format of the ET61X251 driver. 53 - 8 bit RGB format used by the BTTV driver. 58 - YUV 4:2:0 format used by the IVTV driver, 61 The format is documented in the kernel sources in the file 67 - YUV format used by the gspca cpia1 driver. 72 - JPEG-Light format (Pegasus Lossless JPEG) used in Divio webcams NW [all …]
|
| D | dev-subdev.rst | 85 need to expose low-level format configuration to user space. Generic 91 For the purpose of this section, the term *format* means the 92 combination of media bus data format, frame width and frame height. 95 devices using the format and 98 to the requested format at the pipeline input and/or output. 113 Image Format Negotiation on Pipelines 126 can expose pad-level image format configuration to applications. When 138 Pad-level image format configuration support can be tested by calling 140 0. If the driver returns an ``EINVAL`` error code pad-level format 144 Format Negotiation [all …]
|
| D | vidioc-create-bufs.rst | 55 The ``format`` field specifies the image format that the buffers must be 60 requested format is supported by the driver. Based on the format's 67 defined by the ``format.pix.sizeimage`` field (or the corresponding 68 fields for other format types). Usually if the ``format.pix.sizeimage`` 69 field is less than the minimum required for the given format, then an 99 ``format.type``. If those are invalid -1 is returned and errno is 109 - ``format`` 122 ``V4L2_MEMORY_MMAP`` and ``format.type`` to the buffer type. 140 The buffer type (``format.type`` field), requested I/O method 141 (``memory``) or format (``format`` field) is not valid.
|
| D | dev-decoder.rst | 60 coded format 61 encoded/compressed video bytestream format (e.g. H.264, VP8, etc.); see 62 also: raw format. 77 coded format includes a feature of frame reordering; for decoders, 119 raw format 120 uncompressed format containing raw pixel data (e.g. YUV, RGB formats). 214 format set on ``CAPTURE``. 216 about the decoder's capabilities with respect to each coded format. 223 * Only the formats supported for the format currently active on ``OUTPUT`` 226 * In order to enumerate raw formats supported by a given coded format, [all …]
|
| D | dev-meta.rst | 42 Data Format Negotiation 45 The metadata device uses the :ref:`format` ioctls to select the capture format. 46 The metadata buffer content format is bound to that selected format. In addition 47 to the basic :ref:`format` ioctls, the :c:func:`VIDIOC_ENUM_FMT` ioctl must be 50 To use the :ref:`format` ioctls applications set the ``type`` field of the 68 - The data format, set by the application. This is a little endian
|
| D | vidioc-enum-fmt.rst | 66 - Number of the format in the enumeration, set by the application. 85 - Description of the format, a NUL-terminated ASCII string. This 89 - The image format identifier. This is a four character code as 117 .. flat-table:: Image Format Description Flags 124 - This is a compressed format. 127 - This format is not native to the device but emulated through 129 format instead for better performance. 132 - The hardware decoder for this compressed bytestream format (aka coded 133 format) is capable of parsing a continuous bytestream. Applications do 141 compressed bytestream format (aka coded format). It will notify the user
|
| D | vidioc-g-fmt.rst | 19 VIDIOC_G_FMT - VIDIOC_S_FMT - VIDIOC_TRY_FMT - Get or set the data format, try a format 47 These ioctls are used to negotiate the format of data (typically image 48 format) exchanged between driver and application. 63 To change the current format parameters applications initialize the 76 the current format parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does. Very simple, 92 The format as returned by :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` must be identical to what 113 - Definition of an image format, see :ref:`pixfmt`, used by video 118 - Definition of an image format, see :ref:`pixfmt`, used by video 140 - Definition of a data format, see :ref:`pixfmt`, used by SDR 145 - Definition of a metadata format, see :ref:`meta-formats`, used by [all …]
|
| D | dev-sdr.rst | 66 Data Format Negotiation 69 The SDR device uses the :ref:`format` ioctls to select the 70 capture and output format. Both the sampling resolution and the data 71 streaming format are bound to that selectable format. In addition to the 72 basic :ref:`format` ioctls, the 76 To use the :ref:`format` ioctls applications set the ``type`` 83 Content of the ``pixelformat`` is V4L2 FourCC code of the data format. 99 - The data format or type of compression, set by the application.
|
| D | pixfmt-compressed.rst | 37 - MPEG multiplexed stream. The actual format is determined by 65 extracted from the H264 bitstream. This format is adapted for 79 with this pixel format. The output buffer must contain the 85 This format is not yet part of the public kernel API and it 116 This format is adapted for stateless video decoders that implement a 124 this pixel format. The output buffer must contain the appropriate number 159 This format is adapted for stateless video decoders that implement a 165 this pixel format. The output buffer must contain the appropriate number 171 This format is not yet part of the public kernel API and it 204 - Same format as V4L2_PIX_FMT_FWHT but requires stateless codec implementation.
|
| D | pixfmt-v4l2-mplane.rst | 11 Multi-planar format structures 15 and layout for each of the planes in a multi-planar format. The 19 describing all planes of that format. 81 - The pixel format. Both single- and multi-planar four character 93 - An array of structures describing format of each plane this pixel 94 format consists of. The number of valid entries in this array has 98 - Number of planes (i.e. separate memory buffers) for this format 102 - Flags set by the application or driver, see :ref:`format-flags`.
|
| /Documentation/translations/it_IT/process/ |
| D | clang-format.rst | 3 :Original: :ref:`Documentation/process/clang-format.rst <clangformat>` 8 clang-format 10 ``clang-format`` è uno strumento per formattare codice C/C++/... secondo 14 ``clang-format`` può essere usato per diversi fini: 28 Il suo file di configurazione è ``.clang-format`` e si trova nella cartella 35 potete sovrascriverle scrivendole in un altro file ``.clang-format`` in 39 Linux più popolari. Cercate ``clang-format`` nel vostro repositorio. 64 clang-format -i kernel/*.[ch] 70 le nuove funzionalità/versioni di ``clang-format``. 72 ``clang-format`` è in grado di leggere diversi diff unificati, quindi [all …]
|
| /Documentation/process/ |
| D | clang-format.rst | 3 clang-format 6 ``clang-format`` is a tool to format C/C++/... code according to 10 ``clang-format`` can be used for several purposes: 22 Its configuration file is ``.clang-format`` in the root of the kernel tree. 28 another ``.clang-format`` file in a subfolder. 31 Linux distributions for a long time. Search for ``clang-format`` in 55 clang-format -i kernel/*.[ch] 61 ``clang-format`` features/versions. 63 ``clang-format`` also supports reading unified diffs, so you can review 68 To avoid ``clang-format`` formatting some portion of a file, you can do:: [all …]
|
| /Documentation/media/uapi/dvb/ |
| D | video-set-format.rst | 26 .. c:function:: int ioctl(fd, VIDEO_SET_FORMAT, video_format_t format) 52 - video_format_t format 54 - video format of TV as defined in section ??. 60 This ioctl sets the screen format (aspect ratio) of the connected output 69 VIDEO_FORMAT_4_3, /* Select 4:3 format */ 70 VIDEO_FORMAT_16_9, /* Select 16:9 format. */ 92 - format is not a valid video format.
|
| D | video_types.rst | 17 .. _video-format-t: 28 VIDEO_FORMAT_4_3, /* Select 4:3 format */ 29 VIDEO_FORMAT_16_9, /* Select 16:9 format. */ 37 about the display format of the current video stream. 45 In case the display format of the video stream and of the display 54 VIDEO_PAN_SCAN, /* use pan and scan format */ 55 VIDEO_LETTER_BOX, /* use letterbox format */ 56 VIDEO_CENTER_CUT_OUT /* use center cut out format */ 131 __u32 format; 209 case the source video format is not the same as the format of the output
|
| /Documentation/security/ |
| D | IMA-templates.rst | 20 the measurements list would include the code for handling a new format 33 specifying the template format (a string of field identifiers separated 36 by translating the format into an array of template fields structures taken 62 descriptors by adding their identifier to the format string 69 algorithm (field format: [<hash algo>:]digest, where the digest 80 - "ima": its format is ``d|n``; 81 - "ima-ng" (default): its format is ``d-ng|n-ng``; 82 - "ima-sig": its format is ``d-ng|n-ng|sig``; 83 - "ima-buf": its format is ``d-ng|n-ng|buf``; 84 - "ima-modsig": its format is ``d-ng|n-ng|sig|d-modsig|modsig``; [all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-firmware-turris-mox-rwtm | 6 Format: %i 13 Format: %pM 22 Format: string 30 Format: %i 37 Format: %016X
|
| D | sysfs-bus-mei | 7 Format: mei:<mei device name>:<device uuid>:<protocol version> 14 Format: string 21 Format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx 28 Format: %d
|
| D | sysfs-class-iommu-intel-iommu | 7 Format: %llx. This allows association of a sysfs 16 of this DRHD unit. Format: %llx. 24 value of this DRHD unit. Format: %llx. 32 VT-d VER_REG. Format: %d:%d, major:minor
|
| D | sysfs-fs-xfs | 7 log. The LSN is exported in "cycle:basic block" format. 16 log. The LSN is exported in "cycle:basic block" format. 26 "cycle:bytes" format. 38 "cycle:bytes" format.
|
| D | sysfs-bus-moxtet-devices | 5 Description: (R) Moxtet module description. Format: string 11 Description: (R) Moxtet module ID. Format: %x 17 Description: (R) Moxtet module name. Format: string
|
| /Documentation/fb/ |
| D | api.rst | 38 The driver supports the four character code (FOURCC) based format setting API. 47 to be aware of the pixel storage format in order to write image data to the 48 frame buffer memory in the format expected by the hardware. 88 Macropixels are stored in memory as described by the format FOURCC identifier 141 Pixels are encoded and interpreted as described by the format FOURCC 153 about the frame buffer device and the current format. Those information can't 155 application modifies the format:: 179 about a frame buffer device, its current format and video mode, as well as 198 __u32 nonstd; /* != 0 Non standard pixel format */ 231 4. Format configuration [all …]
|
| /Documentation/devicetree/bindings/media/xilinx/ |
| D | video.txt | 20 - xlnx,video-format: This property represents a video format transmitted on an 22 Video IP and System Design Guide" [UG934]. How the format relates to the IP 25 - xlnx,video-width: This property qualifies the video format with the sample 29 - xlnx,cfa-pattern: When the video format is set to Mono/Sensor, this property
|
| /Documentation/driver-api/nvdimm/ |
| D | security.rst | 51 A nvdimm encrypted-key of format enc32 has the description format of: 55 encrypted-keys of enc32 format. TPM usage with a master trusted key is 75 is injected with the description format described from earlier in this 77 the format: 90 The security disable command format is: 98 The command format for doing a secure erase is: 106 The command format for doing an overwrite is: 120 The command format for doing a master update is: 131 The command format for doing a master erase is:
|
| /Documentation/sparc/oradax/ |
| D | dax-hv-api.txt | 138 Table 36.1. CCB Header Format 235 …erpreted by the virtual machine. Not all of the types specified are used by every CCB format. Types 250 36.2.1.1.1. Primary Input Format 252 …The primary input format code is a 4-bit field when it is used. There are 10 primary input formats… 255 Code Format Description 287 Code Format Description 305 field depends on the input format selected, as listed in the table above. 307 36.2.1.1.3. Secondary Input Format 310 …always encoded in a fixed width, bit-packed format. The bits are read from most significant bit to… 315 Format Code [all …]
|
12345678910>>...35