Hi,<br><br><div class="gmail_quote">On Fri, Oct 8, 2010 at 5:42 PM, Gary Thomas <span dir="ltr"><<a href="mailto:gary@mlbassoc.com">gary@mlbassoc.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I have an old USB webcam (Logitech QuickCam Chat) that I'm<br>
trying to use with v4l2src. When I run it on slightly different<br>
versions of Linux & gst-plugins, I get very different results.<br>
<br></blockquote><div> </div><div>..snip..<br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">On x86 Linux 2.6.34, gstreamer-0.10.30, gstreamer-plugins-good-0.10.25,<br>
I get these:<br>
0:00:00.037755702 22728 0x9eec050 DEBUG v4l2 gstv4l2object.c:882:gst_v4l2_object_fill_format_list:<v4l2src0> getting src format enumerations<br>
0:00:00.037806177 22728 0x9eec050 INFO v4l2 gstv4l2object.c:919:gst_v4l2_object_fill_format_list:<v4l2src0> got 4 format(s):<br>
0:00:00.037831421 22728 0x9eec050 INFO v4l2 gstv4l2object.c:925:gst_v4l2_object_fill_format_list:<v4l2src0> YU12 (emulated)<br>
0:00:00.037853538 22728 0x9eec050 INFO v4l2 gstv4l2object.c:925:gst_v4l2_object_fill_format_list:<v4l2src0> YV12 (emulated)<br>
0:00:00.037886708 22728 0x9eec050 INFO v4l2 gstv4l2object.c:925:gst_v4l2_object_fill_format_list:<v4l2src0> BGR3 (emulated)<br>
0:00:00.037908230 22728 0x9eec050 INFO v4l2 gstv4l2object.c:925:gst_v4l2_object_fill_format_list:<v4l2src0> RGB3 (emulated)<br></blockquote><div><br>..snip..<br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
On ARM Linux 2.6.32, gstreamer-0.10.30, gst-plugins-good-0.10.25,<br>
I get this (but not useful) trace:<br>
0:00:00.180328399 741 0x15050 INFO v4l2 gstv4l2object.c:919:gst_v4l2_object_fill_format_list:<v4l2src0> got 2 format(s):<br>
0:00:00.180450469 741 0x15050 INFO v4l2 gstv4l2object.c:925:gst_v4l2_object_fill_format_list:<v4l2src0> GBRG<br>
0:00:00.180603057 741 0x15050 INFO v4l2 gstv4l2object.c:925:gst_v4l2_object_fill_format_list:<v4l2src0> S561<br>
0:00:00.180725127 741 0x15050 DEBUG v4l2 gstv4l2object.c:1151:gst_v4l2_object_v4l2fourcc_to_structure: Unknown fourcc 0x47524247 GBRG<br>
0:00:00.184051543 741 0x15050 DEBUG v4l2src gstv4l2src.c:578:gst_v4l2src_get_caps:<v4l2src0> unknown format 1196573255<br>
0:00:00.184387236 741 0x15050 DEBUG v4l2 gstv4l2object.c:1151:gst_v4l2_object_v4l2fourcc_to_structure: Unknown fourcc 0x31363553 S561<br>
0:00:00.184509307 741 0x15050 DEBUG v4l2src gstv4l2src.c:578:gst_v4l2src_get_caps:<v4l2src0> unknown format 825636179<br>
0:00:00.184661894 741 0x15050 INFO v4l2src gstv4l2src.c:584:gst_v4l2src_get_caps:<v4l2src0> probed caps: EMPTY<br>
<br>
Same camera, same (+/- kernel version) kernel modules, vastly<br>
different behaviour. What gives?<br></blockquote><div><br>the debug log is pretty self-explanatory: the webcam is using different color formats wrt different architectures. Assuming the webcam sensor/phy are the same and the bus used is the same (USB), I'd give a check on the differences in the kernel module between the two releases (2.6.32 / 2.6.34). It's also possible that the driver has some compilation flags which use different paths wrt ARM or x86.<br>
<br>Regards <br></div></div>