Re: [RFC PATCH 00/20] solo6x10: V4L2 compliancy fixes and major overhaul

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun,  3 Mar 2013 00:45:16 +0100
Hans Verkuil <hverkuil@xxxxxxxxx> wrote: 
> 3) What is the meaning of this snippet of code in v4l2-enc.c?
> 
> 	if (pix->priv)
> 		solo_enc->type = SOLO_ENC_TYPE_EXT;
> 
>    I've commented it out since it is completely undocumented and no
> driver should assume that priv is non-zero anymore, precisely because
> of issues like this. Ismael, do you know what the difference is
> between SOLO_ENC_TYPE_STD and SOLO_ENC_TYPE_EXT?

When written to the first bit of the 0x480-0x4BC registers
(SOLO_CAP_CH_COMP_ENA_E(n)), it enables the encoding of the respective
extended channel.

It's a bad name :/.
--
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


[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux