public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: Valentin Longchamp <valentin.longchamp@epfl.ch>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	"linux-hotplug@vger.kernel.org" <linux-hotplug@vger.kernel.org>
Subject: Re: [Q] udev and soc-camera
Date: Thu, 28 Jan 2010 15:13:50 +0100	[thread overview]
Message-ID: <ac3eb2511001280613p698ad22fmb436650122f3a2eb@mail.gmail.com> (raw)
In-Reply-To: <4B61990E.5010604@epfl.ch>

On Thu, Jan 28, 2010 at 15:02, Valentin Longchamp
<valentin.longchamp@epfl.ch> wrote:
> Kay Sievers wrote:
> Thanks a lot Kay, you pointed me exactly where I needed to watch.
> OpenEmbedded adds udevadm trigger a big list of --susbsystem-nomatch options
> as soon as you are not doing your first boot anymore and video4linux is
> among them.
>
> I either have to remove this option in the script or understand why my other
> /dev nodes are kept (ttys are doing fine with the same treatment for
> instance) and not video4linux ones (it looks like they are using DEVCACHE or
> something like this). But I would prefer the first alternative since cameras
> may be unplugged on some robots.

Really, that logic sounds awfully wrong. Any /dev-caching and games
with skipping selected subsystems at coldplug can never reliably work
as you have found out. :) You should definitely go for devtmpfs
instead of such needless and misguided hacks, if a plain "udevadm
trigger" does not work for some reason.

Good luck.
Kay

      reply	other threads:[~2010-01-28 14:19 UTC|newest]

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

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=ac3eb2511001280613p698ad22fmb436650122f3a2eb@mail.gmail.com \
    --to=kay.sievers@vrfy.org \
    --cc=linux-hotplug@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=valentin.longchamp@epfl.ch \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox