<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: v4l2-compliance failures in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/v4l2-compliance-failures/m-p/245756#M21363</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Daiane,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your response.&amp;nbsp; My apologies that I didn't see it in my inbox until now!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I encountered this problem, I was attempting to run various VOIP stacks on the and IMX6 EVM.&amp;nbsp; One was using SDL, which failed when attempting to invoke v4l.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I am able to get back to this, I will message you again with more details on the error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again,&lt;/P&gt;&lt;P&gt;Ken&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 16 Dec 2013 18:34:13 GMT</pubDate>
    <dc:creator>kenfrederickson</dc:creator>
    <dc:date>2013-12-16T18:34:13Z</dc:date>
    <item>
      <title>v4l2-compliance failures</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/v4l2-compliance-failures/m-p/245754#M21361</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm trying to troubleshoot issues with capturing and displaying video on an i.MX6 Sabre board.&amp;nbsp; Video drivers are not my forte.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We're using Yocto to build our bsp and I have added the v4l2-utils packages and dependencies.&amp;nbsp; A result of adding this package is the v4l2-compliance tool.&amp;nbsp; When running that tool, there are several failures.&amp;nbsp; Please see attached.&amp;nbsp; I have read in &lt;A _jive_internal="true" data-containerid="2004" data-containertype="14" data-objectid="295171" data-objecttype="1" href="https://community.nxp.com/thread/295171#300707"&gt;other posts&lt;/A&gt; that claim success despite v4l2-compliance issues.&amp;nbsp; &lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I also performed an strace on an application that is attempting to access /dev/video0.&amp;nbsp; Please see attached.&amp;nbsp; It is obvious that the driver is not providing some of the necessary functionality, namely VIDIOC_TRY_FMT and VIDIOC_QUERYCTRL.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My question is, do I have a broken driver that needs to be patched or are these failures normal?&amp;nbsp; Has anyone experienced this issue?&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks. &lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Original Attachment has been moved to: &lt;A _jive_internal="true" href="https://community.nxp.com/docs/DOC-336431"&gt;AppStrace.zip&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Original Attachment has been moved to: &lt;A _jive_internal="true" href="https://community.nxp.com/docs/DOC-336431"&gt;v4l2ComplianceOutput.zip&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Jun 2013 18:24:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/v4l2-compliance-failures/m-p/245754#M21361</guid>
      <dc:creator>kenfrederickson</dc:creator>
      <dc:date>2013-06-28T18:24:08Z</dc:date>
    </item>
    <item>
      <title>Re: v4l2-compliance failures</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/v4l2-compliance-failures/m-p/245755#M21362</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As I know, linux-imx kernel is not completly &lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif;"&gt;v4l2-compliance &lt;/SPAN&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What do you need? What are you trying to do? Let´s focus on what you want instead of classify compliance the the kernel?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 Aug 2013 16:16:27 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/v4l2-compliance-failures/m-p/245755#M21362</guid>
      <dc:creator>daiane_angolini</dc:creator>
      <dc:date>2013-08-23T16:16:27Z</dc:date>
    </item>
    <item>
      <title>Re: v4l2-compliance failures</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/v4l2-compliance-failures/m-p/245756#M21363</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Daiane,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your response.&amp;nbsp; My apologies that I didn't see it in my inbox until now!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I encountered this problem, I was attempting to run various VOIP stacks on the and IMX6 EVM.&amp;nbsp; One was using SDL, which failed when attempting to invoke v4l.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I am able to get back to this, I will message you again with more details on the error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again,&lt;/P&gt;&lt;P&gt;Ken&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Dec 2013 18:34:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/v4l2-compliance-failures/m-p/245756#M21363</guid>
      <dc:creator>kenfrederickson</dc:creator>
      <dc:date>2013-12-16T18:34:13Z</dc:date>
    </item>
  </channel>
</rss>

