From: Jean-Francois Moine <moinejf@free.fr>
To: Theodore Kilgore <kilgota@banach.math.auburn.edu>
Cc: Andy Walls <awalls@radix.net>, Linux Media <linux-media@vger.kernel.org>
Subject: Re: [PATCH] to add support for certain Jeilin dual-mode cameras.
Date: Mon, 3 Aug 2009 10:39:54 +0200 [thread overview]
Message-ID: <20090803103954.7150909e@tele> (raw)
In-Reply-To: <alpine.LNX.2.00.0908021302390.29819@banach.math.auburn.edu>
On Sun, 2 Aug 2009 14:12:28 -0500 (CDT)
Theodore Kilgore <kilgota@banach.math.auburn.edu> wrote:
[snip]
> > - as there is only one vend:prod, one line is enough in gspca.txt.
>
> This is a question about which I have been curious for quite some
> time, and I think that now is a good time to ask it.
>
> Just what policy do we have about this? The information which links
> brand and model to driver ought to be presented somewhere. If it does
> not go into gspca.txt then where exactly is the appropriate place to
> put said information?
[snip]
Hi Theodore,
gspca.txt has been defined only to know which subdriver has to be
generated for a webcam that a user already owns.
The trade name of the webcams are often not clear enough (look at all
the Creative varieties). So, the user has just to plug her webcam and
with the vend:prod ID, she will know which driver she has to generate
(you may say that there are already tools which do the job, as easycam,
but I do not think they are often used).
The device list of the other drivers (CARDLIST.xx) are not sorted and
their format (numbered list) does not facilitate this job. So, I
prefered a list sorted by vend:prod.
In gspca.txt, the 3rd column contains the webcam names. As you can see,
it is a comma separated list, so, you may put here all the names you may
know. But, is it useful? I think that the webcam names should be only
in the file usb.ids which comes with the usbutils.
To go further, there should be a general file which should contain all
the usb (and pci) devices and their associated drivers. This
information exists in /lib/modules/`uname -r`/modules.usbmap when all
drivers are generated. So, we just need a tool (and a guy!) to maintain
this general file...
Best regards.
--
Ken ar c'hentañ | ** Breizh ha Linux atav! **
Jef | http://moinejf.free.fr/
next prev parent reply other threads:[~2009-08-03 8:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090418183124.1c9160e3@free.fr>
2009-08-01 21:56 ` [PATCH] to add support for certain Jeilin dual-mode cameras Theodore Kilgore
2009-08-02 8:33 ` Jean-Francois Moine
2009-08-02 19:12 ` Theodore Kilgore
2009-08-03 8:39 ` Jean-Francois Moine [this message]
2009-08-03 16:01 ` Theodore Kilgore
2009-08-03 17:26 ` Mauro Carvalho Chehab
2009-08-03 19:46 ` Theodore Kilgore
2009-08-03 21:59 ` Mauro Carvalho Chehab
2009-08-04 5:45 ` Theodore Kilgore
2009-08-02 20:37 ` [PATCH] to add support for certain Jeilin dual-mode cameras. (resubmit) Theodore Kilgore
2009-08-02 13:25 ` [PATCH] to add support for certain Jeilin dual-mode cameras Alexey Klimov
2009-08-03 6:30 ` Jean-Francois Moine
2009-08-03 12:11 ` Mauro Carvalho Chehab
2009-08-04 6:51 ` Alexey Klimov
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=20090803103954.7150909e@tele \
--to=moinejf@free.fr \
--cc=awalls@radix.net \
--cc=kilgota@banach.math.auburn.edu \
--cc=linux-media@vger.kernel.org \
/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