Lets get to it...

[JoJo jojo]

HI

what kind of microdia are you running?

Please reply to this with the following info
<usb vendor code> <bridge & sensor name> <webcam brand & model name>.
example:
0c45:627b, with SN9C201 bridge and OV7660 image sensor, found in Thinkpad Z61t

thats it no more.
(if you know more details about it, I have created pages, see them for
examples and add your webcam info in that manner)

-JoJo

[frectomex]

hi there :) trying to install a webcam on a pc running ubuntu 7.10.

<usb vendor code> 0c45:6027

<bridge & sensor name> SN9C102R (video controller)
(don`t know the senzor :( )

<webcam brand & model name> genius eye 310

[mrpurple]

hi mine web cam is in a assembled portable and is a Microdia
0c45:624f, that i did not let work.
i think to have the same sensor, but i don't know how to be sure of
that.
Thanks you
Mrpurple

[JoJo jojo]

Hi mrpurple

take a look here for the procedure to identify the bridge & sensor
https://groups.google.com/group/microdia/web/reverse-engineering-windows-drivers

-JoJo

[Cyro]

Hello,

Mine is:


<usb vendor code> 0c45:6253

<bridge> SN9C201
<sensor name> OV9650

<webcam brand & model name> Liteon 05P179 Found on an Asus
W5Fm


On my windows drivers inf file i found a lot of info that i do not
know is relevant, but anyway, here goes:

[SN]
;1.3 M
%USBPCamDesc% = SN.USBPCam,USB\VID_0c45&PID_6240 ; SN9C201 +
MI1300
%USBPCamDesc% = SN.USBPCam,USB\VID_0c45&PID_6242 ; SN9C201 +
MI1310
%USBPCamDesc% = SN.USBPCam,USB\VID_0c45&PID_624e ; SN9C201 +
SOI968
%USBPCamDesc% = SN.USBPCam,USB\VID_0c45&PID_624f ;
SN9C201 + OV9650
%USBPCamDesc% = SN.USBPCam,USB\VID_0c45&PID_6243 ; SN9C201 +
S5K4AAFX
%USBPCamDesc% = SN.USBPCam,USB\VID_0c45&PID_627f ;
EEPROM
%USBPCamDesc% = SN.USBPCam,USB\VID_0c45&PID_6253 ; SN9C201 +
OV9650
;VGA Sensor
%USBPCamDesc% = SN.USBPCam,USB\VID_0c45&PID_6270 ; SN9C201 +
MI0360
%USBPCamDesc% = SN.USBPCam,USB\VID_0c45&PID_627c ; SN9C201 +
HV7131R
%USBPCamDesc% = SN.USBPCam,USB\VID_0c45&PID_627b ; SN9C201 +
OV7660
%USBPCamDesc% = SN.USBPCam,USB\VID_0c45&PID_627a ; SN9C201 +
S5K53BEB
%USBPCamDesc% = SN.USBPCam,USB\VID_0c45&PID_624b ; SN9C201 +
CX1332

;
; Usb2.0 PC Camera with Audio Function
;
%USBPCamMicDesc% = SN.PCamMic,USB\VID_0c45&PID_6280&MI_00 ; SN9C202 +
MI1300
%USBPCamMicDesc% = SN.PCamMic,USB\VID_0c45&PID_6282&MI_00 ; SN9C202 +
MI1310
%USBPCamMicDesc% = SN.PCamMic,USB\VID_0c45&PID_628e&MI_00 ; SN9C202 +
SOI968
%USBPCamMicDesc% = SN.PCamMic,USB\VID_0c45&PID_628f&MI_00 ; SN9C202 +
OV9650
%USBPCamMicDesc% = SN.PCamMic,USB\VID_0c45&PID_628a&MI_00 ; SN9C202 +
ICM107
%USBPCamMicDesc% = SN.PCamMic,USB\VID_0c45&PID_62b0&MI_00 ; SN9C202 +
MI0360
%USBPCamMicDesc% = SN.PCamMic,USB\VID_0c45&PID_62bc&MI_00 ; SN9C202 +
HV7131R
%USBPCamMicDesc% = SN.PCamMic,USB\VID_0c45&PID_62bb&MI_00 ; SN9C202 +
Ov7660
%USBPCamMicDesc% = SN.PCamMic,USB\VID_0c45&PID_62ba&MI_00 ; SN9C202 +
S5K53BEB
%USBPCamMicDesc% = SN.PCamMic,USB\VID_0c45&PID_624b&MI_00 ; SN9C202 +
CX1332
%USBPCamMicDesc% = SN.PCamMic,USB\VID_0c45&PID_6283&MI_00 ; SN9C202 +
S5K4AAFX

[SN.NTx86.5.1]
;1.3 M
%USBPCamDesc% = SN.USBPCam.XP,USB\VID_0c45&PID_6240 ; SN9C201 +
MI1300
%USBPCamDesc% = SN.USBPCam.XP,USB\VID_0c45&PID_6242 ; SN9C201 +
MI1310
%USBPCamDesc% = SN.USBPCam.XP,USB\VID_0c45&PID_624f ; SN9C201 +
OV9650
%USBPCamDesc% = SN.USBPCam.XP,USB\VID_0c45&PID_624e ; SN9C201 +
SOI968
%USBPCamDesc% = SN.USBPCam.XP,USB\VID_0c45&PID_6243 ; SN9C201 +
S5K4AAFX
%USBPCamDesc% = SN.USBPCam.XP,USB\VID_0c45&PID_6253 ; SN9C201 +
OV9650
;VGA Sensor
%USBPCamDesc% = SN.USBPCam.XP,USB\VID_0c45&PID_6270 ; SN9C201 +
MI0360
%USBPCamDesc% = SN.USBPCam.XP,USB\VID_0c45&PID_627c ; SN9C201 +
HV7131R
%USBPCamDesc% = SN.USBPCam.XP,USB\VID_0c45&PID_627b ; SN9C201 +
OV7660
%USBPCamDesc% = SN.USBPCam.XP,USB\VID_0c45&PID_627a ; SN9C201 +
S5K53BEB
%USBPCamDesc% = SN.USBPCam.XP,USB\VID_0c45&PID_624b
; SN9C201 + CX1332
%USBPCamDesc% = SN.USBPCam.XP,USB\VID_0c45&PID_627f ; EEPROM

;
; Usb2.0 PC Camera with Audio Function
;
%USBPCamMicDesc% = SN.PCamMic.XP,USB\VID_0c45&PID_6280&MI_00 ; SN9C202
+ MI1300
%USBPCamMicDesc% = SN.PCamMic.XP,USB\VID_0c45&PID_6282&MI_00 ; SN9C202
+ MI1310
%USBPCamMicDesc% = SN.PCamMic.XP,USB\VID_0c45&PID_628e&MI_00 ; SN9C202
+ SOI968
%USBPCamMicDesc% = SN.PCamMic.XP,USB\VID_0c45&PID_628f&MI_00 ; SN9C202
+ OV9650
%USBPCamMicDesc% = SN.PCamMic.XP,USB\VID_0c45&PID_628a&MI_00 ; SN9C202
+ ICM107
%USBPCamMicDesc% = SN.PCamMic.XP,USB\VID_0c45&PID_62b0&MI_00 ; SN9C202
+ MI0360
%USBPCamMicDesc% = SN.PCamMic.XP,USB\VID_0c45&PID_62bc&MI_00 ; SN9C202
+ HV7131R
%USBPCamMicDesc% = SN.PCamMic.XP,USB\VID_0c45&PID_62bb&MI_00 ; SN9C202
+ Ov7660
%USBPCamMicDesc% = SN.PCamMic.XP,USB\VID_0c45&PID_62ba&MI_00 ; SN9C202
+ S5K53BEB
%USBPCamMicDesc% = SN.PCamMic.XP,USB\VID_0c45&PID_628b&MI_00 ; SN9C202
+ CX1332
%USBPCamMicDesc% = SN.PCamMic.XP,USB\VID_0c45&PID_6283&MI_00 ; SN9C202
+ S5K4AAFX

[SN.NTamd64]
;1.3 M
%USBPCamDesc% = SN.USBPCam.x64,USB\VID_0c45&PID_6240 ; SN9C201 +
MI1300
%USBPCamDesc% = SN.USBPCam.x64,USB\VID_0c45&PID_6242 ; SN9C201 +
MI1310
%USBPCamDesc% = SN.USBPCam.x64,USB\VID_0c45&PID_624f ; SN9C201 +
OV9650
%USBPCamDesc% = SN.USBPCam.x64,USB\VID_0c45&PID_624e ; SN9C201 +
SOI968
%USBPCamDesc% = SN.USBPCam.x64,USB\VID_0c45&PID_6243 ; SN9C201 +
S5K4AAFX
%USBPCamDesc% = SN.USBPCam.x64,USB\VID_0c45&PID_6253 ; SN9C201 +
OV9650
;VGA Sensor
%USBPCamDesc% = SN.USBPCam.x64,USB\VID_0c45&PID_6270 ; SN9C201 +
MI0360
%USBPCamDesc% = SN.USBPCam.x64,USB\VID_0c45&PID_627c ; SN9C201 +
HV7131R
%USBPCamDesc% = SN.USBPCam.x64,USB\VID_0c45&PID_627b ; SN9C201 +
OV7660
%USBPCamDesc% = SN.USBPCam.x64,USB\VID_0c45&PID_627a ; SN9C201 +
S5K53BEB
%USBPCamDesc% = SN.USBPCam.x64,USB\VID_0c45&PID_624b ; SN9C201 +
CX1332
;%USBPCamDesc% = SN.USBPCam.x64,USB\VID_0c45&PID_627f ; EEPROM

;
; Usb2.0 PC Camera with Audio Function
;
%USBPCamMicDesc% = SN.PCamMic.x64,USB\VID_0c45&PID_6280&MI_00 ;
SN9C202 + MI1300
%USBPCamMicDesc% = SN.PCamMic.x64,USB\VID_0c45&PID_6282&MI_00 ;
SN9C202 + MI1310
%USBPCamMicDesc% = SN.PCamMic.x64,USB\VID_0c45&PID_628e&MI_00 ;
SN9C202 + SOI968
%USBPCamMicDesc% = SN.PCamMic.x64,USB\VID_0c45&PID_628f&MI_00 ;
SN9C202 + OV9650
%USBPCamMicDesc% = SN.PCamMic.x64,USB\VID_0c45&PID_628a&MI_00 ;
SN9C202 + ICM107
%USBPCamMicDesc% = SN.PCamMic.x64,USB\VID_0c45&PID_62b0&MI_00 ;
SN9C202 + MI0360
%USBPCamMicDesc% = SN.PCamMic.x64,USB\VID_0c45&PID_62bc&MI_00 ;
SN9C202 + HV7131R
%USBPCamMicDesc% = SN.PCamMic.x64,USB\VID_0c45&PID_62bb&MI_00 ;
SN9C202 + Ov7660
%USBPCamMicDesc% = SN.PCamMic.x64,USB\VID_0c45&PID_62ba&MI_00 ;
SN9C202 + S5K53BEB
%USBPCamMicDesc% = SN.PCamMic.x64,USB\VID_0c45&PID_628b&MI_00 ;
SN9C202 + CX1332
%USBPCamMicDesc% = SN.PCamMic.x64,USB\VID_0c45&PID_6283&MI_00 ;
SN9C202 + S5K4AAFX


Cyro

[JoJo jojo]

---------- Forwarded message ----------
From: jabega <jbeta...@gmail.com>
Date: Jan 11, 2008 1:11 AM
Subject: Re: Lets get to it...
To: JoJo jojo <onetw...@gmail.com>

Hi :
I have a microdia webcam
0c45:6260 SN9C201 OV7670
I have instaled the sn9cxxx_2.09-gutsy-1ubuntu1_i386 pack but no
video dev is found.
I`ll thanks you a trick for solving the problem.
Excuse me about my Enghish.

[willflad]

USB Vendor Code: 0c45:60fe
Bridge & Sensor: SN9C105 + OV7630
Brand/ Model: GE Easycam Twin

[Ravan]

0c45:613c
SN9C120 + HV7131R (.inf online see: http://driveragent.com/archive/9604/2-0-16)
X-Gear CX-481U Easy Glow

NOTE: Got the thing running (sort of... just really dark image) with
Wengophone and the gspca driver on Ubuntu Gutsy AMD64. Read more on
http://ubuntuforums.org/showthread.php?p=3941436#post3941436

--ravan

[gwater]

good evening everybody,
just purchased a cheap funny webcam and guess what? ...

So, it's a
SN9C201 chip
SOI 968 sensor
in a Medion MD85572 USB-webcam
code: 0c45:624e

this is what i found about the sensor:
http://www.soinc.com.tw/pd_soi968.htm

I'm running Fedora 8 on a x86_64 machine and don't have any
programming experience. Nevertheless I'm willing to contribute.
In the spca50x devel-list ( http://lists-archives.org/spca50x-devs/maillist.html
) I read one of them is already trying to figure something out - but
there was no known state of development. Of course i cant find the
mail anymore.

GWater

[Gray Water]

hey,
here's another page for the sensor. seems to have the same content but im not sure:
http://www.comedia.com.cn/SOI968.htm

Anyway I noticed that most of us either use a sn9c1xx chip (which should actually already work) or a sn9c201. Collecting data for one single chip is easier than for a whole collection of them - so what data do we currently look for in the usb-snoops?

GWater

[JoJo jojo]

Hi GWater

take a look in the pages section..
for parsing the log from sniffUSB look here
https://groups.google.com/group/microdia/web/usb-sniffing-on-windows

Get an understanding of USB protocol, get a log from sniffUSB, parse
it like mentioned,
analyze the parsed log, upload the parsed file and comment on what you
did to generate that log,
and speculate on what the commands are being sent over, we try to
decipher that the commands mean.

-JoJo

[gwater]

ok thanks,
ill do that.
btw anyone ever tried to run the old fc4 driver in a virtual machine
to see if it works?

GWater

[A+]

0c45:6270
SN9C201
????????

Just posting this for now but will try to research the image sensor
info later (may I really have to take the device apart?). I assume
the bridge is SN9C201 - Vista wanted to download an update for it...

[JoJo jojo]

Hi James,

Non destructive way is to read the windows drivers *.inf file as detailed here
https://groups.google.com/group/microdia/web/reverse-engineering-windows-drivers

should that fail, you may need to carefully remove the cam shell &
note the IC markings

-JoJo

[zenum]

I tried with the fc6 version under a vm, but I couldn't get it to
install as it kept complaining about the kernel. Though it could just
be that i'm not used to working with fc... i'm a debian/ubuntu person
myself....

I have a 0c45:6270 Microdia webcam... with one of the older version of
the linux-projects drivers which didn't support my webcam said that my
image sensor was a MT9V111, now i have the current driver which
allegedly supports my camera and it says its an X sensor... ofcourse
the camera still doesn't work...

The sonix driver is GPL'd... doesn't that mean that we should be able
to get the source code for it? I emailed them asking for it... but
nothing so far :p

[JoJo jojo]

Hi Zenum

Others are reporting MI0360\MT9V111 sensor with your details,
from the windows *.inf files. Is that correct?

under VMware you will only get USB 1.1 and never USB 2.0

Did you update the FC6 after installing it in VM?

Forget about Luca's driver, before he givesus any decent drivers,
i'm afraid sonix will release better ones ;-)
(hmmm, You have the driver from Luca, would you like to share it?)

Yes, it said the .ko was GPL2, I guess thats why Sonix isn't distributing it :-(
(they have'nt figures out, how to cleanly seperate GPL from
proprietary drivers in kernel
like ATI, NVIDIA have)

BTW I noticed that you uploaded the snxcam.ko 1 day after I did the
same(double posting?)

-JoJo

[Gray Water]

hey A+,
this is what I found in my *.inf about your webcam:
SN9C201 + MI0360\MT9V111
look if u can get some detailed info on those sensors.

GWater

2008/1/20, A+ < james...@hotmail.com>:

[Gray Water]

Well,
after spending today on reading the pages section those are my questions/thoughts:

there is a module named sn9cxxx in the gspca source [ Link] which currently only supports some sn9c1xx webcams as we all know. Since it's being published under GPL I assume they wouldn't be angry if we sent them some lines of code to add to it. I don't think a new driver from scratch is really necessary.

While reading the code (with my 1/2 year of java-training) I found out the driver sends a stream of single bytes to the camera to control it. The single bytes-stream depends on the sensor.
Is this correct?

Is it possible to delete all the unnecessary modules(files as well as entries in code in core-source) and make a testing-source consisting of gspca_core.c gspca.h and sn9cxxx.h ?

GWater

[gwater]

BTW the fc6 *.ko needs a 2.6.18-kernel but I think it isn't worth the
effort of vm.

[JoJo jojo]

Hi GrayWater

Looks like you are upto it ;-)

How comfortable are you with the domain?
namely USBSpecs-linuxUSB-git-c-gspca-kernelDrivers-sniffUSB-perl-etc

Yes, gspca is a sound choice, infact when sonix released snxcam.ko for FC6,
they did it with gspca & V4L1

Also You may like to take a look at the code/kernel driver for bridge SN9C102,
done by Luca Risola?

Looks like we need a GIT host? what say You?
(For now you may zip & send the whole directory to me as updates.)

How much time per week can the two of us devote on this?
we may do it offline from the group and only send updates & update docs/files,
but taking care to document the process for others to join/jump in

-JoJo

[gwater]

Im up to it - thats right. I want to use this thing.

My (non-)abilities
I read the pages so I think Im at the edge of understanding usb.
(those sniffs don't seem to be that complicated though its not yet
totally clear to me what they are used for.)
I read most of the spca50x-devel-list-posts refering to sn9cxxx.
I had a half year training in java (just enough to make a computer
print "Hello World" and 5^10). so I think Im able read basic C.
a bit of self-taught python and bash
Im especially not familiar with Object-programming.
Im using linux since fc6 or dapper-ubuntu.
apart from "how to make grub boot a kernel after the fu**-idiot erased
the /boot-partition" the kernel is a mystery to me.
Not the best cv but I think ill get into it quite fast.

Well as long as there are only 2-5 people developing a driver for one
small chip GIT isn't necessary i think.

I could devote a few hours a week (mostly weekendish).

Luca's source looks interesting - it has totally different structure
than gspca. I would think its better we make our driver like gspca -
makes later integration easier.

Lets just open a new discussion and leave this alone for "what chip do
you use". IMO this would be enough documentation. If the driver starts
running we may write some more.

GWater

[JoJo jojo]

Hi GrayWater

Well my standards are pretty low ;-)

