What is your webcam model number/brand name ?
If you want to recieve emails from Microdia Group on your yahoo.es
account you can,
- Sign up on this mailing list from that account
- Set up gmail filter to forward all emails from Microdia Group to
your yahoo.es account
(or more specifically setup all emails containing the keyword 627f
to your yahoo account)
Your english is fine, don't worry.
-JoJo
Hi Vrexio
What is your webcam model number/brand name ?
On Wed, May 7, 2008 at 11:54 PM, Vreixo Formoso Lopes
<meta...@gmail.com> wrote:
> How can I know that? It is a webcam included in my laptop, a Lenovo 3000
> N100. Attached related info from
thats what I wanted to know, thanks
-JoJo
are there any logs from device 627f ? If not, could someone please
create some ?
This device doesn't use a fixed sensor model. The sensor configuration
is defined by an EEPROM (has nothing to do with the 0x50 EEPROM issue !).
For the reported camera models, the sensor configuration seems to be the
same as used by 624f.
However, to add support for this device, we need to know how to
determine this.
Frank
On Wed, May 7, 2008 at 1:01 AM, Vreixo Formoso Lopes wrote
thanks for the link (didn't find this mail in my archive).
Unfortunately, the log doesn't contain the needed data.
It would be nice if you could create another log using SniffUSB and
AMCAP (640x480, RGB24).
Please notice: we need a log from the FIRST start-stream after
connecting the camera to the USB-port (in your case: after system restart).
After stopping the stream, you should wait some seconds before you stop
the logging.
Thanks !
Frank
victorhr schrieb:
Frank
victorhr schrieb:
your log is valid. It seems that the driver reads about 500 bytes from
the EEPROM.
Because address space for each slave is limited to 256 bytes, the driver
uses slave 0x50 for the first 256 bytes and slave 0x51 for bytes 257-512.
I will need some time to work it through.
Frank
victorhr schrieb:
which Notebook (Lenovo 3000 XXXX) do you have ? Which cam does it use
(LiteOn or Chicony) ?
Although init-/start-/stop-sequences of device 624f seems to work for
(some ?) 627f devices, too, these cams are not identic (otherwise they
would have the same PID ;-) ). We need to work out the differences.
Frank
Vreixo Formoso Lopes schrieb:
> Hi!
>
> I have this webcam (0c45:627f) working with the code from
> /*http://repo.or.cz/r/microdia.git */just changing the code as I tell
> in my mail on May 7, 2008:
>
> ------------
> > I've a microdia webcam, with usb id 0c45:627f. This is not listed as
> > supported webcam. However, I have chosen to give the driver a try,
> and to
> > make make webcam work, I've chaged in microdia.h the definition of
> > USB_UDIA_624F_PRODUCT_ID to be 0x627f, and thus match my webcam. Then I
> > compile and... it works!!! And with very good quality!
> --------------------
>
> So, in my opinion both 627f and 624f can work with the same driver
> code. Adding support for it is trivial, I think.
>
>
> > are there any logs from device 627f ? If not, could someone please
> > create some ?
>
> How can I do that?
>
> Cheers
> Vreixo
>
>
> 2008/5/26 victorhr <victor.hr <http://victor.hr>@gmail.com
> <http://gmail.com>>:
>
>
> Answers:
> 1.) Yes.
> 2.) Lenovo 3000 N100, I'll tell you the model number this afternoon,
> when I get home.
> 3.) I'll try to find out this afternoon. However the lenovo windows
> driver comes with both drivers.
> 4.) Windows showed the icon of new hardware found, but it couldn't
> finish to install the cam. I think windows couldn't recognize the cam
> with the sonix driver.
> 5.) Yes, as long as you put it in an anti-automatic spam way.
> Sorry for not having answered before.
> Thanks for your wonk on the cam support!
>
> Victor
>
> 2008/5/24 Comer352l <comer3...@web.de <mailto:comer3...@web.de>>:
> - Ocultar texto citado -
> > Hi Victor,
> >
> > I need some additional informations:
> > 1.) is your device identified as 0c45:627f using lsusb ?
> > 2.) in which notebook is it used (Lenovo 3000 XXXX)
> > 3.) there must be 2 different cams in Lenove 3000 notebooks: a
> Chicony and a
> > LiteOn. Could you please try to find out, which one it is (maybe
> looking at
> > the windows driver information)
> > 4.) Looking at the log, I wonder why the Sonix driver didn't
> work. Which
> > problem did you have when installing the driver ?
> > 5.) I plan to upload a memory map of your EEPROM. Is it OK for
> you to put
> > your mail address into it ?
> >
> > Frank
> >
>
> On 24 mayo, 12:33, Comer352l <comer3...@web.de
Hi Vreixo,
which Notebook (Lenovo 3000 XXXX) do you have ?
Which cam does it use
(LiteOn or Chicony) ?
Although init-/start-/stop-sequences of device 624f seems to work for
(some ?) 627f devices, too, these cams are not identic (otherwise they
would have the same PID ;-) ). We need to work out the differences.
take a look at the Windows driver to find out your cam's manufacturer:
v5.4.x.x = Chicony
v5.5.x.x or v5.7.x.x = LiteOn
(WinXP only)
Could you create a USB-log of the init-/start-/stop sequence ?
Frank
Vreixo Formoso Lopes schrieb:
> Hi!
>
> 2008/5/28 Comer352l <come...@web.de <mailto:come...@web.de>>:
> <mailto:comer3...@web.de> <mailto:comer3...@web.de
> <mailto:comer3...@web.de>>>:
> > - Ocultar texto citado -
> > > Hi Victor,
> > >
> > > I need some additional informations:
> > > 1.) is your device identified as 0c45:627f using lsusb ?
> > > 2.) in which notebook is it used (Lenovo 3000 XXXX)
> > > 3.) there must be 2 different cams in Lenove 3000 notebooks: a
> > Chicony and a
> > > LiteOn. Could you please try to find out, which one it is
> (maybe
> > looking at
> > > the windows driver information)
> > > 4.) Looking at the log, I wonder why the Sonix driver didn't
> > work. Which
> > > problem did you have when installing the driver ?
> > > 5.) I plan to upload a memory map of your EEPROM. Is it OK for
> > you to put
> > > your mail address into it ?
> > >
> > > Frank
> > >
> >
> > On 24 mayo, 12:33, Comer352l <comer3...@web.de
> <mailto:comer3...@web.de>
Hi,
take a look at the Windows driver to find out your cam's manufacturer:
v5.4.x.x = Chicony
v5.5.x.x or v5.7.x.x = LiteOn
(WinXP only)
Could you create a USB-log of the init-/start-/stop sequence ?
Please use SniffUSB (logger) and AMcap (application). You can het AMcap
here: http://www.noeld.com/programs.asp?cat=video#AMCap
We need a short log that contains connection of the device (init), start
stream (start video), stop stream.
Please note:
- set AMCAP to 640x480, RGB24
- we need a log from the FIRST start-stream after connecting the camera
to the USB-port (in your case: after system restart)
- after stopping the stream, you should wait some seconds before you
stop the logging
Thanks !
Frank
Please read
http://groups.google.com/group/microdia/web/usb-sniffing-on-windows.
Please use SniffUSB (logger) and AMcap (application). You can het AMcap
here: http://www.noeld.com/programs.asp?cat=video#AMCap
We need a short log that contains connection of the device (init), start
stream (start video), stop stream.
Please note:
- set AMCAP to 640x480, RGB24
- we need a log from the FIRST start-stream after connecting the camera- after stopping the stream, you should wait some seconds before you
to the USB-port (in your case: after system restart)
stop the logging
Thanks !
Frank
No, we need logs from the Windows-driver.
As soon as I finished working on 62b3, I will post patches for finally
adding 627f.
Please stay tuned for testing them, you know I can't push them without
at least 2 sign-offs.
In the next weeks, I will also send you a special patch that will read
out the content of your cam's EEPROM.
Frank