Embedded autobrightness with Vimicro ZC3XX

Dajka Tamás <[email protected]>
Newsgroups gmane.linux.drivers.spca50x.devel
Message-ID <[email protected]>
Hi,

I'm tring to use a Vimicro ZC3XX based cam on an Asus wl500gp running OpenWrt.

V4L is V4L2, driver is gspcav1-20070508.

Camera is working inside ok, but outside not (overbrighted). I'm using spcacat for grabbing. Is there any other way to get a proper picture? Should I compile spcaview to set autobrightness? Or is it possible to modify spcacat for autobrighting (that's what I was tring to do)?

I saw in the source files, that "Wrong device" means that it's not an SPCA ioctl device. What does that mean? Should I use GSPCA2 for autobright?

the dmesg output:
linux-2.6-brcm47xx/gspcav1-20070508/gspca_core.c: USB GSPCA camera found.(ZC3XX)
build_mipsel/linux-2.6-brcm47xx/gspcav1-20070508/gspca_core.c: [spca5xx_probe:4098] Camera type JPEG
build_mipsel/linux-2.6-brcm47xx/gspcav1-20070508/Vimicro/zc3xx.h: [zc3xx_config:515] Sensor ID:11
build_mipsel/linux-2.6-brcm47xx/gspcav1-20070508/Vimicro/zc3xx.h: [zc3xx_config:566] Find Sensor PB0330
build_mipsel/linux-2.6-brcm47xx/gspcav1-20070508/gspca_core.c: [spca5xx_getcapability:1215] maxw 640 maxh 480 minw 176 minh 144
usbcore: registered new interface driver gspca
build_mipsel/linux-2.6-brcm47xx/gspcav1-20070508/gspca_core.c: gspca driver 01.00.18 registered
usbcore: registered new interface driver spca5xx
build_mipsel/linux-2.6-brcm47xx/spca5xx-le/spca_core.c: spca5xx driver 00.57.06LE registered

Thanks,

                Tom

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

_______________________________________________
Spca50x-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/spca50x-devs
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.