[meta-freescale] mxc_v4l2_capture sometimes not being modprobed

[Eric Nelson]

Hi all,

On 06/05/2014 01:30 PM, John Weber wrote:
> 
> On 6/5/14, 2:34 PM, Otavio Salvador wrote:
>> On Thu, Jun 5, 2014 at 4:10 PM, John Weber <rjohnweber at gmail.com> wrote:
>>> On 6/5/14, 1:38 PM, Otavio Salvador wrote:
>>>> On Thu, Jun 5, 2014 at 3:23 PM, John Weber <rjohnweber at gmail.com>
>>>> wrote:
>>>>> On 6/5/14, 1:17 PM, Otavio Salvador wrote:
>>>>>> On Thu, Jun 5, 2014 at 3:14 PM, John Weber <rjohnweber at gmail.com>
>>>>>> wrote:
>>>>>>> On 6/5/14, 1:08 PM, Otavio Salvador wrote:
>>>>>>>> On Thu, Jun 5, 2014 at 3:05 PM, John Weber <rjohnweber at gmail.com>
>>>>>>>> wrote:
>>>>>>>>> On 6/5/14, 12:34 PM, Otavio Salvador wrote:
>>>>>>>>>> On Mon, May 26, 2014 at 12:42 AM, John Weber
>>>>>>>>>> <rjohnweber at gmail.com>
>>>>>>>>>> wrote:
>>>>>>>>>>> meta-freescalers:
>>>>>>>>>>>
>>>>
>>>> <snip>
>>>>
>>>> Please apply following change in the udev init script:
>>>>
>>>> --- a/meta/recipes-core/udev/udev/init
>>>> +++ b/meta/recipes-core/udev/udev/init
>>>> @@ -103,7 +103,7 @@ case "$1" in
>>>>        udevadm control --env=STARTUP=1
>>>>        if [ "$not_first_boot" != "" ];then
>>>>                udevadm trigger --action=add --subsystem-nomatch=tty
>>>> --subsystem-nomatch=mem --subsystem-nomatch=vc
>>>> --subsystem-nomatch=vtconsole --subsystem-nomatch=misc
>>>> --subsystem-nomatch=dcon -
>>>> -            (udevadm settle --timeout=3; udevadm control
>>>> --env=STARTUP=)&
>>>> +            (udevadm settle; udevadm control --env=STARTUP=)&
>>>>        else
>>>>                udevadm trigger --action=add
>>>>                udevadm settle
>>>>
>>>>
>>> Nope - that doesn't help the problem.  The udevadm trigger line above
>>> includes "--subsystem-nomatch=platform" and if I remove that while
>>> keeping
>>> everything else the same, it works fine.
>> It kind of makes sense to me; if you keep the platform skip and remove
>> the background & job, does it work?
> If you mean, remove the timeout=3 on the udevadm settle, no.  If I keep
> the platform skip, it does not work at all.
> 
>>> I'd be interested to know if anyone else sees the same problem on other
>>> machines?
>> I bet it is not machine dependent.
>>
> 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.

Regards,


Eric