From: Ian Pickworth <ian@pickworth.me.uk>
To: Linux and Kernel Video <video4linux-list@redhat.com>
Subject: Re: How to force the device assignment with V4l V2.0?
Date: Fri, 17 Oct 2008 15:09:49 +0100 [thread overview]
Message-ID: <48F89CAD.5080202@pickworth.me.uk> (raw)
In-Reply-To: <48F89A75.1000100@draigBrady.com>
Pádraig Brady wrote:
> Ian Pickworth wrote:
>> I have two devices - a CX88 based Hauppauge TV PCI card, and a USB
>> webcam. In the "old" style drivers, I could force the loading of the two
>> modules (cx8800 and gspca) in a set sequence, using blacklist and
>> modules.autoload. This is enough to ensure that cx88 gets /dev/video0,
>> and the usb webcam gets /dev/video1.
>
> I use udev rules to give persistent names.
>
> Here is my /etc/udev/rules.d/video.rules file,
> which creates /dev/webcam and /dev/tvtuner as appropriate.
>
> KERNEL=="video*" SYSFS{name}=="USB2.0 Camera", NAME="video%n", SYMLINK+="webcam"
> KERNEL=="video*" SYSFS{name}=="em28xx*", NAME="video%n", SYMLINK+="tvtuner"
>
> To find distinguishing attributes to match on use:
>
> echo /sys/class/video4linux/video* | xargs -n1 udevinfo -a -p
I did think about that, but the problem is that applications want to see
/dev/video(n) style names. Especially TV Time that (I think) uses
/dev/video - set to link to /dev/video0 by the standard udev rules.
I could be wrong - how does one get these programs to recognize the
custom links created by udev rules? Or, is it possible to get udev to
change /dev/video(n) assignment based on udev rules? I'm thinking not,
since one of the things you can match on is KERNEL.
Regards
Ian
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2008-10-17 14:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 13:41 How to force the device assignment with V4l V2.0? Ian Pickworth
2008-10-17 14:00 ` Pádraig Brady
2008-10-17 14:09 ` Ian Pickworth [this message]
2008-10-17 15:51 ` Ian Pickworth
2008-10-18 4:56 ` Brandon Philips
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=48F89CAD.5080202@pickworth.me.uk \
--to=ian@pickworth.me.uk \
--cc=video4linux-list@redhat.com \
/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.