All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carl Karsten <carl@personnelware.com>
To: video4linux-list@redhat.com
Subject: registered as /dev/video%d for all
Date: Fri, 29 Feb 2008 15:00:39 -0600	[thread overview]
Message-ID: <47C87277.2020007@personnelware.com> (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:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

                 reply	other threads:[~2008-02-29 21:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=47C87277.2020007@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.