git is distributed, i.e everyone has local access to it.
The reason for using it is mainly to attract knowledgeable people who work,
in the kernel regularly, plus its what opensource is movingto, and the 2 of us
are not in the same room..yada yada yada

The reason luca's code has totally different structure than gspca is because,
it "professionally" done. It take good code to get into the kernel.
(not to diss. gspca though !)

-JoJo

[zenum]

Hi JoJo,
Not sure about the windows.inf files as I seem to have misplaced my
driver cd, the ones that if I recall correctly work are the sn9c201
drivers from the sonix site.
I've been trying to use VirtualBox which now supports USB2.0 and
VMWare Player (The latest one supports USB2.0) but neither worked
windows or fedora.
The driver I have from Lucas is just the trial one for Gutsy Gibbon, I
could share it but you can just download it from the site for free.
I don't think I double posted the snxcam.ko, my one was compiled for
fc6 and the one before was for fc4... (unless i'm going blind :s)

-Zenum

On Jan 20, 9:53 pm, "JoJo jojo" <onetwoj...@gmail.com> wrote:
> Hi Zenum
>
> Others are reporting MI0360\MT9V111 sensor with your details,
> from the windows *.inf files. Is that correct?
>
> under VMware you will only get USB 1.1 and never USB 2.0
>
> Did you update the FC6 after installing it in VM?
>
> Forget about Luca's driver, before he givesus any decent drivers,
> i'm afraid sonix will release better ones ;-)
> (hmmm, You have the driver from Luca, would you like to share it?)
>
> Yes, it said the .ko was GPL2, I guess thats why Sonix isn't distributing it :-(
> (they have'nt figures out, how to cleanly seperate GPL from
> proprietary drivers in kernel
> like ATI, NVIDIA have)
>
> BTW I noticed that you uploaded the snxcam.ko 1 day after I did the
> same(double posting?)
>
> -JoJo
>

[JoJo jojo]

hmmm,
perhaps you could use a friends' windows PC?

plugin your USB webcam, download drivers for windows from teh interwebs,
install & take a look at the inf files?

just a thought(the suspense is killin' us!!!! ;-)

-JoJo

[PaStIcHiO]

My cam is:

Bus 002 Device 002: ID 0c45:613b Microdia

Inside it should contain the sensor OV7660
and the bridge SN9C120.

Regards,
Andrea

[Gray Water]

Hello Pastichio,
gspca documentation tells me gspca should support your webcam.
Did you try
#modprobe gspca
?

GWater

2008/1/21, PaStIcHiO < andrea...@gmail.com>:

[JoJo jojo]

Hi Andrea,

a similar webcam
0c45:613c with bridge SN9C120 & sensor HV7131R,
is reportedly working with gspca, but giving dark image(probably
brightness control not working)
(you can searh teh interwebs for "how to install gspca on xxyy")

while i dont recommend it,
http://www.linux-projects.org/modules/mydownloads/viewcat.php?op=&cid=7
there is another driver for your bridge, don't know if it supports your sensor
(be warned its only for ubuntu 7.04(fiesty), 32-bit, binary only driver)
If you decide to use any driver from Linux-projects please don't complain.

would you like to add support for your webcam from scratch? We can
help you get started.
if so you are welcome here ;-) else there isn't much we can do for you here.

-JoJo

[PaStIcHiO]

On 21 Gen, 21:17, "Gray Water" <grewa...@googlemail.com> wrote:
> Hello Pastichio,
> gspca documentation tells me gspca should support your webcam.
> Did you try
> #modprobe gspca
> ?
>
> GWater
>

> 2008/1/21, PaStIcHiO <andreacim...@gmail.com>:

>
>
>
> > My cam is:
>
> > Bus 002 Device 002: ID 0c45:613b Microdia
>
> > Inside it should contain the sensor OV7660
> > and the bridge SN9C120.
>
> > Regards,
> > Andrea

I will explain my situtation:
I have bought 3 of theese webcams, very cheap actually.
On Windows platoforms they work preety good.
On Linux (don't ask me why) one works nicely with gpspca, instead
the other 2 ones (same id) the image at the first moments it's ok and
then after a second
the quality decreased and everything becomes dark. This with every
program (i tried Kopete and Skype).
If i can help you, it's a pleasure. Just i need some pointers.

Regards,
Andrea

[PaStIcHiO]

On 22 Gen, 06:12, "JoJo jojo" <onetwoj...@gmail.com> wrote:
> Hi Andrea,
>
> a similar webcam
> 0c45:613c with bridge SN9C120 & sensor HV7131R,
> is reportedly working with gspca, but giving dark image(probably
> brightness control not working)
> (you can searh teh interwebs for "how to install gspca on xxyy")
>

> while i dont recommend it,http://www.linux-projects.org/modules/mydownloads/viewcat.php?op=&cid=7

> there is another driver for your bridge, don't know if it supports your sensor
> (be warned its only for ubuntu 7.04(fiesty), 32-bit, binary only driver)
> If you decide to use any driver from Linux-projects please don't complain.
>
> would you like to add support for your webcam from scratch? We can
> help you get started.
> if so you are welcome here ;-) else there isn't much we can do for you here.
>
>

As i said in the post written 5 mins ago, the support on GSPCA it's
OK, but not
perfect because after some seconds everything becomes dark, i don't
know why.
I can't use the linux-projects drivers because i use Gentoo, a source
based distribution.
If i can help, it's a pleasure :-)

Ciao,
Andrea

[Gray Water]

are you trying to use all three of them at once or at different (physical) machines?
If second is correct - what differences are there between the PCs?

GWater

[PaStIcHiO]

No, i tried to use them one at time, same USB port.
Now i have only one of them because the other two i gave as present.
I have one the suffers of the problem of darkness. If you want i can
send you a video,
but i don't know a program that can record videos.

Andrea

[Gray Water]

Hi everybody,
My gcc is looking for module.h, slab.h, uaccess.h and some more - do you know which headers I'm looking for?

hint: its not the kernel-headers.

Thanks, GWater

[Gray Water]

BTW:
I need them for the source code at the bottom of this page - though you maybe don't understand German the code is good for testing your specific usb-device.

GWater

2008/1/23, Gray Water <grew...@googlemail.com>:

[Gray Water]

Ok, reinstalling the kernel-devel package solved the problem.
Anyway I tsill didn't succeed in compiling this code. If anyone does- please tell me how.
Good evening, GWater

[vitorshigutso]

<usb vendor code> 0c45:612e Microdia
<bridge & sensor name> SN9C110 + OV7630
<webcam brand & model name> Clone 11089 (from Brazil)

Windows drivers download link:
http://www.clone.com.br/downloads/drivers/11089.zip

thanks

On 8 jan, 12:50, "JoJo jojo" <onetwoj...@gmail.com> wrote:
> HI
>
> what kind of microdia are you running?
>
> Please reply to this with the following info
> <usb vendor code> <bridge & sensor name> <webcam brand & model name>.
> example:
> 0c45:627b, with SN9C201 bridge and OV7660 image sensor, found in Thinkpad Z61t
>
> thats it no more.
> (if you know more details about it, I have created pages, see them for
> examples and add your webcam info in that manner)
>
> -JoJo

[Bichon]

<usb vendor code> 0c45:6242 Microdia
<bridge & sensor name> SN9C210 + MI1310 (according with the inf)
<webcam brand & model name> Sangha cB130 (windows driver :
http://www.uniglory.net/zaspx/download.aspx)

I've got time to work on it or at least i will take the time cause i
want my damn cam to work.

Where should i begin ?

Thanks
++ Alex

[Gray Water]

welcome bichon,
first thing to do would be reading the pages section. If you already did usb-driver engineering u may skip that and look at the things in the files section.
We got documentation on two other webcam-drivers written the same way and some utilities for reverse engineering the windows-drivers.
Currently we are just starting to work on it. This means I'm learning C and trying to understand how drivers and especially the libUSB are working and jojo is collecting data and documentation.

Glad to hear you're just as keen on getting things running as I am.
The mail which are not referring to your chip and sensor but to development simply get the [-dev] mark.

GWater

[JoJo jojo]

Hi Alex

could you double check the sensor given in the windows *.inf file
for 0c45:6242 is SN9C201 or SN9C210 ?,
(one other member has reported the sensor in 0c45:6242 as SN9C201,
while you reported SN9C210)

we can use all the help we can get, start reading the threads already
on this group then pages section.

-JoJo

[Alexandre SPAETH]

Oh, sorry, you're right, it's SN9C201.
++ Alex

[vitorshigutso]

no way of making my webcam works?
I can try to write the code myself, but I need some directions how to
start it...
that USB Sniffer is a start?
I know how to program, but I don't know what do program...

<usb vendor code> 0c45:612e Microdia
<bridge & sensor name> SN9C110 + OV7630

[JoJo jojo]

Hi vitorshigutso

please take a look at the following files

http://microdia.googlegroups.com/web/[Dev]call_graphs_gspcav1-20071224.zip
http://microdia.googlegroups.com/web/[Dev]call_graphs_stk11xx-1.2.3.zip

this will give you a feel of how the driver control flows...its not
much but its something,
the driver has to read the URBs and decode the video stream for videodev,
the driver has to write the URBs to send commands to the webcam.

-JoJo

[Gray Water]

hey vitoshigutso,
please tage a look at the pages-section. It ahs been rearranged and should nswer most of your questions.
If not just ask again.

GWater

[Gray Water]

hey jojo
could you please move the new device page to webcams and add a page explaining general standarts like GPLv2 licensing and stuff. Just two sentences or something.

Thanks, GWater

2008/1/28, Gray Water <grew...@googlemail.com>:

[zenum]

> Others are reporting MI0360\MT9V111 sensor with your details,
> from the windows *.inf files. Is that correct?

Yes this is correct :) It can be added to the Microdia_support_31-
Jan-2008.png diagram

[DARKGuy]

Hi guys!

I have (sadly) a "Microdia U-CAM PC Camera NE878" according to "lsusb"
running ArchLinux 32-bit. It's a 0c45:6270.

Here's a picture I took of the camera:

http://img181.imageshack.us/img181/9449/dsc00088rz4.jpg

As it can be seen I have the CD with drivers (the camera works in XP
on my laptop flawlessly) and I'd be glad to put it up for this
project's sake, as I really need my webcam to work, but I dunno if
that's legal? I don't want to be prosecuted or anything, but I'd love
to help on the project, so some kind of assistance would be great so I
can help you guys :).

