From: Paul Check <paul@openstreet.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Video devices
Date: Tue, 11 Jul 2006 02:08:02 +0000 [thread overview]
Message-ID: <44B30802.2030905@openstreet.com> (raw)
In-Reply-To: <44B2FA34.8090405@openstreet.com>
Kay Sievers wrote:
>On Mon, 2006-07-10 at 21:09 -0400, Paul Check wrote:
>
>
>>Hi: I have a webcam and a pvr350 capture card (modules pwc and ivtv
>>resp) attached to my machine, running 2.6.16 kernel and udev. The
>>classic problem is that these modules get assigned to /dev/video0 and
>>/dev/video1 in seemingly arbitrary ways. I've tried forcing module
>>loading at boot time but still can't seem to get one to load first
>>consistently.
>>
>>So, I turned to writing udev rules and followed the "writing udev rules"
>>document. My goal would be to have udev just symlink
>>
>>/dev/webcam0 to /dev/videoM
>>
>>and
>>
>>/dev/pvr0 to /dev/videoN,
>>
>>where M and N are 0 and 1, assignmed however the system so chooses.
>>
>>I've tried writing udev rules to symlink, but they didn't work. Upon
>>further investigation I don't actually see any rules to create the video
>>devices in the /etc/udev/rules.d/ directory. And yet, they are created.
>>Also, I see they are mentioned in /etc/udev/devfs.rules, but there is no
>>symlink to this file in the rules.d/ directory.
>>
>>So, how do the video devices get created here? Is there some devfs
>>left-over? Perhaps if I knew where the /dev/video?'s are being created
>>I'd be able to figure out how to symlink to them?! I'm running debian
>>unstable, fully updated.
>>
>>
>
>Udev does not need any rule to work, it just uses as the default the
>kernel device name and creates the node owned by root.
>
>Kay
>
>
>
Hi Kay: Thanks for the reply. I really don't understand what you mean
though.
Let me show what I did:
I created /etc/udev/local-late.rules containing:
KERNEL="ivtv", SYMLINK+="pvr0", GROUP="video"
KERNEL="pwc", SYMLINK+="webcam0", GROUP="video"
then created a symlink in /etc/udev/rules.d to that file:
z10_local-late.rules -> ../local-late.rules
and yet the /dev/webcam0 and /dev/pvr0 are not created.
Am I missing something there? I thought that perhaps since the video
devices are created as part of the MAKEDEV script my symlinks wouldn't
work. If not that, then why not, or...how to fix?
Thanks, Paul
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2006-07-11 2:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-11 1:09 Video devices Paul Check
2006-07-11 1:21 ` Kay Sievers
2006-07-11 2:08 ` Paul Check [this message]
2006-07-11 12:06 ` 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=44B30802.2030905@openstreet.com \
--to=paul@openstreet.com \
--cc=linux-hotplug@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.