All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Poky Project <poky@yoctoproject.org>
Subject: Debugging udev
Date: Tue, 30 Aug 2011 11:38:19 -0600	[thread overview]
Message-ID: <4E5D200B.20209@mlbassoc.com> (raw)

I'm having trouble with udev creating all the devices I need in
my system.  Based on the latest master, using udev 164.

My system is based on the 3.0 kernel (mainline, not yocto) with
Video4Linux enabled with OMAP3 ISP.  This creates a bunch of
special devices:
   # ls /sys/class/video4linux/
   v4l-subdev0  v4l-subdev3  v4l-subdev6  video0       video3       video6
   v4l-subdev1  v4l-subdev4  v4l-subdev7  video1       video4
   v4l-subdev2  v4l-subdev5  v4l-subdev8  video2       video5
However, udev is not actually creating the device nodes.

Any ideas why?
Any hints on how to debug this?

Thanks

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


             reply	other threads:[~2011-08-30 17:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-30 17:38 Gary Thomas [this message]
2011-09-03 10:20 ` Debugging udev Robert Berger
2011-09-03 17:02   ` Koen Kooi
2011-09-03 20:01     ` Robert Berger

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=4E5D200B.20209@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=poky@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.