Hope this gets along well!

- DARKGuy

[Gray Water]

welcome darkguy,
there's absolutely no need to post  the whole win-driver and you won't be put into prison for taking part in this project. ;-).

Please take a look at the PAGES. I think they will answer most of your questions. If questions remain aimply ask on the list and we'll try to answer them.

GWater

[Jochen Kemnade]

hello,

I own a 0c45:624f model, which apparently is a SN9C201+OV9650. I have
it running on windows but had no success on linux (64 bit ubuntu gutsy/
hardy).

regards,
jochen

[Tiago Madeira]

My cam is a 0c45:6260, embedded Acer Orbicam (on Acer Aspire
5050-3205). It works on Windows with Suyin driver and it's a Sonix
USB2.0 sn9c201+Ov7670. I tried gspcav, linux-uvc, linux-projects and
figured out there's no way to run it under Linux... yet! :D

Tiago Madeira

[Eduardo Javier Paniagua Laconich]

Hey, witchcraft! I was about to report my orbicam... same one:
0c45:6260, on an Acer Aspire 5050-3759. sn9c201+OV7670, and no, no
free drivers yet.

I have Vista (aaagh) installed, and am trying to 'sniffusbize' my
orbicam. I will begin reading the libusb documentation tonight (ok,
maybe not tonight... 14-feb! but tomorrow) and get to work on this.

