Hi Hans,
I noticed there are two s_std ops in core and video for output. And
some drivers call video-s_std_out and then core-s_std in their S_STD
iotcl. Could anyone share me the story why we have
s_std_output/g_std_output/g_tvnorms_output ops in video instead of
making use of s_std/g_std in
On Wed 27 June 2012 11:37:24 Scott Jiang wrote:
Hi Hans,
I noticed there are two s_std ops in core and video for output. And
some drivers call video-s_std_out and then core-s_std in their S_STD
iotcl. Could anyone share me the story why we have
s_std_output/g_std_output/g_tvnorms_output ops
2012/6/27 Hans Verkuil hverk...@xs4all.nl:
On Wed 27 June 2012 11:37:24 Scott Jiang wrote:
Hi Hans,
I noticed there are two s_std ops in core and video for output. And
some drivers call video-s_std_out and then core-s_std in their S_STD
iotcl. Could anyone share me the story why we have
On Wed 27 June 2012 12:14:34 Scott Jiang wrote:
2012/6/27 Hans Verkuil hverk...@xs4all.nl:
On Wed 27 June 2012 11:37:24 Scott Jiang wrote:
Hi Hans,
I noticed there are two s_std ops in core and video for output. And
some drivers call video-s_std_out and then core-s_std in their S_STD
