All of lore.kernel.org
 help / color / mirror / Atom feed
* registered as /dev/video%d for all
@ 2008-02-29 21:00 Carl Karsten
  0 siblings, 0 replies; only message in thread
From: Carl Karsten @ 2008-02-29 21:00 UTC (permalink / raw)
  To: video4linux-list

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:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2008-02-29 21:01 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-02-29 21:00 registered as /dev/video%d for all Carl Karsten

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.