I have waited for so long... patience has run out. I am proficient in
C, and have done some microcontroller programming so maybe I can help.

If you have some code or comments it will be very much appreciated...
post them here.

It is the last non-functioning piece of hardware on my Aspire (well...
there is this ugly ENE Card Reader that can't read xD and Sony
Memsticks, but those are closed, proprietary memcard formats, so to
hell with them)

May the source (and specs) be with us!

[schnebeck]

Ok, I had to open my webcam to know that I have to follow this group
as I have a different vendor ID :-)

ID 145f:013d
No Vendor String shown
Its a Trust WB-3600R (Item number 153088)
Windows driver inf file (snp2std.inf):

;VGA Sensor
[...]
%USBPCamDesc% = SN.USBPCam,USB\VID_145F&PID_013D ;
SN9C201 + OV7660

Adapting the IDs to USB_UDIA_627B_PRODUCT_ID and compiling the git
repository works. The module loads, plug-in and plug-out is sys-logged
from the driver. But no data stream so far.

HTH

Thorsten

P.S. does anyone have a dowloadable and usable vmware player image to
use usbmon?

[JoJo jojo]

Hi Thorsten

If the *.ini file told you which bridge&sensor,
why did you feel the need to open the webcam ;-)
(A lot of our group members are scared to do that,
could you describe how you did it, assuming the webcam still works)

we are trying to implement the "handshake" with the webcams
from the sniffUSB logs, would you like to help us?

I believe Ubuntu v7.10 or even v8.04 will do fine with usbmon, debugfs etc.
to create vmware images *.vmx files you may use http://www.easyvmx.com/

-JoJo

[Dave Neuer]

On Sun, Mar 9, 2008 at 10:16 PM, JoJo jojo <onetw...@gmail.com> wrote:
>
> Hi Thorsten
>
> If the *.ini file told you which bridge&sensor,
> why did you feel the need to open the webcam ;-)
> (A lot of our group members are scared to do that,
> could you describe how you did it, assuming the webcam still works)

Even better, do you happen to have any pictures of the board? In
particular, the other components (e.g., external EEPROM chips, etc)
besides the Sonix chip?

Dave

[JoJo jojo]

well these are the wrong side of the board !
http://rsuinux.free.fr/luxya/img-2.jpg
http://rsuinux.free.fr/luxya/img-3.jpg

-JoJo

[Thorsten Schnebeck]

Am Montag, 10. März 2008 03:16:26 schrieb JoJo jojo:
> Hi Thorsten
Hi JoJo,

>
> If the *.ini file told you which bridge&sensor,
> why did you feel the need to open the webcam ;-)

Erm, I'm a Linux-only user, so windows driver cds is something for /dev/null
for me. :-)

So, my way was like this:

Searching for Trust WB-3600R & Linux, but this leads to nothing but questions
Searching for 145f:013d, leads to nothing but more questions.

As Linux and drivers is more about chips and not brands I thought its a good
idea to open the two skews and search for something new I could put into
Google ;-)

So I found the 9C201 chip and this newsgroup. Here I read this thread and
found the mail from cyro.

Now I got the info that the combination of ccd and custom chip is important
and that I can try to check the windows driver inf file for this.

Next step was setting up wine. As I use gentoo this definitely cost much more
time than oping the device ;-) Extracting the inf-file from the setup.exe was
hard. Without the filename from cyro maybe I had never found this one, as it
was not part of the temp folder created by the setup installer.

So, this was my way and maybe its interesting for others how to collect
information.

> (A lot of our group members are scared to do that,
> could you describe how you did it, assuming the webcam still works)

Ok, but for this cam its trivial. I try to setup an info page on my blog
later.

> we are trying to implement the "handshake" with the webcams
> from the sniffUSB logs, would you like to help us?

In 2 weeks I start a 3-week-holiday and will have some spare time :-)

> I believe Ubuntu v7.10 or even v8.04 will do fine with usbmon, debugfs etc.
> to create vmware images *.vmx files you may use http://www.easyvmx.com/

My devel system is gentoo but I have kubuntu 7.10 on my notebook. But building
kernels is no problem - Linux user since 1996 ;-)
My problem is, I have no windows and it would be nice if someone can point me
to a small ready to work vmware testing image, where I can install the
driver. You can use private mail. I still have some bundled XP license stuff
from my notebook but no valid installation medium - only repair CDs for a
partition that is gone a long time ago :-)

Oh, during my research I found this post:
http://lists.zerezo.com/video4linux/msg20894.html

Maybe this already helps.

Bye

Thorsten

[JoJo jojo]

Hi Thorsten

Have a look here for information
https://groups.google.com/group/microdia/web

We don't host any MS windows vmware images, sorry.
otherwise you can use the windows driver on a "friends" pc ?

if you don't have access to windows, won't worry
try using the sniffUSB logs already uploaded by others here
http://files.zenum.net/microdia/sniffusb_logs/0c45/

we look forward to your how-to & pix of opening the webcams,
you may even post the same on the group website under pages section.

-JoJo

[Dave Neuer]

On Mon, Mar 10, 2008 at 1:05 AM, JoJo jojo <onetw...@gmail.com> wrote:
>
> well these are the wrong side of the board !
> http://rsuinux.free.fr/luxya/img-2.jpg
> http://rsuinux.free.fr/luxya/img-3.jpg

yeah, I saw those, which is why I asked!

Dave

[Thorsten Schnebeck]

Am Monday 10 March 2008 um 10:01:49 schrieb JoJo jojo:
> Hi Thorsten
Hi
>

> Have a look here for information
> https://groups.google.com/group/microdia/web
>
> We don't host any MS windows vmware images, sorry.
> otherwise you can use the windows driver on a "friends" pc ?

Yes, this is possible. Are there some problems with
SniffUSB?
https://groups.google.com/group/microdia/browse_thread/thread/c28387701340b7f4/b9b32c8185bbb3b1#b9b32c8185bbb3b1

If not I will go the SniffUSB way.

>
> if you don't have access to windows, won't worry
> try using the sniffUSB logs already uploaded by others here
> http://files.zenum.net/microdia/sniffusb_logs/0c45/
>
> we look forward to your how-to & pix of opening the webcams,
> you may even post the same on the group website under pages section.

Ok, I have to test how this works

Bye

Thorsten

[Thorsten Schnebeck]

Yes
The eeprom is labled S24CS02
http://pdf1.alldatasheet.com/datasheet-pdf/view/222074/SII/S-24CS02A/datasheet.pdf
Crystal is 12MHz
Sonix is SN9C201AFG
Photos are ready but I have no time to publish

Bye

Thorsten

[Dave Neuer]

On Mon, Mar 10, 2008 at 6:27 PM, Thorsten Schnebeck
<thorsten....@gmx.net> wrote:
>
> Yes
> The eeprom is labled S24CS02

Fantastic.

> http://pdf1.alldatasheet.com/datasheet-pdf/view/222074/SII/S-24CS02A/datasheet.pdf

The datasheet is unfortunately in Japanese.

> Photos are ready but I have no time to publish

Cool. Will look forward to seeing them.

Now, if you get some USB sniff logs we can see if your writes to 10c0
are different from, say, the 624f camera's.

Dave

[Thorsten Schnebeck]

Hi,

Am Dienstag 11 März 2008 schrieb Dave Neuer:
> On Mon, Mar 10, 2008 at 6:27 PM, Thorsten Schnebeck
>
> <thorsten....@gmx.net> wrote:
> > Yes
> > The eeprom is labled S24CS02
>
> Fantastic.
>
> >
> > http://pdf1.alldatasheet.com/datasheet-pdf/view/222074/SII/S-24CS02A/data
> >sheet.pdf
>
> The datasheet is unfortunately in Japanese.

Ups, what about this URI
http://www.alldatasheet.com/datasheet-pdf/pdf/222074/SII/S-24CS02A.html

> > Photos are ready but I have no time to publish
>
> Cool. Will look forward to seeing them.

Hires photos are now part of Microdias data area.

Bye

Thorsten

[Dave Neuer]

On Tue, Mar 11, 2008 at 2:48 AM, Thorsten Schnebeck
<thorsten....@gmx.net> wrote:
>
> Ups, what about this URI
> http://www.alldatasheet.com/datasheet-pdf/pdf/222074/SII/S-24CS02A.html

Excellent, I can read that!

Dave

[guybrush]

Hi to every one,
I have found
Bus 003 Device 002: ID 0c45:6260 Microdia:Acer aspire 5050 (5051)
I have tested the driver we are talking about on this group and It
found my webcam. unfortunately I'm only able to see a black screen.
The power led didn't light.

I'm wondering if I did something wrong
or may be the driver isn't ready to my webcam yet.

although congratulations to all the developers team. you're doing a
great job.
I read something bout send you some logs a bout how the webcam works
on windows.
If it's still useful please tell me and I'll try to get it

unfortunately I'm not a developer, so I'm not able to write any code,
but I can test whatever the group want.

Any way I follow this group eagerly.

Guybrush.

On Mar 11, 1:04 pm, "Dave Neuer" <mr.fred.smoot...@pobox.com> wrote:
> On Tue, Mar 11, 2008 at 2:48 AM, Thorsten Schnebeck
>

[Tiago Madeira]

Hey Guybrush!
I have the same laptop and the same webcam (0c45:6260) and actually
I've written init sequence and I'm writing start sequence (so..
unfortunately the driver is not ready to our webcam... yet). BUT your
log will be very useful, because I'm trying hard but I can't get the
start sequence working at the moment (oh, the led is turning on here,
with a code that is not in the repository yet) and it would be great
to have other logs to compare and fix the code. Here's the link about
usb sniffing: http://groups.google.com/group/microdia/web/usb-sniffing-on-windows

Thanks and let's do it!
Tiago

[guybr...@gmail.com]

Hi,
Ok, I hope during today I'll be able to plug into my laptop the hardrive
with winXP and get the logs.
I will upload it asap.

[guybr...@gmail.com]

Hey guys,
here they are, the logs of my camera.
I don't know how to upload to the server so please anyone who knows
pleas uploat them.

http://monkeyisland.no-ip.info/0c45_6260_23_mar_2008_init_sart_stop_sequences.zip

I hope they are useful.

Regards.

Tiago Madeira escribió:

[Tiago Madeira]

Thanks very much! I'm downloading them and I'll give a feedback asap

[JoJo jojo]

Hi GuyBrush2k4

We have a common website for sniffUSB logs,
I have upped your log file there as well
http://files.zenum.net/microdia/sniffusb_logs/0c45/6260/

-JoJo

[jmo]

Just my 2 Euro-cents:

I have a Trust WB-5400, part no 15007 (Trust's web site lists two
different part numbers for the same product - I can only report for
the (newer) p/n 15007)

USB id is 0c45:624e

according to the Windows driver .inf the bridge is SN9C201, sensor is
SOI968. So this is just like any other 0c45:624e (Medion cam).
Interestingly the installer .inf file refers to "Sonic" as the company
and "Trust WB-5400" as product :-)

Regards,
Jens

[JoJo jojo]

Hi Jens

I have noted down your info here (as usual)
https://spreadsheets.google.com/ccc?key=pyuKEu_RW054Jep2-2In1Fg&hl=en

-JoJo

[JoJo jojo]

On Tue, Apr 22, 2008 at 4:20 PM, al1en <A.Kir...@gmail.com> wrote:
> Hi
>
> I have this tupe of Gembird 66U webcam:
> Bus 001 Device 004: ID 0c45:6270 Microdia U-CAM PC Camera NE878 -
> output from lsusb
>
> %USBPCamDesc% = SN.USBPCam,USB\VID_0c45&PID_6270 ; SN9C201 +
> MI0360\MT9V111 - from windows .ini files, sensor name and model
>
> So, any chance to make this cam working in Ubuntu 8.04 (hardy) 64bit
> on AMD Athlon 64 X2 Dualcore procesor? If so, pls guide me!
> 10x a lot.

Hi Kirovski

Please try the driver like this
https://groups.google.com/group/microdia/web/testing-microdia-driver-draft

-JoJo

[JoJo jojo]

FWD'ing info

-JoJo
---------- Forwarded message ----------
From: lunarknight <vincen...@gmail.com>
Date: Thu, May 1, 2008 at 4:29 AM
Subject: Re: Lets get to it...
To: JoJo jojo <onetw...@gmail.com>

0c45:6288, SN9C202 bridge and OV9655, found in rocketfish desktop/
notebook web camera.

Currently it doesn't work if I build and use this site's microdia
driver. I'll try capturing some logs.

[Shariukas]

Hi,

Microdia 0c45:6242, bridge SN9C201, found in X-point CR-314.

[Victor]

<usb vendor code> 0c45:627f
<bridge & sensor name> SN9C201
<webcam brand & model name> The integrated webcam on the notebook
"Lenovo 300 N 100"

On Apr 22, 2:03 pm, "JoJo jojo" <onetwoj...@gmail.com> wrote:

> Please try the driver like thishttps://groups.google.com/group/microdia/web/testing-microdia-driver-...
>
> -JoJo

[JoJo jojo]

---------- Forwarded message ----------
From: edbroni <edb...@gmail.com>
Date: Sat, May 31, 2008 at 1:05 AM
Subject: Re: Lets get to it...
To: JoJo jojo <onetw...@gmail.com>

Hi,

My webcam is a 0c45:624f, SN9C201 bridge.

I installed the driver downloaded from git and this is my review:
-the green and green shadows are the exclusive color that appear;
-a lot of tiny pink lines in the image too;
-the image appear invert.

I'm using Fedora 8 64 bits in a notebook.

On 8 jan, 10:50, "JoJo jojo" <onetwoj...@gmail.com> wrote:
> HI
>
> what kind of microdia are you running?
>
> Please reply to this with the following info
> <usb vendor code> <bridge & sensor name> <webcam brand & model name>.
> example:
> 0c45:627b, with SN9C201 bridge and OV7660 image sensor, found in Thinkpad Z61t
>
> thats it no more.
> (if you know more details about it, I have created pages, see them for
> examples and add your webcam info in that manner)
>
> -JoJo

[JB]

Found in Notebook Targa Traveller 1526 (http://www.service.targa.de/),
sorry, only german side found.

0c45:62c0
bridge: unknown, because manufactor don't offer a driver, windows
vista driver works "(Windows\system32\drivers\usbvideo.sys",
usbvideo.inf don't show any info.
image sensor: unknown, same problem
open the webcam to read out the chip is not possible, becaue it is
integradet in the monitor.
I posted a lsusb -v -d ... output in the Files section.

Any idea to get more informations , yes, except google ;-)

greetings

Jan

[JoJo jojo]

Hi Jan

Your webcam is already supported by the UVC driver,
go here http://linux-uvc.berlios.de/
.........Bye Jan

-JoJo

[JoJo jojo]

On Mon, Jun 2, 2008 at 12:03 PM, adam_richter <ad...@yggdrasil.com> wrote:
> vendorID = 0c45 : productID = 8008
>
> This is a camera included in the Estes radio controlled model airplane
> of an XB-39 AWACS. Pictures are in flight taken by remote control and
> stored internally for later download by USB.
>
> I expect to try to open it later to read the part numbers printed on
> the chips inside it, at which time I plan to post a follow up with
> that information.
>

Hi Adam

Can you provide us with More info ?
https://groups.google.com/group/microdia/web/howto-get-information-on-your-webcam

