[meta-freescale] mxc_v4l2_capture sometimes not being modprobed

John Weber rjohnweber at gmail.com
Mon Jun 9 10:35:15 PDT 2014

Hi Eric,

On 6/9/14, 12:16 PM, Eric Nelson wrote:
> Hi all,
> On 06/09/2014 06:52 AM, Otavio Salvador wrote:
>> On Mon, Jun 9, 2014 at 10:51 AM, Otavio Salvador
>> <otavio at ossystems.com.br> wrote:
>>> On Sun, Jun 8, 2014 at 12:51 PM, John Weber <rjohnweber at gmail.com> wrote:
>>>> On 6/6/14, 6:10 PM, Eric Nelson wrote:
>>>>> On 06/05/2014 01:33 PM, Eric Nelson wrote:
>>>>>> On 06/05/2014 01:30 PM, John Weber wrote:
>>>>>>> <snip>
>>>>>>> I think you're right, but as far as I know the only other entity that
>>>>>>> could confirm this would be Boundary Devices.  Eric - do you see this
>>>>>>> same issue when connecting your camera to Nitrogen6x?
>>>>>> I've kinda followed this thread, but I'm kinda buried and it will take
>>>>>> a day or two for me to confirm or deny this.
>>>>> I just tested across a dozen assorted reboots/resets/power-cycles
>>>>> and didn't see the issue with an OV5642 parallel camera and 3.10.17.
>>>>> I **don't** have udev-cache configured.
>>>> I suspect that we will need to disable it on Wandboard as well.
>>> This is not a good fix.
>>> I added a patch, for OE-Core/Poky, attached; please confirm it fixes it.
> I just tested again on an image with udev-cache, and don't see any
> issues on a Nitrogen6x board (CSI camera).
> I'm not sure what's different about my environment.
> Regards,
> Eric
Not sure either, but are you testing with the parallel CSI or MIPI CSI camera?  
Could there be a difference in the how the drivers are loaded?


More information about the meta-freescale mailing list