From: Carl Karsten <carl@personnelware.com>
To: video4linux-list@redhat.com
Subject: [patch] vivi: registered as /dev/video%d
Date: Fri, 29 Feb 2008 18:18:17 -0600 [thread overview]
Message-ID: <47C8A0C9.4020107@personnelware.com> (raw)
Now that vivi can be something other than /dev/video0, it should tell us what it
is. This works for n_devs>1.
sudo modprobe vivi n_devs=3
[115041.616401] vivi: V4L2 device registered as /dev/video0
[115041.616445] vivi: V4L2 device registered as /dev/video1
[115041.616481] vivi: V4L2 device registered as /dev/video2
[115041.616486] Video Technology Magazine Virtual Video Capture Board
successfully loaded.
Carl K
diff -r 127f67dea087 linux/drivers/media/video/vivi.c
--- a/linux/drivers/media/video/vivi.c Tue Feb 26 20:43:56 2008 +0000
+++ b/linux/drivers/media/video/vivi.c Fri Feb 29 18:15:01 2008 -0600
@@ -47,6 +47,8 @@
#if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 20)
#include <linux/freezer.h>
#endif
+
+#define MODULE_NAME "vivi"
/* Wake up at about 30 fps */
#define WAKE_NUMERATOR 30
@@ -1338,6 +1340,7 @@ static int __init vivi_init(void)
video_nr++;
dev->vfd = vfd;
+ printk(KERN_INFO "%s: V4L2 device registered as /dev/video%d\n",
MODULE_NAME, vfd->minor);
}
if (ret < 0) {
--
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-03-01 0:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-01 0:18 Carl Karsten [this message]
2008-03-02 6:34 ` [patch] vivi: registered as /dev/video%d Carl Karsten
2008-03-04 14:25 ` Mauro Carvalho Chehab
2008-05-28 20:15 ` Carl Karsten
2008-05-28 20:37 ` Mauro Carvalho Chehab
2008-05-28 22:03 ` Carl Karsten
2008-05-28 22:59 ` hermann pitton
[not found] ` <483DEB53.40604@personnelware.com>
[not found] ` <1212021382.5745.13.camel@pc10.localdom.local>
2008-05-31 3:59 ` Carl Karsten
2008-05-31 6:37 ` Carl Karsten
2008-06-01 4:38 ` hermann pitton
2008-06-10 0:02 ` Carl Karsten
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=47C8A0C9.4020107@personnelware.com \
--to=carl@personnelware.com \
--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.