From: Ian Pickworth <ian@pickworth.me.uk>
To: Linux and Kernel Video <video4linux-list@redhat.com>
Subject: How to force the device assignment with V4l V2.0?
Date: Fri, 17 Oct 2008 14:41:13 +0100 [thread overview]
Message-ID: <48F895F9.5010205@pickworth.me.uk> (raw)
I'm having a play with the latest code from hg on the 2.6.27 kernel,
Gentoo installation. This is triggered by the gspca driver being
absorbed into the main tree (which is a great move by the way).
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.
However, when trying a recent hg snapshot, the sequence of loading the
modules does not change what the V4l driver is doing when loaded.
Looking at dmesg, I see that the new drivers are doing quite a lot of
detecting work themselves - it looks like they pick up the USB device
first regardless of the module blacklist/load sequence I have specified.
So, question is: Is there a preferred way of forcing the sequence of
device assignment in V4L these days? I need the cx88 to be /dev/video0
and the USB webcam to be /dev/video1 - otherwise all sorts of programs
get confused.
Many thanks
Regards
Ian
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next reply other threads:[~2008-10-17 13:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 13:41 Ian Pickworth [this message]
2008-10-17 14:00 ` How to force the device assignment with V4l V2.0? Pádraig Brady
2008-10-17 14:09 ` Ian Pickworth
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=48F895F9.5010205@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox