From: Nick Pelling <nickpelling@nanodome.com>
To: linux-media@vger.kernel.org
Subject: Missing /dev/video[N] devices...?
Date: Wed, 02 Mar 2011 17:25:28 +0000 [thread overview]
Message-ID: <9ffr5a$elf5vr@out1.ip06ir2.opaltelecom.net> (raw)
Hi everyone,
Problem solved - the boot sequence didn't have a makedev, so the
/dev/video[N] nodes weren't getting automatically created. A few
"mknod c X Y" commands later, all the /dev/video[N] items are in place. :-)
Cheers, ....Nick Pelling....
next reply other threads:[~2011-03-02 17:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 17:25 Nick Pelling [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-02 16:16 Missing /dev/video[N] devices...? Nick Pelling
2011-03-02 18:54 ` Andy Walls
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='9ffr5a$elf5vr@out1.ip06ir2.opaltelecom.net' \
--to=nickpelling@nanodome.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox