[07:38] <hverkuil> benjiG: can I merge all the sti patches in my cec notifier series through the media subsystem?
[07:39] <benjiG> hverkuil: yes you can do that
[07:42] <benjiG> hverkuil: I have add Patrice (sti DT maintainer) in copy for the DT patch
[07:45] <hverkuil> thanks
[09:05] <narmstrong> hverkuil: done, sent v5
[09:07] <hverkuil> narmstrong: thanks. I'll probably review it tomorrow and add my acks.
[09:08] <narmstrong> thanks
[09:11] <hverkuil> narmstrong: ping me if you haven't heard from me by Monday afternoon.
[09:14] <milian> hey there. when I use gstreamer with v4l2 with a HD Webcam C525, I have a really long delay at startup for every application that uses this. strace shows me tons of ioctl of this form: https://paste.kde.org/pr7bkawcj (this is just the head, it continues like this for a long long time)
[09:14] <milian> any idea what is going on there?
[09:14] <milian> or how I could influence this to make startup faster?
[09:14] <milian> note that I can reproduce this delay easily already with gst-launch-1.0 v4l2src ! xvimagesink
[09:14] <milian> is this a gstreamer issue? or something with v4l2?
[09:15] <milian> I notice that some other applications, presumably not using streamer, are not suffering from this, e.g. guvcviewer. so is this a setup question in the gstreamer pipeline?
[09:25] <milian> hm vlc also doesn't show this issue, I'll try to ask the gstreamer people
[09:30] <pinchartl> milian: it's a known gtsreamer issue with UVC devices
[09:30] <pinchartl> gstreamer tries all supported formats
[09:31] <pinchartl> and that's a costly operation with UVC cameras
[09:31] <milian> can you point me at the issue report? I couldn't find anything on that
[09:31] <milian> i.e. my googling failed me so far
[09:31] <pinchartl> I can't sorry? I've discussed it maybe 5 years ago, I don't remember who with and where
[09:31] <milian> ok hm
[09:36] <milian> pinchartl: http://gstreamer-devel.966125.n4.nabble.com/Decreasing-startup-delay-with-v4lsrc-td4681453.html - thanks
[11:46] <pH5> Is VIDIOC_SUBDEV_G_FMT supposed to return the field height (288 or 240 instead of the full frame height of 576 or 480) for V4L2_FIELD_ALTERNATE field order?
[11:47] <hverkuil> pH5: I would expect so, since that's what VIDIOC_G_FMT will return as well.
[11:48] <hverkuil> the frame height makes no sense in combination with FIELD_ALT.
[11:48] <pH5> How about VIDIOC_SUBDEV_ENUM_FRAME_SIZES ?
[11:48] <pH5> And V4L2_SEL_TGT_CROP ?
[11:49] <hverkuil> crop is in frame coordinates, not field.
[11:49] <hverkuil> does frame_sizes make sense when used with FIELD_ALT? That usually means an HDTV/SDTV input, which typically does not implement ENUM_FRAME_SIZES.
[11:49] <pH5> Ok, so in the spec "frame" is full frame as opposed to field, but "image" could be the field?
[11:50] <hverkuil> I've never seen it used with interlaced formats, in fact.
[11:50] <hverkuil> yes.
[11:50] <hverkuil> No guarantee if the right terminology is always used :-)
[11:50] <pH5> I want to make the i.MX6 CSI handle FIELD_ALT input (but output SEQ_BT or SEQ_TB depending on std)
[11:50] <pH5> with cropping and scaling
[11:51] <hverkuil> Well, you're the first to do that.
[11:51] <pH5> I hate interlacing :)
[11:52] <hverkuil> Do you really need it? Handling interlaced formats is tricky, so I wouldn't implement it unless there is a good reason.
[11:53] <hverkuil> Main guideline for interlacing: everything uses frame coordinates, except for the actual buffers being transferred. So G/S/TRY_FMT all use half height for FIELD_ALTERNATE.
[11:53] <hverkuil> The vivid driver does it correctly (although it doesn't use subdevs of course).
[11:54] <hverkuil> v4l2-compliance also handles this correctly.
[11:54] <pH5> Yes, I have a TPV5150 connected to i.MX6, and since commit 4f57d27be2a5 that produces FIELD_ALT output, and the CSI can only sync to full frames.
[11:54] <pH5> Excellent, thanks for clearing this up.
[11:54] <hverkuil> Well, good luck! :-)
[12:35] <pinchartl> pH5: from your question I assume that the documentation wasn't clear on the topic. it would be great if you had time to submit a documentation patch :-)
[12:44] <pH5> pinchartl: already on it, if only to make sure I understood correctly from the patch feedback.
[12:58] <eduardas_m> hello, where do I get (how do I install the Virtual Video Test Driver (vivid)) on my Ubuntu 14.04 system? I do not see it among the v4l-utils source
[12:59] <hverkuil> eduardas_m: it's a kernel module, but not all distros build that driver.
[12:59] <hverkuil> Try (as root): modprobe vivid
[12:59] <hverkuil> If it is not found, then your distro doesn't build it and you have to compile the kernel yourself.
[13:07] <eduardas_m> hverkuil: understood, thank you
[15:33] *** benjiG has left 
[16:37] <pinchartl> pH5: thanks a lot!