Skip to contentSkip to conversation

registered as /dev/video%d for all

DISCUSSION Carl Karsten 1 participant 1 message Feb 29, 2008 Media (V4L/DVB)

lore
Share & tools
lore
#0 lore raw

I want to patch vivi.c to identify what /dev it attaches itself to.

Current:

1342 if (ret < 0) {
1343 vivi_release();
1344 printk(KERN_INFO "Error %d while loading vivi driver\n", ret);
1345 } else
1346 printk(KERN_INFO "Video Technology Magazine Virtual Video "
1347 "Capture Board successfully loaded.\n");
1348 return ret;

http://www.video4linux.org/browser/linux/drivers/media/video/vivi.c#L1342

In looking at the other drivers, I see each has it's own "module loaded" code.
Would it make sense to make a generic bit of code that can be included in
every driver?

w9968cf.c seems to have the most detail and might be good for use on all others:

* USB probe and V4L registration, disconnect and id_table[] definition *
...

w9968cf.c DBG(2, "V4L device registered as /dev/video%d", cam->v4ldev->minor)

http://www.video4linux.org/browser/linux/drivers/media/video/w9968cf.c#L3577

Or does each driver really need it's own?

Carl K

--
video4linux-list mailing list
Unsubscribe mailto:[email protected]?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list