-JoJo

[JB]

> Your webcam is already supported by the UVC driver,
> go here http://linux-uvc.berlios.de/

oh, thanks.
Just I add a new page about it, now I edit it so that there exists a
driver. I'll test it.

Maybe you move the page in the right chapter and let it exists, to get
the information...

[Marsteegh]

Hi all,

first: I'm a bit confused about how these google groups work, so I
hope I post in the right topic/place.

I just wanted to share my experience with the latest git driver (date
20 jun 08).

It sortof works. When I run 'camorama -D --width=640 --height=480' or
'camorama -D -R --width=640 --height=480'
I do get an image, but It's way to bright most of the time (*), even
when I set camorama's brightness slider all the way to the left. The
brightness= module parameter doesn';t seem to have any effect. without
v/hflip the image is rotated 180 degrees.

(*) once every second or so I get one frame which looks ok (a 'dark
flash'), though it's hard to tell since it's passing quite fast. I
tried saving a stream with mencoder, but when saving I don't get these
'dark flashes' and just get the overly bright image.



Hardware:
an MSI M662 laptop with the webcam built into the screen. Internally
attached via usb.

inserting the module:
[ 6826.723786] microdia: Microdia USB2.0 Webcam - Product ID 624F.
[ 6826.723795] microdia: Release: 0100
[ 6826.723798] microdia: Number of interfaces : 1
[ 6826.725237] microdia: Microdia USB2.0 Camera is now controlling
video device /dev/video0
[ 6826.880920] Changing resolution to 640 by 480
[ 6826.924677] microdia: Read from EEPROM successful


cat /sys/class/video4linux/video0$ cat informations:
Asked resolution : 640x480
Driver resolution : 640x480
Webcam resolution : 640x480

RGB24 - RGB-8-8-8 - 24 bits

Brightness : 0x7F00
Contrast : 0x0
Whiteness : 0x3300
Exposure : 0x1
Sharpness : 0x1F
Horizontal flip : 0
Vertical flip : 0
Auto-exposure : 1
Auto-whitebalance : 1


lsusb -v:
Bus 005 Device 005: ID 0c45:624f Microdia
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0c45 Microdia
idProduct 0x624f
bcdDevice 1.00
iManufacturer 0
iProduct 1 USB20 Camera
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 279
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 10
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0080 1x 128 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 10
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 2
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0100 1x 256 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 10
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 3
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0180 1x 384 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 10
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 4
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 10
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 5
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x02a8 1x 680 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 10
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 6
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0320 1x 800 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 10
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 7
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0b84 2x 900 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 10
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 8
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x1400 3x 1024 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 10
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)


greetings
--
martijn

[John Lemon]

Hi! My cam is 0x0C45:0x613A, sn9c120 bridge, OV7648 sensor (according
to the .inf file), in a SERIOUX USB Toy Web Cam (330k)
lsusb result:
Bus 003 Device 003: ID 0c45:613a Microdia

dmesg result:
[13802.928000] usb 3-1: new full speed USB device using uhci_hcd and
address 3
[13803.088000] usb 3-1: configuration #1 chosen from 1 choice
[13803.092000] usb 3-1: SN9C120 PC Camera Controller detected (vid:pid
0x0C45:0x613A)
[13803.196000] usb 3-1: No supported image sensor detected for this
bridge

Why does it say no supported image sensor?

Doesn't work with gspca.
I've also downloaded the free sn9c102 driver from
http://www.linux-projects.org/modules/mydownloads/viewcat.php?cid=2,
and it compiled succesfully but I can't add the module with insmod, it
says
Error -1, Unrecognized symbol

> ...
>
> read more »

[GWater]

John Lemon schrieb:

> Hi! My cam is 0x0C45:0x613A, sn9c120 bridge, OV7648 sensor (according
> to the .inf file), in a SERIOUX USB Toy Web Cam (330k)
> lsusb result:
> Bus 003 Device 003: ID 0c45:613a Microdia
>
> dmesg result:
> [13802.928000] usb 3-1: new full speed USB device using uhci_hcd and
> address 3
> [13803.088000] usb 3-1: configuration #1 chosen from 1 choice
> [13803.092000] usb 3-1: SN9C120 PC Camera Controller detected (vid:pid
> 0x0C45:0x613A)
> [13803.196000] usb 3-1: No supported image sensor detected for this
> bridge
>
> Why does it say no supported image sensor?
>
> Doesn't work with gspca.
> I've also downloaded the free sn9c102 driver from
> http://www.linux-projects.org/modules/mydownloads/viewcat.php?cid=2,
> and it compiled succesfully but I can't add the module with insmod, it
> says
> Error -1, Unrecognized symbol
>

Ok there are several issues here:

1. I don't know which part of the kernel printed these messeges to dmesg
- the "usb" suggests it's the usb-subsystem but the content of the
messeges suggests it rather is a webcam kernel driver.

2. From our perspective both image sensor and bridge chip (sn9c120) are
not yet supported (by the microdia driver). Also, our current policy is
that sn9c1xx bridges won't be included into the current driver but into
a fork driver which will be created as soon as there are developers.
Therefore this is your once-in-a-lifetime chance to work on support for
your webcam. We will assist as much as we can.

3. Though the sn9c102 module won't help you much here is a solution for
your problem:

# insmod sn9c102.ko
/*insmod: error inserting 'sn9c102.ko': -1 Unknown symbol in module*/

See the output of #dmesg

the last few lines would be complaints about missing symbols, depending
upon whats missing

you may not have loaded the modules that module depends on,
So it failed with those error messages. You would need to modprobe for
that module's dependencies

Try

$sudo modprobe videodev

$sudo modprobe compat-ioctl32

then

$sudo insmod sn9c102.ko

Hope I could help,

GWater

[Comer352l]

John Lemon schrieb:
> ...

> I've also downloaded the free sn9c102 driver from
> http://www.linux-projects.org/modules/mydownloads/viewcat.php?cid=2,
> and it compiled succesfully but I can't add the module with insmod, it
> says
> Error -1, Unrecognized symbol
>

Hi John,

the sn9c1xx-driver from linux-projects.org should indeed support your
device.
Do you have the kernel symbols installed ?
Please tell us if the driver works for you.

Frank

[John Lemon]

@GWater
@Comer3521

Thank you both for your answers. Yep, i had to load videodev and
compat-ioctl32 before the sn9c102 driver. It did load this time:

[ 1892.620000] sn9c102: V4L2 driver for SN9C1xx PC Camera Controllers
v1:1.48
[ 1892.620000] usbcore: registered new interface driver sn9c102

After plugging in the camera, I got this:

