From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Bas Bloemsaat <bas.bloemsaat@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Vicam driver, device
Date: Sat, 02 Sep 2006 15:12:22 -0300 [thread overview]
Message-ID: <1157220743.15841.118.camel@praia> (raw)
In-Reply-To: <7c4668e50609021101j2b8c561er94d41ca95aca2b1b@mail.gmail.com>
Hi, Blas,
Em Sáb, 2006-09-02 às 20:01 +0200, Bas Bloemsaat escreveu:
> Hi,
>
> I have an old webcam, a Compro PS39U. By windows it's recognized as
> vicam and works with the vicam driver. With Linux it didn't work.
> lsusb showed that it identifies different than camera's recognized by
> the vicam driver. So I added the usb id to vicam.c, and it now
> produces images through the driver under Linux too. It's still a
> shitty camera though.
>
> I'm submitting the change, maybe someone else has this camera and
> want's to use it.
Although this is really a trivial patch, it would be nice if you can
sign your patch (on our wiki you can have more info about patch
submission procedure:
http://linuxtv.org/v4lwiki/index.php/How_to_submit_patches). Basically,
you should send at the email a line with:
Signed-off-by: Your name <name@yoursite.com>
Also, it would be nice if you add a comment above the new entry at vicam
PCI table a short comment describing the new device, like, for example:
/* Compro PS39U */
>
> Regards,
> Bas
>
> --- drivers/media/video/usbvideo/vicam.c 2006-08-23 23:16:33.000000000 +0200
> +++ drivers/media/video/usbvideo/vicam.c.compro 2006-09-02
> 19:45:20.000000000 +0200
> @@ -60,6 +60,8 @@
> /* Define these values to match your device */
> #define USB_VICAM_VENDOR_ID 0x04c1
> #define USB_VICAM_PRODUCT_ID 0x009d
> +#define USB_COMPRO_VENDOR_ID 0x0602
> +#define USB_COMPRO_PRODUCT_ID 0x1001
>
> #define VICAM_BYTES_PER_PIXEL 3
> #define VICAM_MAX_READ_SIZE (512*242+128)
> @@ -1254,6 +1256,7 @@
> /* table of devices that work with this driver */
> static struct usb_device_id vicam_table[] = {
> {USB_DEVICE(USB_VICAM_VENDOR_ID, USB_VICAM_PRODUCT_ID)},
> + {USB_DEVICE(USB_COMPRO_VENDOR_ID, USB_COMPRO_PRODUCT_ID)},
> {} /* Terminating entry */
> };
Cheers,
Mauro.
--
VGER BF report: U 0.5
next prev parent reply other threads:[~2006-09-02 18:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-02 18:01 Bas Bloemsaat
2006-09-02 18:12 ` Mauro Carvalho Chehab [this message]
[not found] ` <7c4668e50609030111i5f3cb079j76e9c8651cf8d6b4@mail.gmail.com>
2006-09-03 8:38 ` Bas Bloemsaat
2006-09-03 16:30 ` Nick Warne
[not found] ` <7c4668e50609041128j4e382815me92cdbabb53d662d@mail.gmail.com>
2006-09-04 18:35 ` Nick Warne
2006-09-02 19:55 ` Pavel Machek
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=1157220743.15841.118.camel@praia \
--to=mchehab@infradead.org \
--cc=bas.bloemsaat@gmail.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®