public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Reinhard Katzmann <suamor@web.de>
To: gspca list <linux-media@vger.kernel.org>
Subject: Re: [GSPCA] Driver Development for Speed Link VAD Laplace
Date: Fri, 15 May 2009 15:41:26 +0200	[thread overview]
Message-ID: <4A0D7106.2030702@web.de> (raw)
In-Reply-To: <62e5edd40905071238l3bc3a154g8247e5e4399a068b@mail.gmail.com>

Hi Erik,

Erik Andrén wrote:
>> I have searched for some more hardware information than from the vendor
>> available but in vain (though the cam is about 1 year old already).
>> I know that especially the video format the webcam delivers would be
>> important to know for driver development.
>>
>> If there are any (freeware) tools available except those USB sniffers to
>> find out any more hardware details please let me know, so I can help
>> with the driver.
>>
>
> Hi,
> If possible, you can open the case and inspect what chips that are inside.
> That should give you a head start.
>

Thanks for the hint. It was a bit difficult but with the help of my
friends we managed to open the CAM without any visible harm and got
the following chip information:

Main chip (Large)

EMPIA EM2765
6Z523-500
0711-118G

Little chips
IDT
STAC9753AX
MPG
E10745Z
UT10953

I also updated the wiki and included some pics.
http://linuxtv.org/wiki/index.php/VAD_Laplace

Regards,

Reinhard
-- 
Software-Engineer, Developer of User Interfaces
Project: Canorus - the next generation music score editor - 
http://canorus.berlios.de
GnuPG Public Key available on request



      reply	other threads:[~2009-05-15 13:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-07 17:35 [GSPCA] Driver Development for Speed Link VAD Laplace Reinhard Katzmann
2009-05-07 19:38 ` Erik Andrén
2009-05-15 13:41   ` Reinhard Katzmann [this message]

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=4A0D7106.2030702@web.de \
    --to=suamor@web.de \
    --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