Talk:FAQ
From Ov51x JPEG hacked Wiki
When I modprobe ov519_decomp it complains about unknown symbols. What's wrong?
If you're getting similar messages in dmesg:
ov519_decomp: disagrees about version of symbol ov511_deregister_decomp_module ov519_decomp: Unknown symbol ov511_deregister_decomp_module ov519_decomp: disagrees about version of symbol ov511_register_decomp_module ov519_decomp: Unknown symbol ov511_register_decomp_module
It's likely that the ov511 driver included in the 2.6 kernel is getting in the way. Move it someplace and try again:
# mv /lib/modules/`uname -r`/kernel/drivers/usb/media/ov511.ko \
/lib/modules/`uname -r`/kernel/drivers/usb/media/ov511.ko.orig
# depmod -a
# modprobe ov519_decomp
Compilation with kernels => 2.6.19
With recent kernel, the first include to linux/config.h has to be changed for linux/autoconf.h. You can either edit the code or create a symlink the new. I won't release a new version, since this is tricky to correctly solve (this files gives the kernel verison, so no preprocessing possible), and I will switch definitly for next release, see svn sources for more info.
Will the patches of the original ov51x driver be also included?
(The last available version of ov51x driver contains
support for new chipsets such as OV530. However, it cannot be compiled for kernel version larger than 2.6.16. --Szazs89 19:58, 1 January 2007 (CET))
- I'll do this ASAP Toots 17:20, 13 January 2007 (CET)
Done in lastest svn ! Toots 23:01, 21 January 2007 (CET)
I have a Creative Live! Cam Vista IM. Can this driver be good for it?
(...after some modifications?)
I have found no supported device/chipset page, hence, I write here:
- See details about this device at http://www.qbik.ch/usb/devices/
- From the V0260530.set file of the Creative(TM) driver it seems that it has ov7670 sensor and OV530 chipset;
- I have tried to patch the 0.5.4 version:
--- ov51x-jpeg-0.5.4/ov51x.c 2006-09-28 12:46:21.000000000 +0200
+++ ov51x-jpeg-0.5.4-creative/ov51x.c 2007-01-01 17:51:41.000000000 +0100
@@ -418,6 +418,7 @@
{ USB_DEVICE(VEND_SONY, PROD_EYETOY4) },
{ USB_DEVICE(VEND_SONY, PROD_EYETOY5) },
{ USB_DEVICE(VEND_MATTEL, PROD_ME2CAM) },
+ { USB_DEVICE(VEND_CREATIVE, PROD_LIVE_VISTA_IM) },
{ } /* Terminating entry */
};
@@ -8230,6 +8231,10 @@
&& dev->descriptor.idProduct != PROD_EYETOY4
&& dev->descriptor.idProduct != PROD_EYETOY5)
return NULL;
+
+ if (dev->descriptor.idVendor == VEND_CREATIVE
+ && dev->descriptor.idProduct != PROD_LIVE_VISTA_IM)
+ return NULL;
#endif
#if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 5, 36)
@@ -8291,6 +8296,7 @@
case PROD_OV519:
case PROD_OV4519:
case PROD_OV8519:
+ case PROD_LIVE_VISTA_IM:
ov->bridge = BRG_OV519;
ov->bclass = BCL_OV519;
break;
--- ov51x-jpeg-0.5.4/ov51x.h 2006-09-28 12:44:18.000000000 +0200
+++ ov51x-jpeg-0.5.4-creative/ov51x.h 2007-01-01 17:48:19.000000000 +0100
@@ -103,6 +103,9 @@
#define PROD_EYETOY6 0x0156
#define PROD_EYETOY7 0x0157
+#define VEND_CREATIVE 0x041e
+#define PROD_LIVE_VISTA_IM 0x4052
+
/* --------------------------------- */
/* DEVICE IMPLEMENTATIONS */
/* --------------------------------- */
(the compilation to kernel 2.6.19.1 was successful) and when connecting to the USB:
usb 2-1: new full speed USB device using uhci_hcd and address 7 usb 2-1: configuration #1 chosen from 1 choice Linux video capture interface: v2.00 /mnt/h/src/ov51x-jpeg-0.5.4-creative/ov51x.c: USB OV519 video device found /mnt/h/src/ov51x-jpeg-0.5.4-creative/ov51x.c: Sensor is an OV7610 /mnt/h/src/ov51x-jpeg-0.5.4-creative/ov51x.c: Sensor not supported for OV519! /mnt/h/src/ov51x-jpeg-0.5.4-creative/ov51x.c: Camera initialization failed ov51x: probe of 2-1:1.0 failed with error -5 usbcore: registered new interface driver ov51x /mnt/h/src/ov51x-jpeg-0.5.4-creative/ov51x.c: v1.65-1.11-mark : ov51x USB Camera Driver
- After spending more time on hacking ov51x.c around line no.7307 and trying to read product id registers using the i2c_r() function I have obtained 0x7673.
- That's all I could do. Now the question is how to go further...?
--Szazs89 20:59, 1 January 2007 (CET)
- This device is claimed as an ov530/ov519 device, but the driver lacks support of the sensor (and its product number is not yet known..) Any help from a hacker owning this device would be welcome ! Toots 23:02, 21 January 2007 (CET)
- I have this device and I'm searching for some driver for months! What should I do to help you? --Endrju 21:38, 23 February 2007 (CET)
- This kernel patch may be of interest - it purports to be a V4L driver for OV7670 cameras, like the Vista IM appears to be. Present in the 2.6.20 kernel. Aoanla 14:47, 7 March 2007 (CET)
- Further to the above: I am currently in the process of hacking together something like OV7670 support for all the functions in the OV51x-jpeg driver. I may have something usable by the end of the coming weekend, depending on testing. I'll keep you all informed, and post a diff if I get things working. If anyone else is actually developing for OV7670 support, please contact me. Aoanla 18:54, 7 March 2007 (CET)
For better communication, I have opened a mailing list at this place: http://lists.rastageeks.org/cgi-bin/listinfo/ov51x-jpeg Toots 13:42, 8 March 2007 (CET)
- I signed up to the mailing list, and sent mail, but it appears I haven't been approved yet! For people who care to know things quickly: my modifications to the driver, based on the 2.6.20 kernel ov7670.c driver, produce output. The output is mangled, probably because the driver seems to expect YUV420 colourspace, and the ov7670 doesn't produce this output - only YUV422, RGB565, RGB555, RGB444. Still, there is mangled output! Aoanla 22:19, 9 March 2007 (CET)
- Did you check your spam folder? In my case, the confirmation mail was wrongly classified as SPAM --Fons 20:00, 3 April 2007 (CEST)
Using a usb Hub, my camera fails to initialize
Yes, true, but why? This HUB is externally powered and seem to be able to handle all the speed requirements. --Grin 21:23, 15 September 2009 (UTC)
