All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valentin Longchamp <valentin.longchamp@epfl.ch>
To: linux-media@vger.kernel.org, linux-hotplug@vger.kernel.org
Subject: [Q] udev and soc-camera
Date: Wed, 27 Jan 2010 23:25:14 +0000	[thread overview]
Message-ID: <4B60CB5A.7000109@epfl.ch> (raw)

Hello,

I have a system that is built with OpenEmbedded where I use a mt9t031 
camera with the soc-camera framework. The mt9t031 works ok with the 
current kernel and system.

However, udev does not create the /dev/video0 device node. I have to 
create it manually with mknod and then it works well. If I unbind the 
device on the soc-camera bus (and then eventually rebind it), udev then 
creates the node correctly. This looks like a "timing" issue at "coldstart".

OpenEmbedded currently builds udev 141 and I am using kernel 2.6.33-rc5 
(but this was already like that with earlier kernels).

Is this problem something known or has at least someone already 
experienced that problem ?

Thanks and best regards

Val

-- 
Valentin Longchamp, PhD Student, EPFL-STI-LSRO1
valentin.longchamp@epfl.ch, Phone: +41216937827
http://people.epfl.ch/valentin.longchamp
MEB3494, Station 9, CH-1015 Lausanne

WARNING: multiple messages have this Message-ID (diff)
From: Valentin Longchamp <valentin.longchamp@epfl.ch>
To: linux-media@vger.kernel.org, linux-hotplug@vger.kernel.org
Subject: [Q] udev and soc-camera
Date: Thu, 28 Jan 2010 00:25:14 +0100	[thread overview]
Message-ID: <4B60CB5A.7000109@epfl.ch> (raw)

Hello,

I have a system that is built with OpenEmbedded where I use a mt9t031 
camera with the soc-camera framework. The mt9t031 works ok with the 
current kernel and system.

However, udev does not create the /dev/video0 device node. I have to 
create it manually with mknod and then it works well. If I unbind the 
device on the soc-camera bus (and then eventually rebind it), udev then 
creates the node correctly. This looks like a "timing" issue at "coldstart".

OpenEmbedded currently builds udev 141 and I am using kernel 2.6.33-rc5 
(but this was already like that with earlier kernels).

Is this problem something known or has at least someone already 
experienced that problem ?

Thanks and best regards

Val

-- 
Valentin Longchamp, PhD Student, EPFL-STI-LSRO1
valentin.longchamp@epfl.ch, Phone: +41216937827
http://people.epfl.ch/valentin.longchamp
MEB3494, Station 9, CH-1015 Lausanne

             reply	other threads:[~2010-01-27 23:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-27 23:25 Valentin Longchamp [this message]
2010-01-27 23:25 ` [Q] udev and soc-camera Valentin Longchamp
2010-01-28  9:18 ` Kay Sievers
2010-01-28  9:18   ` Kay Sievers
2010-01-28 14:02   ` Valentin Longchamp
2010-01-28 14:02     ` Valentin Longchamp
2010-01-28 14:13     ` Kay Sievers
2010-01-28 14:13       ` Kay Sievers

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=4B60CB5A.7000109@epfl.ch \
    --to=valentin.longchamp@epfl.ch \
    --cc=linux-hotplug@vger.kernel.org \
    --cc=linux-media@vger.kernel.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.