All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Weber <rjohnweber@gmail.com>
To: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: mxc_v4l2_capture sometimes not being modprobed
Date: Sun, 25 May 2014 22:42:31 -0500	[thread overview]
Message-ID: <5382B827.2030302@gmail.com> (raw)

meta-freescalers:

I'm seeing a behavior that I can't easily explain.  I'm not seeing the mxc_v4l2_capture drivers and dependent ipu drivers being automatically modprobed on Wandboard during a majority of system startups (but not all).  I was under the impression that this should be done by udev, but for some reason it seems to either fail or is skipped.

I can force the driver to be loaded at startup by adding the name of the driver in a line in /etc/modules.  This works to load the driver every time at startup, but I'm fairly certain that this is not the most ideal approach because (A) I have to write a recipe to make the change to /etc/modules and (B) it does not explain why the driver load works sometimes, but not all of the time.

Any ideas?

John



             reply	other threads:[~2014-05-26  3:49 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-26  3:42 John Weber [this message]
2014-06-05 17:34 ` mxc_v4l2_capture sometimes not being modprobed Otavio Salvador
2014-06-05 18:05   ` John Weber
2014-06-05 18:08     ` Otavio Salvador
2014-06-05 18:14       ` John Weber
2014-06-05 18:17         ` Otavio Salvador
2014-06-05 18:23           ` John Weber
2014-06-05 18:38             ` Otavio Salvador
2014-06-05 19:10               ` John Weber
2014-06-05 19:34                 ` Otavio Salvador
2014-06-05 20:30                   ` John Weber
2014-06-05 20:33                     ` Eric Nelson
2014-06-05 20:40                       ` John Weber
2014-06-06 23:10                       ` Eric Nelson
2014-06-08 15:51                         ` John Weber
2014-06-09 13:51                           ` Otavio Salvador
2014-06-09 13:52                             ` Otavio Salvador
2014-06-09 16:00                               ` John Weber
2014-06-09 17:16                               ` Eric Nelson
2014-06-09 17:35                                 ` John Weber
2014-06-09 17:49                                   ` Eric Nelson
2014-06-09 17:59                                     ` John Weber
2014-06-09 18:09                                       ` Eric Nelson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5382B827.2030302@gmail.com \
    --to=rjohnweber@gmail.com \
    --cc=meta-freescale@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.