On Tue, Jul 30, 2013 at 01:16:54PM +0200, Laurent Pinchart wrote: ... > > > + <para>This is a multi-planar, two-plane version of the YUV 4:2:0 > format. > > > +The three components are separated into two sub-images or planes. > > > +<constant>V4L2_PIX_FMT_NV16M</constant> differs from > > > <constant>V4L2_PIX_FMT_NV16 +</constant> in that the two planes are > > > non-contiguous in memory, i.e. the chroma +plane do not necessarily > > > immediately follows the luma plane. > > > +The luminance data occupies the first plane. The Y plane has one byte per > > > pixel. +In the second plane there is a chrominance data with alternating > > > chroma samples. +The CbCr plane is the same width and height, in bytes, > > > as the Y plane. +Each CbCr pair belongs to four pixels. For example, > > > +Cb<subscript>0</subscript>/Cr<subscript>0</subscript> belongs to > > > +Y'<subscript>00</subscript>, Y'<subscript>01</subscript>, > > > +Y'<subscript>10</subscript>, Y'<subscript>11</subscript>. > > > +<constant>V4L2_PIX_FMT_NV61M</constant> is the same as > > > <constant>V4L2_PIX_FMT_NV16M</constant> +except the Cb and Cr bytes are > > > swapped, the CrCb plane starts with a Cr byte.</para> + > > > + <para><constant>V4L2_PIX_FMT_NV16M</constant> is intended to be > > > +used only in drivers and applications that support the multi-planar API, > > > +described in <xref linkend="planar-apis"/>. </para> > > > > I think you could refer to V4L2_PIX_FMT_NV61M or alternatively move the > > sentence explaining V4L2_PIX_FMT_NV61M after the above. Up to you. > > Something like > > <para><constant>V4L2_PIX_FMT_NV16M</constant> and > <constant>V4L2_PIX_FMT_NV61M</constant> are intended to be used only in > drivers and applications that support the multi-planar API, described in Fine for me. -- Cheers, Sakari Ailus e-mail: sakari.ailus@xxxxxx XMPP: sailus@xxxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html