RE: RFC (v1.2): V4L - Support for video timings at the input/output interface

2009-10-21 Thread Karicheri, Muralidharan
Hans, /* timing data values specified by various standards such as BT.1120, BT.656 etc. */ /* bt.656/bt.1120 timing data */ struct v4l2_bt_timings { __u32 interlaced; __u64 pixelclock; __u32 width, height; __u32

RE: RFC (v1.2): V4L - Support for video timings at the input/output interface

2009-10-21 Thread Hans Verkuil
> Hans, > > >>> >>> #define V4L2_DV_INVALID0x >>> #define V4L2_DV_480I59_94 0x0001 >>> #define V4L2_DV_480I60 0x0002 >>> #define V4L2_DV_480P23_976 0x0003 >>> #define V4L2_DV_480P24 0x0004 >>> #define

RE: RFC (v1.2): V4L - Support for video timings at the input/output interface

2009-10-21 Thread Karicheri, Muralidharan
Hans, >> >> #defineV4L2_DV_INVALID0x >> #define V4L2_DV_480I59_94 0x0001 >> #define V4L2_DV_480I60 0x0002 >> #define V4L2_DV_480P23_976 0x0003 >> #define V4L2_DV_480P24 0x0004 >> #define V4L2_DV

Re: RFC (v1.2): V4L - Support for video timings at the input/output interface

2009-10-20 Thread Hans Verkuil
> Hi, > > Here is the updated RFC incorporating comments received on last one. > > Following are the changes:- > > 1) Removed V4L2_DV_CUSTOM since we have a capability flag for it in > v4l2_input/output structure > > 2) Replaced V4L2_DV_CUSTOMS with V4L2_DV_INVALID (value 0x) > > 3) Rename