[ 1955.604000] usb 3-2: new full speed USB device using uhci_hcd and
address 2
[ 1955.764000] usb 3-2: configuration #1 chosen from 1 choice
[ 1955.768000] usb 3-2: SN9C120 PC Camera Controller detected (vid:pid
0x0C45:0x613A)
[ 1955.880000] usb 3-2: OV7648 image sensor detected
[ 1956.196000] usb 3-2: Initialization succeeded
[ 1956.196000] usb 3-2: V4L2 device registered as /dev/video0
[ 1956.196000] BUG: unable to handle kernel paging request at virtual
address 05100070
[ 1956.196000] printing eip:
[ 1956.196000] c02f338b
[ 1956.196000] *pde = 00000000
[ 1956.196000] Oops: 0002 [#1]
[ 1956.196000] SMP
[ 1956.196000] Modules linked in: sn9c102 compat_ioctl32 videodev
v4l2_common v4l1_compat ipv6 af_packet binfmt_misc ppdev powernow_k8
cpufreq_stats cpufreq_powersave cpufreq_userspace cpufreq_conservative
cpufreq_ondemand freq_table container video ac dock sbs button battery
nls_iso8859_1 nls_cp437 vfat fat lp snd_via82xx gameport
snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm
snd_page_alloc snd_mpu401_uart snd_seq_dummy joydev snd_seq_oss
snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer
snd_seq_device parport_pc nvidia(P) parport usbhid hid snd pcspkr
psmouse serio_raw k8temp i2c_viapro i2c_core soundcore shpchp
pci_hotplug amd64_agp agpgart evdev ext3 jbd mbcache ide_cd cdrom
ide_disk via82cxxx ide_core floppy ehci_hcd via_rhine mii uhci_hcd
usbcore ata_generic ahci libata scsi_mod thermal processor fan fuse
apparmor commoncap
[ 1956.196000] CPU: 0
[ 1956.196000] EIP: 0060:[<c02f338b>] Tainted: P VLI
[ 1956.196000] EFLAGS: 00010246 (2.6.22-15-generic #1)
[ 1956.196000] EIP is at mutex_lock+0xb/0x20
[ 1956.196000] eax: 05100070 ebx: 05100070 ecx: 00000004 edx:
c19f2000
[ 1956.196000] esi: ecebb608 edi: ffffffef ebp: 00000000 esp:
c19f3cb4
[ 1956.196000] ds: 007b es: 007b fs: 00d8 gs: 0000 ss: 0068
[ 1956.196000] Process khubd (pid: 2063, ti=c19f2000 task=c19274c0
task.ti=c19f2000)
[ 1956.196000] Stack: f8cfa98c c01c3557 f8c273a9 ecebb648 00000004
d85f01a4 00000000 d60aa25c
[ 1956.196000] d60a8000 ecebb5d0 00000000 d60aa25c d60a8000
f8cdffbc f8cf5bc8 f88ffdf9
[ 1956.196000] d85fb910 00000000 0000613a f8ce5c54 f88f3dc7
d6ed6e00 00000000 00000000
[ 1956.196000] Call Trace:
[ 1956.196000] [<c01c3557>] sysfs_add_file+0x37/0x90
[ 1956.196000] [<f8c273a9>] video_register_device+0x139/0x280
[videodev]
[ 1956.196000] [<f8cdffbc>] sn9c102_usb_probe+0x11c/0x840 [sn9c102]
[ 1956.196000] [<f88f3dc7>] usb_match_one_id+0x27/0xb0 [usbcore]
[ 1956.196000] [<f88f4f66>] usb_probe_interface+0x96/0xe0 [usbcore]
[ 1956.196000] [<c026134e>] driver_probe_device+0x8e/0x190
[ 1956.196000] [<c02f1943>] klist_next+0x53/0xa0
[ 1956.196000] [<c0260604>] bus_for_each_drv+0x44/0x70
[ 1956.196000] [<c0261516>] device_attach+0x86/0x90
[ 1956.196000] [<c0261450>] __device_attach+0x0/0x10
[ 1956.196000] [<c026056d>] bus_attach_device+0x4d/0xa0
[ 1956.196000] [<c02609b9>] bus_add_device+0x129/0x160
[ 1956.196000] [<c025f23f>] device_add+0x49f/0x570
[ 1956.196000] [<f88f2f22>] usb_set_configuration+0x2a2/0x4f0
[usbcore]
[ 1956.196000] [<f88fae1d>] generic_probe+0x16d/0x250 [usbcore]
[ 1956.196000] [<f88f4c33>] usb_probe_device+0x33/0x40 [usbcore]
[ 1956.196000] [<c026134e>] driver_probe_device+0x8e/0x190
[ 1956.196000] [<c02f1943>] klist_next+0x53/0xa0
[ 1956.196000] [<c0260604>] bus_for_each_drv+0x44/0x70
[ 1956.196000] [<c0261516>] device_attach+0x86/0x90
[ 1956.196000] [<c0261450>] __device_attach+0x0/0x10
[ 1956.196000] [<c026056d>] bus_attach_device+0x4d/0xa0
[ 1956.196000] [<c02609b9>] bus_add_device+0x129/0x160
[ 1956.196000] [<c025f23f>] device_add+0x49f/0x570
[ 1956.196000] [<f88ee28d>] usb_new_device+0x8d/0x110 [usbcore]
[ 1956.196000] [<f88eef6e>] hub_thread+0x78e/0xc30 [usbcore]
[ 1956.196000] [<c02f229a>] schedule+0x2ca/0x890
[ 1956.196000] [<c013be00>] autoremove_wake_function+0x0/0x50
[ 1956.196000] [<f88ee7e0>] hub_thread+0x0/0xc30 [usbcore]
[ 1956.196000] [<c013bb42>] kthread+0x42/0x70
[ 1956.196000] [<c013bb00>] kthread+0x0/0x70
[ 1956.196000] [<c0105487>] kernel_thread_helper+0x7/0x10
[ 1956.196000] =======================
[ 1956.196000] Code: 53 89 c3 e8 48 f5 ff ff b8 ff ff ff ff 90 0f c1
03 83 e8 01 78 04 5b 31 c0 c3 89 d8 5b eb 21 90 53 89 c3 e8 28 f5 ff
ff 89 d8 90 <ff> 08 79 05 e8 0c 01 00 00 5b c3 8d 76 00 8d bc 27 00 00
00 00
[ 1956.196000] EIP: [<c02f338b>] mutex_lock+0xb/0x20 SS:ESP
0068:c19f3cb4

The last part, from the "BUG: unable to handle..." appears every time
I start a program that uses the driver. I tried Camorama, Ekiga,
XSane. They all remain in memory, and appear as uninterruptible in the
process viewer (not even kill won't remove them).

[balev]

Hi All,

I have to following camera:
"Bus 1 Device 4: ID 0c45:624f Microdia PC Camera (SN9C201)" in a
Lenovo 3000 N100 integrated.

Compiled the driver, loaded it into kernel (latest stable vanilla
2.6.25.8 on Slackware 12.1) and according to dmesg it registers it as
it has to.
Only camstream can make use of the driver and display video stream,
mplayer gives the following output with a blank window:

[QUOTE]
balev@lenovo:~$mplayer tv:// -tv driver=v4l2:width=320:height=240 -fps
15
MPlayer 1.0rc2-4.2.3 (C) 2000-2007 MPlayer Team
CPU: Intel(R) Core(TM)2 CPU T5500 @ 1.66GHz (Family: 6,
Model: 15, Stepping: 6)
CPUflags: MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 1
Compiled for x86 CPU with extensions: MMX MMX2 SSE SSE2

Playing tv://.
TV file format detected.
Selected driver: v4l2
name: Video 4 Linux 2 input
author: Martin Olschewski <olsch...@zpr.uni-koeln.de>
comment: first try, more to come ;-)
Selected device: Microdia USB Video Camera
Capabilites: video capture read/write streaming
supported norms: 0 = webcam;
inputs: 0 = Webcam;v4l2: ioctl get input failed: Invalid argument

Current input: 1
Current format: BGR24
v4l2: ioctl set format failed: Invalid argument
tv.c: norm_from_string(pal): Bogus norm parameter, setting default.
Selected input hasn't got a tuner!
v4l2: ioctl set mute failed: Invalid argument
v4l2: ioctl query control failed: Invalid argument
v4l2: ioctl query control failed: Invalid argument
==========================================================================
Opening video decoder: [raw] RAW Uncompressed Video
VDec: vo config request - 320 x 240 (preferred colorspace: BGR 24-bit)
Could not find matching colorspace - retrying with -vf scale...
Opening video filter: [scale]
VDec: using BGR 24-bit as output csp (no 0)
Movie-Aspect is undefined - no prescaling applied.
[swscaler @ 0x889c030]SwScaler: using unscaled bgr24 -> yuv420p
special converter
VO: [xv] 320x240 => 320x240 Planar YV12 [zoom]
Selected video codec: [rawbgr24] vfm: raw (RAW BGR24)
==========================================================================
Audio: no sound
FPS forced to be 15.000 (ftime: 0.067).
Starting playback...
New_Face failed. Maybe the font path is wrong.
Please supply the text font file (~/.mplayer/subfont.ttf).
subtitle font: load_sub_face failed.
X11 error: BadAlloc (insufficient resources for operation)
X11 error: BadAlloc (insufficient resources for operation)
X11 error: BadAlloc (insufficient resources for operation)
[/QUOTE]

Skype with a black screen when testing:
[QUOTE]
balev@lenovo:~$Skype V4L2: Failed to change capture framerate (15)
Starting the process...
Skype Xv: Xv ports available: 17
Skype XShm: XShm support enabled
Skype Xv: Using Xv port 82
[/QUOTE]

I have "framebuffer overflow" in dmesg after trying to use.
I tried to seek for "framebuffer" errors and for the "X11 error" when
suddenly started to think about that maybe it has something to do with
Compiz/Gl. I switched back to use Metacity and it made the change. I
have really good output in mplayer and skype also gives a reasonable
stream.
Do you have any idea what to tweak the have the driver work under
compiz?

Thank for the great efforts you are taking in order to provide
Microdia webcam owners a driver (not for only a "distro" with one
certain kernel and for money as others offers...)

So, keep up the good work :)
waiting for your kindly answers and sorry if it was already answered
somewhere,
nice day to everybody,

balev,
Hungary

[Comer352l]

Hi John,

seems to be an USB-related problem. Did you try on different machines ?
I don't know if Luca offers support for his driver, but there is a
(empty) forum on his page...

Frank

John Lemon schrieb:

[John Lemon]

Hi Frank, Luca's forum isn't exactly empty. You just have to show
older posts. Anyway, I found a thread with exactly my webcam and
exactly my error. The solution was to compile the driver without
advanced debugging support through /sysfs, and it worked for me. The
cam works as it should in this application here:
http://www.linux-projects.org/modules/mydownloads/visit.php?cid=5&lid=42
Now, what webcam programs are v4l2 compliant?
Cheers, John Lemon.

[balev]

[quote]I have "framebuffer overflow" in dmesg after trying to use.

I tried to seek for "framebuffer" errors and for the "X11 error" when
suddenly started to think about that maybe it has something to do with
Compiz/Gl. I switched back to use Metacity and it made the change. I
have really good output in mplayer and skype also gives a reasonable
stream.
Do you have any idea what to tweak the have the driver work under

compiz?[/quote]

Anyone has some experience on compiz problem?

Nice day to everybody,
balev

[JoJo jojo]

Fwd'ing the ML

-JoJo

---------- Forwarded message ----------
From: david <da...@edenroad.demon.co.uk>
Date: Thu, Jul 10, 2008 at 4:09 PM
Subject: Re: Lets get to it...
To: JoJo jojo <onetw...@gmail.com>

On Jan 8, 3:50 pm, "JoJo jojo" <onetwoj...@gmail.com> wrote:
> HI
>
> what kind of microdia are you running?
>
> Please reply to this with the following info
> <usb vendor code> <bridge & sensor name> <webcam brand & model name>.
> example:
> 0c45:627b, with SN9C201 bridge and OV7660 image sensor, found in Thinkpad Z61t

0c45:6242 with SN9C201 (or 202, I can't tell), in a Panther Gx4

The module works under Ubuntu 8.04, with a pretty good frame rate
although it's very dark and quiet, and generates buffer overflow
warnings at 640x480 resolution.

Works with Skype, Cheese and Camorama.

Excellent work.

[zigzagzen]

Hello,

New to Linux, old hand at computing. Running Ubuntu 8.04 32bit on a
HPCompaq Presario C500 series. Did not reverse engineer to get this
info as Linux happily gave it to me - so let me know if doing that
will help and if I may have errors.

My webcam is branded as MIKOMI and has (see end of dmesg and lsusb
below for source):

device ID 0c45:60fe. Microdia
Bridge SN9C105
Sensor OV7630

This is exactly the same as the GE Easycam Twin/Pro which is listed in
your Microdia spreadsheet with the comment "listed as supported in
sn9c1xx-driver". Is this a driver that is shipping with current Linux
versions or one of yours? ... I'm guessing it's in the distro's
because my camera wants to work lol

My Cam has a mic but that seems not to be recognised (I don't need it
to be). Plugging my webcam into the laptop it is immediately
recognised and Skype is offering me the choice to use SNC1xx PC
Camera /dev/video0/

However when I try to test or use the camera I am getting a plain
green image with a matrix like effect of wiggly lines at the top. I
have a feeling I am not far from getting it working, so the "supported
in" comment may be right.

Don't just want to get MY camera working - would like to add something
to efforts here but my skills with Linux are still rudimentary.

Below is the end of dmesg output and the lsusb from where I have drawn
the above information on bridge, sensor etc. Can I trust it or is
reverse engineering under windows going to help? Anyone got any bright
ideas for my next step?

Matthew

[14940.713558] usb 3-2: SN9C105 PC Camera Controller detected (vid:pid
0x0C45:0x60FE)
[14940.806664] usb 3-2: OV7630 image sensor detected
[14941.304212] usb 3-2: Initialization succeeded
[14941.304295] usb 3-2: V4L2 device registered as /dev/video0
[14941.304301] usb 3-2: Optional device control through 'sysfs'
interface disabled
me@mattop:~$ lsusb
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 002: ID 0c45:60fe Microdia

[zigzagzen]

A ps to my earlier messsage. The Microphone On my USB webcam IS
working on skype - both on Ubuntu i386 Hardy and on x64 Hardy (with
Skype forced into operation - don't remember where I found out how to
do that)

So clearly this device is supported and I am probably one or two steps
away from actually getting a properly decoded video stream. Those
steps ... those steps .. where are they?

zigzagzen

[Hans de Goede]

zigzagzen wrote:
> Hello,
>

Hi zigzagzen, please contact JF Moine:
http://moinejf.free.fr/

Who maintains the usb webcam driver framework gspca which has been merged for
2.6.27 and maintains the sonixj subdriver of gspca, which could support your
cam (but currently doesn't).

Jean Francois is always willing to spend time to get your cam to work, provided
you can test patches for him, provide windows usb snoops, etc.

> Don't just want to get MY camera working - would like to add something
> to efforts here but my skills with Linux are still rudimentary.
>

Good, glad to hear that for now contact JF Moine, tell him what cam you have
and that you want to help get it work and are willing to test any driver
versions he will throw at you :)

Regards,

Hans

[JoJo jojo]

Forwarding the ML

screenshot when 62bb is forced as 627b.

The key difference being 62bb is SN9C202
while 627b is SN9C201

-JoJo

---------- Forwarded message ----------
From: Virgilio Gómez Rubio <becario...@gmail.com>
Date: Thu, Aug 7, 2008 at 1:57 AM
Subject: Re: MOdel 62bb
To: JoJo jojo <onetw...@gmail.com>

Hi,

Thanks again

uname -a :
Linux fh-vrubio 2.6.24-19-generic #1 SMP Fri Jul 11 23:41:49 UTC 2008
i686 GNU/Linux

Screenshot attached.

I have got the version of the driver with

git clone http://repo.or.cz/r/microdia.git

Many thanks again,

Virgil

On Wed, Aug 6, 2008 at 8:24 PM, JoJo jojo <onetw...@gmail.com> wrote:
>
> Hi Virgilio
>
> privide me output of
> #unama -a
> screenshot of
> #mplayer tv:// -tv driver=v4l2:width=640:height=480:device=/dev/video0
> -fps 20 -vo x11
>
> I hope you are running the latest git version of the driver as well.
>
> -JoJo
>
> On Thu, Aug 7, 2008 at 12:30 AM, Virgilio Gómez Rubio
> <becario...@gmail.com> wrote:
> > Hi,
> >
> > This is the output from dmesg when the camera in plugged-in:
> >
> > [86527.335873] microdia: Microdia USB2.0 Webcam - Product ID 62BB.
> > [86527.335881] microdia: Release: 0100
> > [86527.335884] microdia: Number of interfaces : 3
> > [86527.354586] microdia: No ack from I2C slave 0x21 for write to address
> > 0x0a
> > [86527.359274] microdia: Microdia USB2.0 Camera is now controlling video
> > device /dev/video0
> > [86527.361261] ALSA
> > /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-generic/sound/alsa-driver/usb/usbaudio.c:1296:
> > 6:2:1: cannot get freq at ep 0x84
> > [86528.195441] ALSA
> > /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-generic/sound/alsa-driver/usb/usbaudio.c:1296:
> > 6:2:1: cannot get freq at ep 0x84
> >
> > And I have tried to get iamg ewith camstrema dn vlc but it does not work.
> > basically I get a black
> > square in camstream (no display window in vlc) and the programme freezes
> > when I close it. Furthermore,
> > the red light in the camera doesn't light on.
> >
> > The permissions of the device aer
> >
> > crw-rw----+ 1 root video 81, 0 2008-08-06 19:53 /dev/video0
> >
> > and I am in group video.
> >
> > Cheers,
> >
> > Virgilio
> >
> >
> > On Wed, Aug 6, 2008 at 6:18 PM, JoJo jojo <onetw...@gmail.com> wrote:
> >>
> >> On Wed, Aug 6, 2008 at 9:59 PM, Virgilio Gómez Rubio
> >> <becario...@gmail.com> wrote:
> >> > Jojo,
> >> >
> >> > Many thanks for the patch. I had tried that option
> >> > before but unfortunately it does not work with
> >> > my card (do not ask me why...).
> >> >
> >>
> >> My diff/patch should have worked for you,
> >> is it possible that you are doing something wrong ?
> >>
> >> I'll need to know more to diagnose your problem
> >>
> >> -JoJo
> >
> >

[Brian Johnson]

microdia-decoder probably needs to be patched to use the right
decoding routine for this model i would guess

[JoJo jojo]

Fwd'in the list

-JoJo

---------- Forwarded message ----------
From: Jon Arnold <jonarno...@gmail.com>
Date: Sun, Aug 24, 2008 at 11:46 PM
Subject: Re: Lets get to it...
To: JoJo jojo <onetw...@gmail.com>

0c45:627b, with SN9C201 bridge and OV7660 image sensor, found in Pixxo
AW-I1130 (http://www.mypixxo.com/product/AW-I1130.html) i.e. cheap
webcam from Fry's.

[JoJo jojo]

Hi Jon

email micr...@googlegroups.com, that way you will get faster response ;-)

On Sun, Aug 24, 2008 at 11:57 PM, Jon Arnold <jonarno...@gmail.com> wrote:
> Wow, fast reply. I'm actually getting a very yellow picture in Cheese. It's
> attached. Also I get a weird output in Skype. Ubuntu's screenshot program
> doesn't seem to want to save a screenshot of the Skype window. I will work
> on getting this.
>

Yellow picture can be fixed by increasing the blue color component,
you will need the GUI tool V4L2UCP pointed out here
https://groups.google.com/group/microdia/msg/b940018aa7bb84a5

> Also, I'm not really sure what I did but I downloaded the source from
> http://repo.or.cz/r/microdia.git
> because the Using Git page says that address but it also says
> http://repo.or.cz/w/microdia.git
> I'm not sure what the difference is, but when I realized this I tried to use
> the latter one and got an error.
>
>
> ~$ git clone http://repo.or.cz/w/microdia.git
> Initialized empty Git repository in /home/jon/microdia/.git/
> error: Could not interpret response from server '<?xml version="1.0"
> encoding="utf-8"?>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-US" lang
> cd: 491: can't cd to /home/jon/microdia/.git/refs/remotes/origin
> Warning: Remote HEAD refers to nonexistent ref, unable to checkout.
>

do $ git clone http://repo.or.cz/r/microdia.git instead, you can use any of the
following repo mirroring URLs
git://repo.or.cz/microdia.git
http://repo.or.cz/r/microdia.git

I suspect the ~/r/~ is the repo while ~/w/~ is the web directory or
something similar

so do that & also test the patches posted to this group.

-JoJo