From hwaechtler@yahoo.com Mon, 1 May 2000 11:36:25 +0200 (CEST) Date: Mon, 1 May 2000 11:36:25 +0200 (CEST) From: Holger Waechtler hwaechtler@yahoo.com Subject: [cpia] Should multiple USB cameras work ??? Hi everybody, I tried to get two TerraCAM USB cameras on the ports of my USB controller working, but unfortunally I didn't was very successful. Every single cam works fine, but together I get only the first frame from the second camera and then both capture processes freeze. The kernel log is full of messages like: cpia data error: [8] len=844, status=FFFFFFC1A and: cpia: scratch buf overflow!scr_len: 32217, n: 960 I tried Kernel 2.2.14 with the USB backport and 2.3.99-pre6, both with the kernel driver and the the seperate driver from the cpia project page. The behaviour changed a bit (the old kernel driver crashed my box, the new versions can be recovered by unloading/reloading the module), but none was able to capture from both cameras at the same time. Is this not yet supported by the driver or am I just doing something stupid ? If it should work, but is not tested, where may be problems, where might I look ? What logs do you need ? - Holger From nikom@merl.com Tue, 02 May 2000 14:49:06 -0400 Date: Tue, 02 May 2000 14:49:06 -0400 From: Jacob Nikom nikom@merl.com Subject: [cpia] gqcam hangs with D status Hi, I am running gqcam application on cpia-0.7.4 on 2.3.99-pre5. using WebCamII Creative Labs camera. My computer is PII 233MHz. It runs well but after some time it hangs. Then create process with D status (uninterruptable sleep) and I cannot kill it but only rebooting my machine. Is it expected behavior? How to kill the process without reboting? Thank you, Jacob Nikom From jerdfelt@sventech.com Tue, 2 May 2000 15:10:29 -0400 Date: Tue, 2 May 2000 15:10:29 -0400 From: Johannes Erdfelt jerdfelt@sventech.com Subject: [cpia] gqcam hangs with D status On Tue, May 02, 2000, Jacob Nikom wrote: > > I am running gqcam application on cpia-0.7.4 on 2.3.99-pre5. > using WebCamII Creative Labs camera. My computer is PII 233MHz. > It runs well but after some time it hangs. Then create process > with D status (uninterruptable sleep) and I cannot kill it but > only rebooting my machine. > > Is it expected behavior? Not expected behaviour, however it is known. Check the latest CVS version which has the fix. I also posted a fix to the list a couple of weeks ago but I don't know if the list is archived anywhere. > How to kill the process without reboting? You can't. JE From Peter_Pregler@email.com Wed, 3 May 2000 08:29:07 +0200 Date: Wed, 3 May 2000 08:29:07 +0200 From: Peter Pregler Peter_Pregler@email.com Subject: [cpia] gqcam hangs with D status On Tue, May 02, 2000 at 03:10:29PM -0400, Johannes Erdfelt wrote: > > I also posted a fix to the list a couple of weeks ago but I don't know > if the list is archived anywhere. It is done automatically by the listserver. See the url at the bottom of any message. -Peter -- I will not waste chalk. --Bart Simpson at the blackboard -------------------------------------------------------- Email: Peter_Pregler@email.com WWW: http://www.risc.uni-linz.ac.at/people/ppregler From piero.campanelli@galactica.it Wed, 3 May 2000 09:38:28 +0200 Date: Wed, 3 May 2000 09:38:28 +0200 From: Piero Campanelli piero.campanelli@galactica.it Subject: [cpia] Webcam creative II and brightness ? This is a multi-part message in MIME format. ------=_NextPart_000_0066_01BFB4E3.562ED970 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi. I am working with Creative II and kernel 2.3.99pre6. All works well !! I = am making screeenshoot on my webpage using 'vidcat' but i am unhappy. = Every time i do a vidcat, vidcat open the CAM and make the photo. = However cam needs two or three seconds to adjust it's settings according = the lights in the room. So the result is that i have photos too dark or too bright. Any help on a better software ?? Thanks Piero ------=_NextPart_000_0066_01BFB4E3.562ED970 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi.
 
I am working with Creative II and = kernel=20 2.3.99pre6. All works well !! I am making screeenshoot on my webpage = using=20 'vidcat' but i am unhappy. Every time i do a vidcat, vidcat open the CAM = and=20 make the photo. However cam needs two or three seconds to adjust it's = settings=20 according the lights in the room.
 
So the result is that i have photos too = dark or too=20 bright.
 
Any help on a better software = ??

Thanks
Piero
 
------=_NextPart_000_0066_01BFB4E3.562ED970-- From piero.campanelli@galactica.it Wed, 3 May 2000 10:03:46 +0200 Date: Wed, 3 May 2000 10:03:46 +0200 From: Piero Campanelli piero.campanelli@galactica.it Subject: [cpia] USB CAM crash Hi. I am loading kernel 2.3.99pre6 (so I think with the latest patchs of cpia driver). However after 30 minutes drivers crash ! When i do a new videocapture I receive: Can't open device /dev/video So the only thing I can do is to reboot the machine. Could you help me ? Evetnually how can i refix it without rebooting ? Tnx From Henry.BRUCE@st.com Wed, 3 May 2000 10:33:27 +0100 (BST) Date: Wed, 3 May 2000 10:33:27 +0100 (BST) From: Henry Bruce Henry.BRUCE@st.com Subject: [cpia] Webcam creative II and brightness ? > Hi. > > I am working with Creative II and kernel 2.3.99pre6. All works well !! I am > making screeenshoot on my webpage using 'vidcat' but i am unhappy. Every > time i do a vidcat, vidcat open the CAM and make the photo. However cam > needs two or three seconds to adjust it's settings according the lights in > the room. > > So the result is that i have photos too dark or too bright. This happens because the firmware always goes to a mid range exposure on device initialisation, and it takes a number of frames to reach the correct value. This will take longer if a low sensor frame rate is selected. The Windows driver avoids the delay (in some cases) by remembering the exposure (and gain) from the last session and applying it when the driver opens. Regards, Henry Bruce From nikom@merl.com Wed, 03 May 2000 10:44:15 -0400 Date: Wed, 03 May 2000 10:44:15 -0400 From: Jacob Nikom nikom@merl.com Subject: [cpia] USB CAM crash Hi Piero, I have the same behavior. Johannes Erdfelt said that it is fixed in pre6 but maybe it did not get in yet. You could verify that the latest patch is over there. Go to the directory: /usr/src/linux/drivers/char Look at the file cpia.c. Starting from the line 1579 you should see the code from the patch: retval = cam->ops->transferCmd(cam->lowlevel_data, cmd, data); - if (retval) + if (retval) { DBG("%x - failed, retval=%d\n", command, retval); - else { + if (command == CPIA_COMMAND_GetColourParams || + command == CPIA_COMMAND_GetColourBalance || + command == CPIA_COMMAND_GetExposure) + up(&cam->param_lock); + } else { switch(command) { case CPIA_COMMAND_GetCPIAVersion: cam->params.version.firmwareVersion = data[0]; I did not recompiled my kernel yet to verify the fix. Regards, Jacob Nikom Piero Campanelli wrote: > > Hi. > > I am loading kernel 2.3.99pre6 (so I think with the latest patchs of cpia > driver). However after 30 minutes drivers crash ! > When i do a new videocapture I receive: > > Can't open device /dev/video > > So the only thing I can do is to reboot the machine. Could you help me ? > Evetnually how can i refix it without rebooting ? > > Tnx > > _______________________________________________ > cpia mailing list - cpia@risc.uni-linz.ac.at > http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia From piero.campanelli@galactica.it Wed, 3 May 2000 20:40:55 +0200 Date: Wed, 3 May 2000 20:40:55 +0200 From: Piero Campanelli piero.campanelli@galactica.it Subject: R: [cpia] USB CAM crash Hi The patch is present in the kernel pre6 (i have seen this code in soruce kernel)...so I think the problem is more serious :-) This is the report for today: Started at 9.00 am Crash at 9.43 (reboot) Crash at 15.30 (reboot) At the moment is live.... I do every 56 second a vidcat -f jpeg -d /dev/video1 ... Byeee : /usr/src/linux/drivers/char : : Look at the file cpia.c. Starting from the line 1579 : you should see the code from the patch: : retval = cam->ops->transferCmd(cam->lowlevel_data, cmd, data); : - if (retval) : + if (retval) { : DBG("%x - failed, retval=%d\n", command, retval); : - else { : + if (command == CPIA_COMMAND_GetColourParams || : + command == CPIA_COMMAND_GetColourBalance || : + command == CPIA_COMMAND_GetExposure) : + up(&cam->param_lock); : + } else { : switch(command) { : case CPIA_COMMAND_GetCPIAVersion: : cam->params.version.firmwareVersion = data[0]; : : I did not recompiled my kernel yet to verify the fix. : : Regards, : : Jacob Nikom : : : Piero Campanelli wrote: : > : > Hi. : > : > I am loading kernel 2.3.99pre6 (so I think with the latest : patchs of cpia : > driver). However after 30 minutes drivers crash ! : > When i do a new videocapture I receive: : > : > Can't open device /dev/video : > : > So the only thing I can do is to reboot the machine. Could you help me ? : > Evetnually how can i refix it without rebooting ? : > : > Tnx : > : > _______________________________________________ : > cpia mailing list - cpia@risc.uni-linz.ac.at : > http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia From jerdfelt@sventech.com Wed, 3 May 2000 14:47:44 -0400 Date: Wed, 3 May 2000 14:47:44 -0400 From: Johannes Erdfelt jerdfelt@sventech.com Subject: R: [cpia] USB CAM crash Could you giv us some more information? Such as some logs? Run dmesg after you have some problems and there should be some messages which may give us some information. JE On Wed, May 03, 2000, Piero Campanelli wrote: > Hi > > The patch is present in the kernel pre6 (i have seen this code in soruce > kernel)...so I think the problem is more serious :-) > > This is the report for today: > > Started at 9.00 am > Crash at 9.43 (reboot) > Crash at 15.30 (reboot) > > At the moment is live.... > > I do every 56 second a > > vidcat -f jpeg -d /dev/video1 ... > > Byeee > > > > : /usr/src/linux/drivers/char > : > : Look at the file cpia.c. Starting from the line 1579 > : you should see the code from the patch: > : retval = cam->ops->transferCmd(cam->lowlevel_data, cmd, data); > : - if (retval) > : + if (retval) { > : DBG("%x - failed, retval=%d\n", command, retval); > : - else { > : + if (command == CPIA_COMMAND_GetColourParams || > : + command == CPIA_COMMAND_GetColourBalance || > : + command == CPIA_COMMAND_GetExposure) > : + up(&cam->param_lock); > : + } else { > : switch(command) { > : case CPIA_COMMAND_GetCPIAVersion: > : cam->params.version.firmwareVersion = data[0]; > : > : I did not recompiled my kernel yet to verify the fix. > : > : Regards, > : > : Jacob Nikom > : > : > : Piero Campanelli wrote: > : > > : > Hi. > : > > : > I am loading kernel 2.3.99pre6 (so I think with the latest > : patchs of cpia > : > driver). However after 30 minutes drivers crash ! > : > When i do a new videocapture I receive: > : > > : > Can't open device /dev/video > : > > : > So the only thing I can do is to reboot the machine. Could you help me ? > : > Evetnually how can i refix it without rebooting ? > : > > : > Tnx > : > > : > _______________________________________________ > : > cpia mailing list - cpia@risc.uni-linz.ac.at > : > http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia > > > _______________________________________________ > cpia mailing list - cpia@risc.uni-linz.ac.at > http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia > From piero.campanelli@galactica.it Wed, 3 May 2000 20:53:56 +0200 Date: Wed, 3 May 2000 20:53:56 +0200 From: Piero Campanelli piero.campanelli@galactica.it Subject: R: R: [cpia] USB CAM crash This is a multi-part message in MIME format. ------=_NextPart_000_0003_01BFB541.B2E1AFE0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Here it is the log :) After I have received your mail, CAM crashed ....:))) Byeee : -----Messaggio originale----- : Da: Johannes Erdfelt [mailto:jerdfelt@sventech.com] : Inviato: mercoledi 3 maggio 2000 20.48 : A: Piero Campanelli : Cc: nikom@merl.com; cpia@risc.uni-linz.ac.at : Oggetto: Re: R: [cpia] USB CAM crash : : : Could you giv us some more information? Such as some logs? Run dmesg : after you have some problems and there should be some messages which may : give us some information. : : JE : : On Wed, May 03, 2000, Piero Campanelli : wrote: : > Hi : > : > The patch is present in the kernel pre6 (i have seen this code in soruce : > kernel)...so I think the problem is more serious :-) : > : > This is the report for today: : > : > Started at 9.00 am : > Crash at 9.43 (reboot) : > Crash at 15.30 (reboot) : > : > At the moment is live.... : > : > I do every 56 second a : > : > vidcat -f jpeg -d /dev/video1 ... : > : > Byeee : > : > : > : > : /usr/src/linux/drivers/char : > : : > : Look at the file cpia.c. Starting from the line 1579 : > : you should see the code from the patch: : > : retval = cam->ops->transferCmd(cam->lowlevel_data, cmd, data); : > : - if (retval) : > : + if (retval) { : > : DBG("%x - failed, retval=%d\n", command, retval); : > : - else { : > : + if (command == CPIA_COMMAND_GetColourParams || : > : + command == CPIA_COMMAND_GetColourBalance || : > : + command == CPIA_COMMAND_GetExposure) : > : + up(&cam->param_lock); : > : + } else { : > : switch(command) { : > : case CPIA_COMMAND_GetCPIAVersion: : > : cam->params.version.firmwareVersion = data[0]; : > : : > : I did not recompiled my kernel yet to verify the fix. : > : : > : Regards, : > : : > : Jacob Nikom : > : : > : : > : Piero Campanelli wrote: : > : > : > : > Hi. : > : > : > : > I am loading kernel 2.3.99pre6 (so I think with the latest : > : patchs of cpia : > : > driver). However after 30 minutes drivers crash ! : > : > When i do a new videocapture I receive: : > : > : > : > Can't open device /dev/video : > : > : > : > So the only thing I can do is to reboot the machine. Could : you help me ? : > : > Evetnually how can i refix it without rebooting ? : > : > : > : > Tnx : > : > : > : > _______________________________________________ : > : > cpia mailing list - cpia@risc.uni-linz.ac.at : > : > http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia : > : > : > _______________________________________________ : > cpia mailing list - cpia@risc.uni-linz.ac.at : > http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia : > ------=_NextPart_000_0003_01BFB541.B2E1AFE0 Content-Type: application/octet-stream; name="boot.message" Content-Disposition: attachment; filename="boot.message" Content-Transfer-Encoding: quoted-printable Linux version 2.3.99-pre6 (root@pclabsrv) (gcc version egcs-2.91.66 = 19990314/Linux (egcs-1.1.2 release)) #4 Mon May 1 21:33:49 CEST 2000=0A= e820: 0009fc00 @ 00000000 (usable)=0A= e820: 00000400 @ 0009fc00 (reserved)=0A= e820: 00010000 @ 000f0000 (reserved)=0A= e820: 07efd000 @ 00100000 (usable)=0A= e820: 00002000 @ 07ffd000 (ACPI data)=0A= e820: 00001000 @ 07fff000 (ACPI NVS)=0A= e820: 00010000 @ ffff0000 (reserved)=0A= On node 0 totalpages: 32765=0A= zone(0): 4096 pages.=0A= zone(1): 28669 pages.=0A= zone(2): 0 pages.=0A= Initializing CPU#0=0A= Detected 350798462 Hz processor.=0A= Console: colour VGA+ 80x25=0A= Calibrating delay loop... 699.60 BogoMIPS=0A= Memory: 126676k/131060k available (1213k kernel code, 3996k reserved, = 90k data, 188k init, 0k highmem)=0A= VFS: DCACHE hash table configured to 16384 entries=0A= Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes)=0A= Page-cache hash table entries: 32768 (order: 5, 131072 bytes)=0A= VFS: INODE hash table configured to 8192 entries=0A= CPU: Intel Pentium II (Deschutes) stepping 02=0A= Checking 386/387 coupling... OK, FPU using exception 16 error reporting.=0A= Checking 'hlt' instruction... OK.=0A= POSIX conformance testing by UNIFIX=0A= mtrr: v1.36 (20000221) Richard Gooch (rgooch@atnf.csiro.au)=0A= PCI: PCI BIOS revision 2.10 entry at 0xf0720, last bus=3D1=0A= PCI: Using configuration type 1=0A= PCI: Probing PCI hardware=0A= PCI: Using IRQ router PIIX [8086/122e] at 00:04.0=0A= Limiting direct PCI/PCI transfers.=0A= Linux NET4.0 for Linux 2.3=0A= Based upon Swansea University Computer Society NET3.039=0A= NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.=0A= NET4: Linux TCP/IP 1.0 for NET4.0=0A= IP Protocols: ICMP, UDP, TCP, IGMP=0A= IP: routing cache hash table of 512 buckets, 4Kbytes=0A= TCP: Hash tables configured (established 8192 bind 8192)=0A= Initializing RT netlink socket=0A= Starting kswapd v1.6=0A= pty: 256 Unix98 ptys configured=0A= Uniform Multi-Platform E-IDE driver Revision: 6.30=0A= ide: Assuming 33MHz system bus speed for PIO modes; override with = idebus=3Dxx=0A= PIIX4: IDE controller on PCI bus 00 dev 21=0A= PIIX4: not 100% native mode: will probe irqs later=0A= ide0: BM-DMA at 0xb800-0xb807, BIOS settings: hda:DMA, hdb:DMA=0A= ide1: BM-DMA at 0xb808-0xb80f, BIOS settings: hdc:DMA, hdd:pio=0A= hda: QUANTUM FIREBALL CR4.3A, ATA DISK drive=0A= hdb: FUJITSU MPD3108AT, ATA DISK drive=0A= hdc: ASUS CD-S400/A, ATAPI CDROM drive=0A= ide0 at 0x1f0-0x1f7,0x3f6 on irq 14=0A= ide1 at 0x170-0x177,0x376 on irq 15=0A= hda: 8418816 sectors (4310 MB) w/418KiB Cache, CHS=3D524/255/63, UDMA(33)=0A= hdb: 21095424 sectors (10801 MB) w/512KiB Cache, CHS=3D1313/255/63, = UDMA(33)=0A= hdc: ATAPI 40X CD-ROM drive, 128kB Cache, UDMA(33)=0A= Uniform CD-ROM driver Revision: 3.07=0A= Partition check:=0A= hda: hda1 hda2 < hda5 >=0A= hdb: hdb1=0A= md driver 0.90.0 MAX_MD_DEVS=3D256, MAX_REAL=3D12=0A= md.c: sizeof(mdp_super_t) =3D 4096=0A= scsi : 0 hosts.=0A= scsi : detected total.=0A= Serial driver version 4.93 (2000-03-20) with MANY_PORTS SHARE_IRQ = SERIAL_PCI enabled=0A= ttyS00 at 0x03f8 (irq =3D 4) is a 16550A=0A= ttyS01 at 0x02f8 (irq =3D 3) is a 16550A=0A= VFS: Mounted root (ext2 filesystem) readonly.=0A= Freeing unused kernel memory: 188k freed=0A= Adding Swap: 265032k swap-space (priority -1)=0A= 8139too Fast Ethernet driver 0.9.4 loaded=0A= eth0: RealTek RTL8139 Fast Ethernet at 0xe0800000, IRQ 10, = 00:00:b4:aa:fb:d1.=0A= PPP generic driver version 2.4.1=0A= i2c-core.o: i2c core module=0A= Linux video capture interface: v1.00=0A= saa7146_init_one()=0A= i2c-core.o: adapter saa7146(1) registered as adapter 0.=0A= saa7146_core.o: saa7146(1): bus:0, rev:1, mem:0xc8847000.=0A= i2c-core.o: driver VES1893 DVB DECODER registered.=0A= VES1893: attaching VES1893 at 0x10=0A= i2c-core.o: client [VES1893] registered to adapter [saa7146(1)](pos. 0).=0A= VES1893: init chip=0A= VES1893: attached to adapter saa7146(1)=0A= VES1893: init_module=0A= i2c-core.o: driver VES1820 DVB DECODER registered.=0A= VES1820: init_module=0A= i2c-core.o: driver dvbi2c registered.=0A= dvb: ARM firmware successfully loaded.=0A= dvb: firmware =3D f0240009=0A= dvb: MAC =3D 00 d0 5c 2d ca 88 =0A= dvb: attach_adapter=0A= dvb: attached/detached client VES1893 in dvb(0)=0A= dvb: 1 dvb(s) found!=0A= i2c-core.o: driver i2c TV tuner driver registered.=0A= tuner: chip found @ 0x61=0A= dvb: attached/detached client i2c tv tuner chip in dvb(0)=0A= VES1893: init chip=0A= i2c-core.o: client [SP5659] registered to adapter [saa7146(1)](pos. 1).=0A= i2c-core.o: driver i2c msp3400 driver registered.=0A= V4L-Driver for Vision CPiA based cameras v0.7.4=0A= usb.c: registered new driver usbdevfs=0A= usb.c: registered new driver hub=0A= usb.c: registered new driver cpia=0A= uhci.c: USB UHCI at I/O 0xb400, IRQ 5=0A= uhci.c: detected 2 ports=0A= usb.c: new USB bus registered, assigned bus number 1=0A= usb.c: USB new device connect, assigned device number 1=0A= usb.c: kmalloc IF c61999a0, numif 1=0A= usb.c: new device strings: Mfr=3D0, Product=3D2, SerialNumber=3D1=0A= usb.c: USB device number 1 default language ID 0x0=0A= Product: USB UHCI Root Hub=0A= SerialNumber: b400=0A= hub.c: USB hub found=0A= hub.c: 2 ports detected=0A= hub.c: ganged power switching=0A= hub.c: standalone hub=0A= hub.c: global over-current protection=0A= hub.c: power on to power good time: 2ms=0A= hub.c: hub controller current requirement: 0mA=0A= hub.c: port 1 is removable=0A= hub.c: port 2 is removable=0A= hub.c: local power source is good=0A= hub.c: no over-current condition exists=0A= hub.c: enabling power on all ports=0A= usb.c: hub driver claimed interface c61999a0=0A= uhci.c: root-hub INT complete: port1: 93 port2: 80 data: 2=0A= hub.c: port 1 connection change=0A= hub.c: portstatus 101, change 1, High Speed=0A= hub.c: portstatus 103, change 0, High Speed=0A= usb.c: USB new device connect, assigned device number 2=0A= usb.c: kmalloc IF c6199ca0, numif 1=0A= usb.c: new device strings: Mfr=3D0, Product=3D0, SerialNumber=3D0=0A= USB CPiA camera found=0A= CPiA Version: 1.20 (2.0)=0A= CPiA PnP-ID: 0553:0002:0100=0A= VP-Version: 1.0 0100=0A= usb.c: cpia driver claimed interface c6199ca0=0A= PPP BSD Compression module registered=0A= PPP Deflate Compression module registered=0A= ip_tables: (c)2000 Netfilter core team=0A= ip_conntrack (1023 buckets, 8184 max)=0A= cpia.c:parse_picture(1946):EOL not found giving up after 75/44020 bytes=0A= cpia.c:parse_picture(1964):line length was not 1 but 0 after 70/43488 = bytes=0A= cpia.c:parse_picture(1964):line length was not 1 but 0 after 70/37268 = bytes=0A= usb_control/bulk_msg: timeout=0A= ------=_NextPart_000_0003_01BFB541.B2E1AFE0-- From pcampanelli@acm.org Wed, 3 May 2000 21:06:46 +0200 Date: Wed, 3 May 2000 21:06:46 +0200 From: Piero Campanelli pcampanelli@acm.org Subject: [cpia] CAM Crash Hi i have found a fix for the moment ....it is cumbersome...but it works..... When cam crash....i unplug USB and replug....than i reload all kernel modules...and cam works....... Hope this help... Bye From nikom@merl.com Thu, 04 May 2000 19:02:45 -0400 Date: Thu, 04 May 2000 19:02:45 -0400 From: Jacob Nikom nikom@merl.com Subject: [cpia] Do you know other applications using usb WebCamII? Hi, I was able to install WebCamII on 2.3.99-pre5. The application, gqcam runs now very well. Do you know other, simplier applcations than gqcam (without so much GUI) which also use WebCamII? For example, simple one which takes one frame and saves it in .ppm. Thank you, Jacob From sbertin@mindspring.com Fri, 5 May 2000 00:55:16 -0400 (EDT) Date: Fri, 5 May 2000 00:55:16 -0400 (EDT) From: sbertin@mindspring.com sbertin@mindspring.com Subject: [cpia] Are we ready for 1.0? I'm planning on making a new release on Sunday, and I was wondering if this should be 0.8 or 1.0. The parallel port and core cpia code seem to be stable. There have been a few reports of problems with USB, but most of those are fixed in CVS already. The only outstanding issue I'm aware of is Piero Campanelli's report of his USB camera crashing occasionally. Is anybody making progress on this? Please try out the latest CVS code (I just made some minor changes tonight), and send any problems you have to the list. Scott J. Bertin sbertin@mindspring.com From zaitcev@metabyte.com Thu, 4 May 2000 23:44:57 -0700 (PDT) Date: Thu, 4 May 2000 23:44:57 -0700 (PDT) From: Pete Zaitcev zaitcev@metabyte.com Subject: [cpia] Barbie Cam baud rate? Itai seems to be out of the picture so I started to poke myself. First thing - they did not mention the proper baud rate for the VVL300. Does anyone know what it is? --Pete From Peter_Pregler@email.com Fri, 5 May 2000 09:10:11 +0200 Date: Fri, 5 May 2000 09:10:11 +0200 From: Peter Pregler Peter_Pregler@email.com Subject: [cpia] Barbie Cam baud rate? On Thu, May 04, 2000 at 11:44:57PM -0700, Pete Zaitcev wrote: > Itai seems to be out of the picture so I started to poke myself. > First thing - they did not mention the proper baud rate for the VVL300. > Does anyone know what it is? Yes, sorry for being lazy and not putting it on the web: > Details are as follows > > - 57,600 baud > - 8 data bits, no parity, 1 stop bit > - no handshaking -Peter -- I will not waste chalk. --Bart Simpson at the blackboard -------------------------------------------------------- Email: Peter_Pregler@email.com WWW: http://www.risc.uni-linz.ac.at/people/ppregler From nikom@merl.com Fri, 05 May 2000 12:00:45 -0400 Date: Fri, 05 May 2000 12:00:45 -0400 From: Jacob Nikom nikom@merl.com Subject: [cpia] Are we ready for 1.0? I am running WebCamII USB for more than 24 hours and did not have any problems. I installed all patches up to pre6. Jacob Nikom sbertin@mindspring.com wrote: > > I'm planning on making a new release on Sunday, and I was wondering if > this should be 0.8 or 1.0. The parallel port and core cpia code seem to > be stable. There have been a few reports of problems with USB, but most > of those are fixed in CVS already. > > The only outstanding issue I'm aware of is Piero Campanelli's report of > his USB camera crashing occasionally. Is anybody making progress on > this? > > Please try out the latest CVS code (I just made some minor changes > tonight), and send any problems you have to the list. > > Scott J. Bertin > sbertin@mindspring.com > > _______________________________________________ > cpia mailing list - cpia@risc.uni-linz.ac.at > http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia From piero.campanelli@galactica.it Fri, 05 May 2000 18:23:47 +0200 Date: Fri, 05 May 2000 18:23:47 +0200 From: Piero Campanelli piero.campanelli@galactica.it Subject: [cpia] Are we ready for 1.0? I have the problem the CAM drivers go down ! As first FIX i unplug CAM and reload cpia module!! Sometimes this isn't enough so I have to reboot machine (one time out 2 days). So I am quite happy with drivers !!!!! For your happyness in LINUX drivers crash isn't a bad news....in WIN instead a driver crash means an OS failure and a blue screen ;))))) Anyway i have pre6 kernel....have I to get a new version of cpia from CVS ? Byee At 12.00 05/05/2000 -0400, Jacob Nikom wrote: >I am running WebCamII USB for more than 24 hours and did not have >any problems. I installed all patches up to pre6. > >Jacob Nikom > > > >sbertin@mindspring.com wrote: > > > > I'm planning on making a new release on Sunday, and I was wondering if > > this should be 0.8 or 1.0. The parallel port and core cpia code seem to > > be stable. There have been a few reports of problems with USB, but most > > of those are fixed in CVS already. > > > > The only outstanding issue I'm aware of is Piero Campanelli's report of > > his USB camera crashing occasionally. Is anybody making progress on > > this? > > > > Please try out the latest CVS code (I just made some minor changes > > tonight), and send any problems you have to the list. > > > > Scott J. Bertin > > sbertin@mindspring.com > > > > _______________________________________________ > > cpia mailing list - cpia@risc.uni-linz.ac.at > > http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia > >_______________________________________________ >cpia mailing list - cpia@risc.uni-linz.ac.at >http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia From root@mail.velenje.cx Fri, 5 May 2000 19:23:07 +0200 (CEST) Date: Fri, 5 May 2000 19:23:07 +0200 (CEST) From: Samo Gabrovec root@mail.velenje.cx Subject: [cpia] Are we ready for 1.0? mine worked with 0.74 constantly until the cable broke ;) *up to +-30days without reloading the driver* ---------------------------------------------------------------- If you try to fail, and succeed, which have you done? ---------------------------------------------------------------- Visit http://www.velenje.cx ---------------------------------------------------------------- On Fri, 5 May 2000, Piero Campanelli wrote: > I have the problem the CAM drivers go down ! > As first FIX i unplug CAM and reload cpia module!! Sometimes this isn't > enough so I have to reboot machine (one time out 2 days). So I am quite > happy with drivers !!!!! > > For your happyness in LINUX drivers crash isn't a bad news....in WIN > instead a driver crash means an OS failure and a blue screen ;))))) > > Anyway i have pre6 kernel....have I to get a new version of cpia from CVS ? > > Byee > > > > At 12.00 05/05/2000 -0400, Jacob Nikom wrote: > >I am running WebCamII USB for more than 24 hours and did not have > >any problems. I installed all patches up to pre6. > > > >Jacob Nikom > > > > > > > >sbertin@mindspring.com wrote: > > > > > > I'm planning on making a new release on Sunday, and I was wondering if > > > this should be 0.8 or 1.0. The parallel port and core cpia code seem to > > > be stable. There have been a few reports of problems with USB, but most > > > of those are fixed in CVS already. > > > > > > The only outstanding issue I'm aware of is Piero Campanelli's report of > > > his USB camera crashing occasionally. Is anybody making progress on > > > this? > > > > > > Please try out the latest CVS code (I just made some minor changes > > > tonight), and send any problems you have to the list. > > > > > > Scott J. Bertin > > > sbertin@mindspring.com > > > > > > _______________________________________________ > > > cpia mailing list - cpia@risc.uni-linz.ac.at > > > http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia > > > >_______________________________________________ > >cpia mailing list - cpia@risc.uni-linz.ac.at > >http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia > > > _______________________________________________ > cpia mailing list - cpia@risc.uni-linz.ac.at > http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia > From sbertin@mindspring.com Sun, 7 May 2000 11:33:58 -0400 (EDT) Date: Sun, 7 May 2000 11:33:58 -0400 (EDT) From: sbertin@mindspring.com sbertin@mindspring.com Subject: [cpia] cpia-1.0 Version 1.0 is now available from http://webcam.sourceforge.net Scott J. Bertin sbertin@mindspring.com 2000-05-07 v1.0 Patch from Johannes Erdfelt - semaphore deadlock fix Patch from George Almasi - Intel QX3 microscope support Patch from Peter Pregler - 2.3.x block read instead of line-oriented read Patch from George Talusan - Fix compile problem with gcc-2.8.1 and _CPIA_DEBUG_ turned off. Patch from Scott J. Bertin - usb.h moved in kernel 2.3.51, #include it from the correct place - Fixes for VIDEO_PALETTE_GREY - Allow setting the yuv order - Support for decimation and YUV420 - Move QX3 detection from cpia_usb.c to cpia.c - New defaults for y_threshold, uv_threshold, target_framerate, and target_quality from windows driver From scottf@scs.unr.edu Mon, 8 May 2000 09:48:31 -0700 (PDT) Date: Mon, 8 May 2000 09:48:31 -0700 (PDT) From: Scott. scottf@scs.unr.edu Subject: [cpia] Vision File Format Hello everyone! My name is Scott Fritzinger, a developer for the gPhoto project (http://www.gphoto.org). I am currently adding Barbie/HotWheels/WWF camera support to gPhoto and would like to see if anyone knows the image file format? i'm not sure if the file format is the same between the still cameras and the full-motion CPia cameras. I know the barbie camera CAN run in full-motion video mode (but that requires a vid-capture card), so there might be some relation. In the barbie cameras, the picture size is denoted by: N1 = number of columns in the image N2 = number of black lines N3 = number of visible lines N4 = number of status bytes Number of data bytes = N1 * (N2 + N3) + N4 is this anything similar to the CPia image format? or other related projects? any help would be greatly appreciated. Please CC: me as i am not on the list. Thank you! ====---- - - - - - - - - - Scott Fritzinger New .sig coming soon! From zaitcev@metabyte.com Mon, 8 May 2000 10:51:54 -0700 (PDT) Date: Mon, 8 May 2000 10:51:54 -0700 (PDT) From: Pete Zaitcev zaitcev@metabyte.com Subject: [cpia] Vision File Format Scott, your timing seems to be a perfect match for mine as I finally got around to poke my barbiecam. I meant to do it since Itai's era :) > Date: Mon, 8 May 2000 09:48:31 -0700 (PDT) > From: "Scott." > I am currently adding Barbie/HotWheels/WWF camera support to gPhoto and > would like to see if anyone knows the image file format? [...] scicomms.doc mentions VVL330, for which there is no datasheet on Vision website. It seems that we can reuse a datasheet for VV6300 which is probably exactly the same thing. Jeff Laing have sent me his code for Mac, which is not GPL-ed, but he explicitly permitted me to examine it for the purpose of redoing (I hope I understood him right). I did not look at it yet, but supposedly it does the job. Vision used to have posted some code fragments too under GPL, on their website, but now I cannot find them. The website seems to be convoluted somewhat. Get them from http://corp.metabyte.com/zaitcev/~linux/bcam/decode.zip Yesterday I finished my "evk lores" tool that talks to the camera and was just going to look into the image format. Other thing that needs work is a setup of the camera wrt. lighting conditions, etc. Please keep me posted, --Pete cc: to cpia list and to jeff From scottf@scs.unr.edu Mon, 8 May 2000 12:34:17 -0700 (PDT) Date: Mon, 8 May 2000 12:34:17 -0700 (PDT) From: Scott. scottf@scs.unr.edu Subject: [cpia] Vision File Format On Mon, 8 May 2000, Pete Zaitcev wrote: > > I am currently adding Barbie/HotWheels/WWF camera support to gPhoto and > > would like to see if anyone knows the image file format? [...] > scicomms.doc mentions VVL330, for which there is no datasheet on > Vision website. It seems that we can reuse a datasheet for VV6300 > which is probably exactly the same thing. hmmmmmm. i'll check that out. i found the decode.zip off the CPia site, but haven't had a chance to rummage through it yet. > Jeff Laing have sent me his code for Mac, > which is not GPL-ed, but he explicitly permitted me to examine it > for the purpose of redoing (I hope I understood him right). > I did not look at it yet, but supposedly it does the job. that sounds good. since Jeff got a copy of this email, i'll wait for his response :) > Vision used to have posted some code fragments too under GPL, > on their website, but now I cannot find them. > The website seems to be convoluted somewhat. > Get them from http://corp.metabyte.com/zaitcev/~linux/bcam/decode.zip yeah, that site is dead. > Yesterday I finished my "evk lores" tool that talks to the camera > and was just going to look into the image format. Other thing that > needs work is a setup of the camera wrt. lighting conditions, etc. i have the camera working completely under gPhoto (taking pictures, transferring images, etc...) but i just need to convert the image format to something know :P then the library gets committed to CVS and the barbie cam is supported :) > cc: to cpia list and to jeff ditto. ====---- - - - - - - - - - Scott Fritzinger New .sig coming soon! From nikom@merl.com Mon, 08 May 2000 16:14:28 -0400 Date: Mon, 08 May 2000 16:14:28 -0400 From: Jacob Nikom nikom@merl.com Subject: [cpia] Do you know other applications using usb WebCamII? Hi Kali, Thank you very much for your help. I was able to fix the problem in the code and now the program communicates with the camera and saves the images in .ppm format. Also, it became shorter. I got rid of duplicate operations and unnecessary include files, trying to get it simpler and shorter (currently it has less than 100 lines): //===== start of the file v4lgrab.c ===== #include #include #include #include #include #include #define IMAGE_DEPTH 24 #define IMAGE_WIDTH 352 #define IMAGE_HEIGHT 288 #define IMAGE_SIZE (IMAGE_HEIGHT*IMAGE_WIDTH) * (IMAGE_DEPTH/8) struct video_window vid_win; struct video_picture vid_pic; struct video_capability vid_caps; int main() { unsigned char buffer[IMAGE_SIZE]; char header[100]; int read_size; int dev, out_raw, write_raw_size; int out_ppm, write_ppm_size, write_ppm_header; if ((dev = open ("/dev/video", O_RDWR)) < 0) { perror("/dev/video"); exit(1); } vid_pic.palette = VIDEO_PALETTE_RGB24; // from videodev.h vid_pic.depth = IMAGE_DEPTH; if (ioctl (dev, VIDIOCSPICT, &vid_pic)) { perror("wrong palette/depth"); exit( 1 ); } vid_win.x = 0; vid_win.y = 0; vid_win.width = IMAGE_WIDTH; vid_win.height = IMAGE_HEIGHT; if (ioctl (dev, VIDIOCSWIN, &vid_win) == -1) { perror ("ioctl (VIDIOCSWIN)"); exit( 1 ); } errno = 0; if ((read_size = read(dev, buffer, IMAGE_SIZE)) <= 0 ) { if (errno != 0 && errno != EINTR) { perror("Error read image\n"); exit( 1 ); } } // closing the video device close(dev); // create output file for .ppm format if ((out_ppm = open("outfile.ppm", O_WRONLY | O_CREAT, 0644)) == -1) { fprintf( stderr, "open outfile.ppm failed: %d\n", errno ); exit( 1 ); } // create .ppm header sprintf( header, "P6\n%d %d\n%d\n", vid_win.width, vid_win.height, 255); /* Write .ppm header to file */ if ((write_ppm_header = write(out_ppm, header, strlen(header))) < 0) { fprintf( stderr, "write outfile.raw header failed: %d\n", errno ); exit( 1 ); } // write the image data to the .ppm file if ((write_ppm_size = write(out_ppm, buffer, read_size)) < 0) { fprintf( stderr, "write outfile.ppm failed: %d\n", errno ); exit( 1 ); } printf("write into file outfile.ppm : %d\n", write_ppm_size ); // closing output .ppm file close(out_ppm); } // ==== end of the file v4lgrab.c ==== Do you think it could be simplify further? Regards, Jacob Nikom Kali Griffin wrote: > > How did you change it to make it produce a ppm file? > > It produces RGB or BGR based on your hardware. > > To change the RGB file to a ppm file you must run > a program called: rawtoppm > > usage: > > rawtoppm 352 288 output.raw > outty.ppm > > The 352 and 288 are the image's width and height. > > -kali > > On Fri, 5 May 2000, Jacob Nikom wrote: > > > Hi Kali, > > > > Thank you very much for your program. I tried to use it > > (I called it v4lcap.c). I was able to compile and run it > > successfully, however I got strange output. > > > > First, I changed it to produce .ppm file which I could > > view using "display" or "xv". It produced the file, but > > strange one. It looks like it is the output from interlaced > > camera with only one field captured. > > > > I changed it to use writeRGBStream routine, but it > > did not change anything. I attached this image file > > converted to .gif format which I compared visually with > > my .ppm file (they looked identically). > > > > I know my .ppm subroutine works correctly, so something > > different should be with capture. Do you have such an > > experience? Do you know what should I change to get > > the correct image? > > > > Thank you very much, > > > > Jacob Nikom > > > > Here my attachment - output.gif file > > > > Kali Griffin wrote: > > > > > > here is a simple little program that outputs RGB. Based on your > > > hardware it may output BGR. Youll know when you look at the picture. > > > > > > If you do get BGR, then you can replace the write() call with the > > > function writeRGBStream() that I included and that will do the > > > write()'s correctly. > > > > > > To convert it to a ppm use the program rawtoppm. It should come with > > > your linux distribution. If you need help with this part, then let me > > > know. > > > > > > Then to view, look at the ppm file in the gimp or something. if the color > > > is screwed up, then youre gettin BGR. Have fun. > > > > > > -kali > > > > > > On Fri, 5 May 2000, Jacob Nikom wrote: > > > > > > > Yes Kali, > > > > > > > > I think gqcam uses video4linux interface and I want to use it. > > > > If you could provide the code of your short example, I would > > > > appreciate it very much. > > > > > > > > Thank you, > > > > > > > > Jacob Nikom > > > > > > > > > > > > > > > > Kali Griffin wrote: > > > > > > > > > > do you want one using the video4linux interface? if so, I have > > > > > a very short program that does this, it serves as a good example. > > > > > -kali > > > > > > > > > > On Thu, 4 May 2000, Jacob Nikom wrote: > > > > > > > > > > > Hi, > > > > > > > > > > > > I was able to install WebCamII on 2.3.99-pre5. The application, > > > > > > gqcam runs now very well. Do you know other, simplier applcations > > > > > > than gqcam (without so much GUI) which also use WebCamII? > > > > > > > > > > > > For example, simple one which takes one frame and saves it in .ppm. > > > > > > > > > > > > Thank you, > > > > > > > > > > > > Jacob > > > > > > > > > > > > _______________________________________________ > > > > > > cpia mailing list - cpia@risc.uni-linz.ac.at > > > > > > http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia > > > > > > > > > > > > > > > > ------------------------------------------------------------------------ > > > /* > > > Simple Video For Linux Capture Application > > > Author: Kali Griffin > > > > > > */ > > > > > > #include > > > > > > #include > > > #include > > > #include > > > #include > > > #include > > > #include > > > > > > #define DEVICE_NAME "/dev/video" > > > #define IMAGE_DEPTH 24 > > > > > > #define IMAGE_WIDTH 352 > > > #define IMAGE_HEIGHT 288 > > > /* 176x144 QCIF > > > 352x288 CIF */ > > > > > > #define IMAGE_PIXEL_FORMAT VIDEO_PALETTE_RGB24 > > > /* > > > Formats: > > > VIDEO_PALETTE_GREY 1 Linear greyscale > > > VIDEO_PALETTE_HI240 2 High 240 cube (BT848) > > > VIDEO_PALETTE_RGB565 3 565 16 bit RGB > > > VIDEO_PALETTE_RGB24 4 24bit RGB > > > VIDEO_PALETTE_RGB32 5 32bit RGB > > > VIDEO_PALETTE_RGB555 6 555 15bit RGB > > > VIDEO_PALETTE_YUV422 7 YUV422 capture > > > VIDEO_PALETTE_YUYV 8 > > > VIDEO_PALETTE_UYVY 9 The great thing about standards is ... > > > VIDEO_PALETTE_YUV420 10 > > > VIDEO_PALETTE_YUV411 11 YUV411 capture > > > VIDEO_PALETTE_RAW 12 RAW capture (BT848) > > > VIDEO_PALETTE_YUV422P 13 YUV 4:2:2 Planar > > > VIDEO_PALETTE_YUV411P 14 YUV 4:1:1 Planar > > > VIDEO_PALETTE_YUV420P 15 YUV 4:2:0 Planar > > > VIDEO_PALETTE_YUV410P 16 YUV 4:1:0 Planar > > > VIDEO_PALETTE_PLANAR 13 start of planar entries > > > VIDEO_PALETTE_COMPONENT 7 start of component entries > > > */ > > > > > > int setWindowParams(int fd) { > > > > > > struct video_window winny; > > > > > > if (ioctl (fd, VIDIOCGWIN, &winny) == -1) { > > > printf("error getting window params.\n"); > > > return -1; > > > } > > > > > > winny.width = IMAGE_WIDTH; > > > winny.height = IMAGE_HEIGHT; > > > > > > if (ioctl (fd, VIDIOCSWIN, &winny) == -1) { > > > printf("error setting window params.\n"); > > > return -1; > > > } > > > > > > return 0; > > > } > > > > > > int setImageParams(int fd) { > > > > > > struct video_picture image; > > > > > > if (ioctl (fd, VIDIOCGPICT, &image) == -1) { > > > printf("error getting picture params.\n"); > > > return -1; > > > } > > > > > > image.depth = IMAGE_DEPTH; > > > image.palette = IMAGE_PIXEL_FORMAT; > > > > > > if (ioctl (fd, VIDIOCSPICT, &image) == -1) { > > > printf("error setting picture params.\n"); > > > return -1; > > > } > > > > > > return 0; > > > } > > > > > > /* > > > I have to do this sometimes because sometimes I > > > get BGR byte ordering instead of RGB > > > */ > > > void writeRGBStream(int fd, char *buffer, int size){ > > > int i; > > > char *rgbBuf; > > > rgbBuf = (char *)malloc (size); > > > > > > for (i = 0; i < size; i+=3) { > > > rgbBuf[i] = buffer[i+2]; > > > rgbBuf[i+1] = buffer[i+1]; > > > rgbBuf[i+2] = buffer[i]; > > > } > > > write (fd, rgbBuf, size); > > > } > > > > > > void signal_handler(int err){ > > > printf("caught sigalarm, bye\n"); > > > exit(0); > > > } > > > > > > int main() { > > > int vidfd, outfd; > > > int size; > > > int captureMode; > > > char *buffer; > > > int readLength; > > > char *outputFile = "output.raw"; > > > > > > signal(SIGALRM, signal_handler); > > > > > > size = (IMAGE_HEIGHT*IMAGE_WIDTH) * (IMAGE_DEPTH/8); > > > > > > if ((vidfd = open (DEVICE_NAME, O_RDONLY)) == -1) { > > > printf("error opening %s\n",DEVICE_NAME); > > > exit(0); > > > } > > > printf("opened device\n"); > > > > > > > > > if (setWindowParams(vidfd) == -1) { > > > printf("error in setWindowParams()\n"); > > > } > > > > > > if (setImageParams(vidfd) == -1) { > > > printf("error in setImageParams()\n"); > > > } > > > > > > buffer = (char *)malloc(size); > > > > > > if ((outfd = open (outputFile, O_WRONLY | O_CREAT)) == -1) { > > > printf("Error opening output file\n"); > > > exit(0); > > > } > > > > > > readLength = read (vidfd, buffer, size); > > > printf("read one frame of %d bytes\n", readLength); > > > > > > write(outfd, buffer, readLength); > > > > > > close(vidfd); > > > close(outfd); > > > chmod(outputFile, 0600); > > > > > > } From piero.campanelli@galactica.it Mon, 08 May 2000 22:34:14 +0200 Date: Mon, 08 May 2000 22:34:14 +0200 From: Piero Campanelli piero.campanelli@galactica.it Subject: [cpia] Webcam II and kernel 2.2 Hi. Is there anyone that has tested the backport of USB stack to kernel 2.2 ??? Does it work with CPIA ? Bye From jerdfelt@valinux.com Mon, 8 May 2000 16:52:07 -0400 Date: Mon, 8 May 2000 16:52:07 -0400 From: Johannes Erdfelt jerdfelt@valinux.com Subject: [cpia] Webcam II and kernel 2.2 On Mon, May 08, 2000, Piero Campanelli wrote: > > Is there anyone that has tested the backport of USB stack to kernel 2.2 ??? > Does it work with CPIA ? Absolutely. Just make sure you have the semaphore deadlock fix, but it seems to work very well for me and the other people here. JE From jeffl@SPATIALinfo.com Tue, 9 May 2000 08:49:59 +1000 Date: Tue, 9 May 2000 08:49:59 +1000 From: Jeff Laing jeffl@SPATIALinfo.com Subject: [cpia] Vision File Format > i have the camera working completely under gPhoto (taking pictures, > transferring images, etc...) but i just need to convert the image format > to something know :P then the library gets committed to CVS and the barbie > cam is supported :) I don't know how much you already know about the camera image format so here's a brain-dump of all I know currently. First, my camera seems to be using the horizontal shuffle mode so you need to unshuffle the pixels on each row. ie, the pixels returned by the camera are actually numbered <00><02><04><06>......<01><03><05>..... My loop to unshuffle them is in evk2.c, as I recall. The second thing to consider is that the doc on the VV6300 suggests that the CCD array looks like: GRGRGRGR BGBGBGBG GRgRGRGR but the actual image starts at an "R", not a "G". Also, watch the PDF's use of "odd" and "even". At times, it suggests the ODD columns are 0,2,4,... So, the raw camera data is more like: RRRRRR.....GGGGG... GGGGGG.....BBBBB... The shuffled data is therefore .......... .......... ... Getting this unshuffled was my first step in getting an image on-screen. Colors were all shot to hell but all I did was set a GRAY at the same intensity as the color for any given pixel. (ie, put the pixel value into all of R, G and B) I improved this by using the "lum=22%R + 71%G + 7%B" (from memory!) For quite a while, I had a bad horizontal banding problem where the image was in bunches of four rows, where the third and fourth row were noticably darker than the first two. This turned out to be caused by (a) a bad unshuffle (b) thinking that the image data started with "G" instead of "R". Now, the next problem is trying to work out what RGB values to use in each pixel space, and this is the area where the image processing stuff comes in. My first guess was to shift the image left and down by half-a-pixel. ie, for each pixel in the result image, I apply some algorithm to the values that are immediately NW, SW, NE and SE of it. For, image(0,0) is the result of processing red(0,0), green(0,1), green(1,0) and blue(1,1). There are four possibly permutations you have to deal with in this approach: RG GR GB BG GB BG RG GR My approach was to just take the Red and Blue values verbatim and average the Green values. Not a brilliant image. My next thought was to just treat each of the colors seperately. If you look at the red CCD array, it must look something like: R.R.R.R.R.R.R.R.. ................. R.R.R.R.R.R.R.R.. ::::::::::::::: I thought that it was probably reasonable to assume linear averaging down the image, so I populated those values first: R.R.R.R.R.R.R.R.. r.r.r.r.r.r.r.r.. R.R.R.R.R.R.R.R.. ::::::::::::::: then assume linear averaging across the image as well gives: RrRrRrRrRrRrRrR.. rrrrrrrrrrrrrrr.. RrRrRrRrRrRrRrR.. ::::::::::::::: then just treat construct image(0,0) from red(0,0), green(0,0), blue(0,0) The blue array is slightly different (ie, its offset +1,+1) but can use the same approach. The green array is better populated: .G.G.G.G.G.G.G... G.G.G.G.G.G.G.... .G.G.G.G.G.G.G... :::::::::::::: I think, at this point, I have tried a couple of different approaches, trying to average the four surrounding cells for each hole. My main problem at this point is that I get a "ghosting" effect, about six or so pixels across where it looks like the Red is being offset from the Blue, for some reason. No idea why. Henry has hinted: > You'll get some help from "A technical introduction to digital video" by > Charles A Poynton, page 177, Equation 9.10. Now, I don't have a copy, but from browsing the online table of contents at http://www.inforamp.net/~poynton/notes/TIDV/TIDV_toc.html it's possible it's something to do with converting between Y'CbCr and RGB. I'm assuming that perhaps the camera isn't returning RGB at all, although the datasheet says otherwise. Instead, perhaps its returning YCbCr. Alternately, you might need to massage the R,G,G,B quad into a YCbCr value, then convert it back to RGB space. Anyway, thats all I have for now, Jeff Laing ------------------------------------------------------------------ I got a lot of ideas. Trouble is, most of them suck. ---George Carlin From pcampanelli@acm.org Wed, 10 May 2000 01:37:12 +0200 Date: Wed, 10 May 2000 01:37:12 +0200 From: Piero Campanelli pcampanelli@acm.org Subject: [cpia] WEbcam II and vidcat patch Hi. I have downgraded my kernel from 2.3.99 to 2.2.15 and i have applied path for usb on 2.2 and installed cpia-1.0 ! It works well....however sometimes cam goed down (it doesn't crash). So if I do a vidcap i receive: Can't open /dev/video. Plugging and unplugging it returns working !!! I have done a dmesg and I read something similato to: CAM goes to lower state. Anyway it works well !! I need a fix for the problem of auto exposure. Have you any fix for vidcat ? (or any other similar software ?) Thank you ... Byeee From pcampanelli@acm.org Wed, 10 May 2000 19:20:30 +0200 Date: Wed, 10 May 2000 19:20:30 +0200 From: Piero Campanelli pcampanelli@acm.org Subject: [cpia] CAM crash debug WEBCAM II Creative USB Via Chipset Athlon Redhat 6.2 with kernel 2.2.15 + backport USB cpia 1.0 Problem: Sometimes cam goes down and vidcat returns "Can't open video device". Temporaney FIX: Plug/Unplug webcam connector DMESG Output: cpia.c(2882922):goto_low_power(2648):c0 02 d8 c2 60 cb b9 c0 VFS: Disk change detected on device ide1(22,64) cpia.c(2883023):goto_low_power(2648):80 04 d8 c2 60 cb b9 c0 cpia.c(2883125):goto_low_power(2648):c0 02 d8 c2 60 cb b9 c0 VFS: Disk change detected on device ide1(22,64) cpia.c(2883227):goto_low_power(2648):80 04 d8 c2 60 cb b9 c0 cpia.c(2883329):goto_low_power(2648):c0 02 d8 c2 60 cb b9 c0 Byeee From randy.dunlap@intel.com Fri, 12 May 2000 16:51:14 -0700 Date: Fri, 12 May 2000 16:51:14 -0700 From: Randy Dunlap randy.dunlap@intel.com Subject: [cpia] [patch] cpia_usb.c for 2.3.99-pre8 This is a multi-part message in MIME format. --------------A4C208E580129D8B8D05690D Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, I'd like to propose this patch to cpia_usb.c for 2.3.99-pre8. It corrects one printk() string and makes cpia_usb_open() honor error returns from usb_submit_urb(). This is important for USB bandwidth allocation/management. Thanks, Randy -- ___________________________________________________ |Randy Dunlap Intel Corp., DAL Sr. SW Engr.| |randy.dunlap.at.intel.com 503-696-2055| |NOTE: Any views presented here are mine alone | |and may not represent the views of my employer. | |_________________________________________________| --------------A4C208E580129D8B8D05690D Content-Type: text/plain; charset=us-ascii; name="cpia_usb.diff" Content-Disposition: inline; filename="cpia_usb.diff" Content-Transfer-Encoding: 7bit --- cpia_usb.c.org Thu Mar 30 18:00:01 2000 +++ cpia_usb.c Thu May 11 17:20:53 2000 @@ -186,7 +186,7 @@ if (ret < 0) { printk(KERN_ERR "cpia_usb_open: usb_set_interface error (ret = %d)\n", ret); retval = -EBUSY; - goto error_all; + goto error_1; } ucpia->buffers[0]->status = FRAME_EMPTY; @@ -203,7 +203,7 @@ if (!urb) { printk(KERN_ERR "cpia_init_isoc: usb_alloc_urb 0\n"); retval = -ENOMEM; - goto error_all; + goto error_1; } ucpia->sbuf[0].urb = urb; @@ -222,9 +222,9 @@ urb = usb_alloc_urb(FRAMES_PER_DESC); if (!urb) { - printk(KERN_ERR "cpia_init_isoc: usb_alloc_urb 0\n"); + printk(KERN_ERR "cpia_init_isoc: usb_alloc_urb 1\n"); retval = -ENOMEM; - goto error_all; + goto error_urb0; } ucpia->sbuf[1].urb = urb; @@ -245,20 +245,30 @@ ucpia->sbuf[0].urb->next = ucpia->sbuf[1].urb; err = usb_submit_urb(ucpia->sbuf[0].urb); - if (err) + if (err) { printk(KERN_ERR "cpia_init_isoc: usb_submit_urb 0 ret %d\n", err); + goto error_urb1; + } err = usb_submit_urb(ucpia->sbuf[1].urb); - if (err) + if (err) { printk(KERN_ERR "cpia_init_isoc: usb_submit_urb 1 ret %d\n", err); + goto error_urb1; + } ucpia->streaming = 1; ucpia->open = 1; return 0; -error_all: +error_urb1: /* free urb 1 */ + usb_free_urb(ucpia->sbuf[1].urb); + +error_urb0: /* free urb 0 */ + usb_free_urb(ucpia->sbuf[0].urb); + +error_1: kfree (ucpia->sbuf[1].data); error_0: kfree (ucpia->sbuf[0].data); --------------A4C208E580129D8B8D05690D-- From cloud@chool.com Sun, 14 May 2000 16:37:43 -0500 (CDT) Date: Sun, 14 May 2000 16:37:43 -0500 (CDT) From: Sam Reynolds cloud@chool.com Subject: [cpia] Parallel Webcam II + 2.2.15 troubles Hi, I am very new to this list and am trying to get my Creative Webcam 2 (parallel version) to work with 2.2.15. I read the kernel documentation and chose to go the "linked in" route. I also made the video device like it said and appended the address, DMA, and IRQ in my lilo.conf. The first time it told me that my port was not ECP compatable so i changed it to ECP in my bios. Now it tells me: <--snip--> Linux video capture interface: v1.00 V4L-Driver for Vision CPiA based cameras v0.5.0 Parallel port driver for Vision CPiA based cameras v0.5.0 cpia_pp.c:cpia_pp_register(1307):failed to cpia_register_camera 0 camera(s) found <--snip--> I tried to peruse the archives to see if this had been brought up before but was unable to find any messages regarding it. Thank you in advance for your help :) Sam Reynolds From deepak@csociety.purdue.edu Mon, 15 May 2000 14:20:49 -0500 Date: Mon, 15 May 2000 14:20:49 -0500 From: Deepak Saxena deepak@csociety.purdue.edu Subject: [cpia] CPIA && RealProducer Has anyone working with the CPIA driver + Ezonics EZCam had any luck getting RealProducer to capture video? I get messages telling me that VIDIOCMCAPTURE failed, and if turne on debugging on the driver, it looks like it's not getting data from the camera. However, gqcam works ok. I'll post another message later with the driver debug log when I have access to the test system. ~ Deepak -- Deepak Saxena - deepak@csociety.purdue.edu Home://480.820.4722 Mobile://602.790.0500 "Computers are useless, they can only give you answers" - Picasso From jerdfelt@sventech.com Tue, 16 May 2000 13:03:12 -0400 Date: Tue, 16 May 2000 13:03:12 -0400 From: Johannes Erdfelt jerdfelt@sventech.com Subject: [cpia] Re: CPiA problem? On Tue, May 16, 2000, Chris Jones wrote: > I just tried out 2.3.99-pre8 on my 2xCeleron 433 ABit BP6 machine (256MB > RAM). I decided to stress test it a bit so I left xawtv running on the > webcam /dev/video entry, an mpeg playing and an mp3 playing overnight. > From the point of the cpia module being loaded at 06:56am (i was using your > alternative usb stack - the main one just hung my machine) I had xawtv > reading the webcam pretty much continuously and the last entry in my > /var/log/messages is at 13:29pm so it managed to go quite a while, but after > that the system was very unstable - I managed to issue some SysRq commands, > but it hung and corrupted the video display before I could finish. > > I've looked through the logs and I can't find any oopsen so I guess this may > be hard to track down, but I've put some of the more important bits of the > log below (let me know if you need anymore). > > On a slightly different note - using xawtv to view th webcam I could only > take 2 jpeg snapshots with it before it would exit when trying to take > another - is this a CPiA problem or an xawtv problem? It's hard to tell who's problem it is. There is a bug in the CPiA code wrt to getting a number of corrupted frames in a short time apparentely. One of my coworkers showed me his machine which has the CPiA camera stuck with a bunch of error messages parsing the compressed frame. I haven't been able to duplicate the problem quite yet. These may be related. > This is me loading your alternative usb stack: > May 16 06:55:58 bitch kernel: usb.c: registered new driver hub > May 16 06:55:58 bitch kernel: uhci.c: USB UHCI at I/O 0xc000, IRQ 19 > May 16 06:55:58 bitch kernel: uhci.c: detected 2 ports > May 16 06:55:58 bitch kernel: usb.c: new USB bus registered, assigned bus > number 1 > May 16 06:55:58 bitch kernel: usb.c: USB new device connect, assigned device > number 1 > May 16 06:55:58 bitch kernel: hub.c: USB hub found > May 16 06:55:58 bitch kernel: hub.c: 2 ports detected > May 16 06:56:00 bitch kernel: usb.c: USB new device connect, assigned device > number 2 > May 16 06:56:00 bitch kernel: usb.c: This device is not recognized by any > installed USB driver. Looks good. > This is me loading the CPiA module > May 16 06:56:12 bitch kernel: Linux video capture interface: v1.00 > May 16 06:56:12 bitch kernel: V4L-Driver for Vision CPiA based cameras > v0.7.4 > May 16 06:56:12 bitch kernel: usb.c: registered new driver cpia > May 16 06:56:12 bitch kernel: USB CPiA camera found > May 16 06:56:12 bitch kernel: CPiA Version: 1.20 (2.0) > May 16 06:56:12 bitch kernel: CPiA PnP-ID: 0553:0002:0100 > May 16 06:56:12 bitch kernel: VP-Version: 1.0 0100 Looks good. > There were an awful lot of these (I have heard this is an ABit BP6 problem?) > May 16 07:52:44 bitch kernel: APIC error interrupt on CPU#0, should never > happen. > May 16 07:52:44 bitch kernel: ... APIC ESR0: 00000000 > May 16 07:52:44 bitch kernel: ... APIC ESR1: 00000004 > May 16 07:52:44 bitch kernel: ... bit 2: APIC Send Accept Error. > May 16 07:59:14 bitch kernel: usb_control/bulk_msg: timeout > May 16 08:05:56 bitch kernel: APIC error interrupt on CPU#1, should never > happen. > May 16 08:05:56 bitch kernel: ... APIC ESR0: 00000000 > May 16 08:05:56 bitch kernel: ... APIC ESR1: 00000002 > May 16 08:05:56 bitch kernel: ... bit 1: APIC Receive CS Error (hw problem). Looks very bad. This could be a cause of some of the problem you were seeing. I'm pretty confident that we (USB or CPiA) didn't cause this problem. > This was the final log entry before the machine froze. > May 16 13:29:39 bitch kernel: usb_control/bulk_msg: timeout Quite a while before this happened. Were there any other USB/UHCI related messages? If not, then there is a couple of possibilities. The camera could be continuously NAKing the control transfer which is unlikely but possible. Or the Host Controller could have locked up, but it usually tells us something really bad happened with an interrupt. There could be some sort of problem with the APIC. What is definately a possibility given those errors you see above. Have you sent a message to linux-kernel yet about the APIC problem? JE From chris@black-sun.co.uk Wed, 17 May 2000 05:33:00 +0100 Date: Wed, 17 May 2000 05:33:00 +0100 From: Chris Jones chris@black-sun.co.uk Subject: [cpia] Re: CPiA problem? Hi Johannes Erdfelt wrote: > > I haven't been able to duplicate the problem quite yet. These may be > related. I'll try and leave it running overnight again today - it's a little tricky though because my box is providing network access for my house LAN and so having it crashed while I'm asleep isn't much use! > This could be a cause of some of the problem you were seeing. I'm pretty > confident that we (USB or CPiA) didn't cause this problem. It's definitely not a USB or CPiA caused problem, but I thought I'd include it for completeness as maybe it triggered the problem. It's something that was reported on lkml a while back and appears to be specific to the BP6. As far as I followed the discussion it seemed that this is not actually a problem, it's just a wierdness. The errors occur on 2.2 as well, they're just not actually reported by the kernel. > Quite a while before this happened. Were there any other USB/UHCI related > messages? Nope, the stuff I included in the original mail was the only kernel messages related to USB or CPiA (and the APIC stuff). -- _____ _ _ _____ | __ | |___ ___| |_ ___| __|_ _ ___ Chris "Ng" Jones | __ -| | .'| _| '_|___|__ | | | | chris@black-sun.co.uk |_____|_|__,|___|_,_| |_____|___|_|_| www.black-sun.co.uk S o f t w a r e From csb@psouth.net Thu, 18 May 2000 20:59:00 -0400 Date: Thu, 18 May 2000 20:59:00 -0400 From: C. Bradford csb@psouth.net Subject: [cpia] cpia_usb.o I'm running the 2.2.14 kernel with the 2.3.xx backport for the usb-drivers... all drivers are fine except for cpia_usb.o... all can be loaded without problems! I can't get cpia_usb.o to compile!! It always exits out with about 2 million error messages (I've honestly never seen this many!)... is there anything obvious that I'm missing in order to get it to go? Regards --Chris Bradford From jerdfelt@sventech.com Thu, 18 May 2000 21:07:12 -0400 Date: Thu, 18 May 2000 21:07:12 -0400 From: Johannes Erdfelt jerdfelt@sventech.com Subject: [cpia] cpia_usb.o On Thu, May 18, 2000, C. Bradford wrote: > I'm running the 2.2.14 kernel with the 2.3.xx backport for the > usb-drivers... all drivers are fine except for cpia_usb.o... all can be > loaded without problems! > > I can't get cpia_usb.o to compile!! It always exits out with about 2 > million error messages (I've honestly never seen this many!)... is > there anything obvious that I'm missing in order to get it to go? Which cpia_usb.o are you trying to compile? JE From chrisb@network-systems.com Fri, 19 May 2000 09:33:37 -0400 Date: Fri, 19 May 2000 09:33:37 -0400 From: Christopher Bradford chrisb@network-systems.com Subject: [cpia] cpia data error? Hi everyone - I'm running a 2.2.14 kernel with the 2.3.xx backport usb drivers... I've also compiled the cpia1.0 drivers for usb... everything loads ok and the camera is detected... However, when I try to grab frames from the camera, dmesg is full of the following lines: cpia data error: [7] len=0, status=FFFFFFEE cpia_usb.c(3601576):cpia_usb_complete(147):Ignoring packet! cpia_usb.c(3601576):cpia_usb_complete(147):Ignoring packet! cpia_usb.c(3601576):cpia_usb_streamRead(385):Something went wrong! cpia.c(3601576):fetch_frame(2535):streamRead failed: -1 cpia.c(3601577):save_camera_state(2665):0/0/185/0/220/214/214/230 cpia.c(3601577):save_camera_state(2669):32/6/92 cpia data error: [0] len=0, status=FFFFFFEE cpia data error: [2] len=0, status=FFFFFFEE cpia data error: [4] len=0, status=FFFFFFEE cpia data error: [6] len=0, status=FFFFFFEE cpia data error: [8] len=0, status=FFFFFFEE cpia.c(3601578):goto_low_power(2645):camera now in LOW power state I'm also using someof the xawtv 3.14 utilites to try and grab frames, which fails.. I'm assuming it fails because of the above messages. However, perhaps the above messages are caused by xawtv? Doesn't seem likely... anybody have any ideas what causes the above errors? Also, what is a good framegrabbing utility that is known to work? Regards --Chris Bradford From jmbuena@dia.fi.upm.es Fri, 19 May 2000 16:46:16 +0200 Date: Fri, 19 May 2000 16:46:16 +0200 From: Jose Miguel Buenaposada Biencinto jmbuena@dia.fi.upm.es Subject: [cpia] CPIA 1.0 in 2.2.14 with USB 2.3.99-pre7 Backport 2.2.14 problems Hi, again ! I'm here again because nobody answered my other emails. So I hope there is a response this time, thank you anyway. I have read the usb mailing list archive and I have found people with the same problem than me. So I think is an interesting question than must be resolved (well, I'm very interested in it, of course ;) ). One person get a OV511 cam working with 2.2.14+2.3.99-pre7 USB backport in one computer and can not work in other computer getting: usb_control/bulk_msg: timeout messages so the cam is not recognized. Well, I have a similar problem but with a USB Zoom Cam. I have tried 2 versions of the backport (usb-2.3.99-pre7-1-for-2.2.14.diff.gz and usb-2.3.50-1-for-2.2.14.diff.gz) with kernels 2.2.14 and 2.2.15 with the same results (SMP kernel): May 19 16:13:22 hal kernel: V4L-Driver for Vision CPiA based cameras v1.0.0 May 19 16:13:22 hal insmod: /lib/modules/2.2.14/misc/cpia_usb.o: insmod cpia_usb failed May 19 16:13:22 hal kernel: usb.c: registered new driver cpia May 19 16:15:34 hal kernel: usb.c: USB new device connect, assigned device number 2 May 19 16:15:37 hal kernel: usb_control/bulk_msg: timeout May 19 16:15:49 hal last message repeated 4 times May 19 16:15:49 hal kernel: usb.c: USB device not responding, giving up (error=-110) May 19 16:16:14 hal kernel: usb.c: USB disconnect on device -1 May 19 16:16:17 hal kernel: usb.c: USB new device connect, assigned device number 2 May 19 16:16:20 hal kernel: usb_control/bulk_msg: timeout May 19 16:16:32 hal last message repeated 4 times May 19 16:16:32 hal kernel: usb.c: USB device not responding, giving up (error=-110) The USB subsystem is not able to contact with the cam, I think. Anyway, when I use the kernel 2.3.51 (SMP kernel) I can view my not very pretty face ;) in the screen. I can use it without problems. Well my intention is to debug the problem but I'm not a kernel hacker so I ask you for some help in what to do to find the problem , what can I do ? I need the cam working in 2.2.x kernels. Thaks you very much for any help. Here is some information: [root@hal usb]# cat /proc/version Linux version 2.2.14 (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #3 SMP Fri May 19 15:58:43 CEST 2000 [root@hal usb]# cat /proc/interrupts CPU0 CPU1 0: 102209 99257 IO-APIC-edge timer 1: 4660 4200 IO-APIC-edge keyboard 2: 0 0 XT-PIC cascade 4: 7856 8503 IO-APIC-edge serial 11: 0 0 IO-APIC-edge usb-uhci 13: 1 0 XT-PIC fpu 16: 40330 40465 IO-APIC-level aic7xxx, aic7xxx 17: 0 0 IO-APIC-level es1371 18: 15180 14840 IO-APIC-level eth0 NMI: 0 ERR: 0 [root@hal usb]# cat /proc/modules cpia_usb 4784 0 (unused) cpia 58064 0 [cpia_usb] usb-uhci 22304 0 (unused) usbcore 43592 0 [cpia_usb usb-uhci] videodev 2592 0 [cpia] es1371 27904 0 soundcore 2564 4 [es1371] [root@hal usb]# /sbin/lspci 00:00.0 Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge (rev 03) 00:01.0 PCI bridge: Intel Corporation 440BX/ZX - 82443BX/ZX AGP bridge (rev 03) 00:07.0 ISA bridge: Intel Corporation 82371AB PIIX4 ISA (rev 02) 00:07.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01) 00:07.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01) 00:07.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 02) 00:09.0 Multimedia audio controller: Ensoniq ES1371 (rev 08) 00:0a.0 Ethernet controller: 3Com Corporation: Unknown device 9200 (rev 74) 00:0c.0 SCSI storage controller: Adaptec 7896 00:0c.1 SCSI storage controller: Adaptec 7896 01:00.0 VGA compatible controller: Matrox Graphics, Inc.: Unknown device 0525 (rev 04) -- ------------------------------------------------------------------- Jose Miguel Buenaposada Biencinto Facultad de Informática | Computer Science School Universidad Politécnica de Madrid (UPM) | Madrid Tech. University. Campus de Montegancedo s/n 28660 Boadilla del Monte, Madrid (ESPAÑA)| (SPAIN) Voice +34 91 336 69 47 e-mail: jmbuena@dia.fi.upm.es web : http://www.dia.fi.upm.es/~jmbuena ------------------------------------------------------------------- From jerdfelt@sventech.com Fri, 19 May 2000 11:42:20 -0400 Date: Fri, 19 May 2000 11:42:20 -0400 From: Johannes Erdfelt jerdfelt@sventech.com Subject: [cpia] CPIA 1.0 in 2.2.14 with USB 2.3.99-pre7 Backport 2.2.14 problems On Fri, May 19, 2000, Jose Miguel Buenaposada Biencinto wrote: > I have read the usb mailing list archive and I have found people with > the same problem than me. So I think is an interesting question than must > be resolved (well, I'm very interested in it, of course ;) ). One person > get a OV511 cam working with 2.2.14+2.3.99-pre7 USB backport in one > computer and can not work in other computer getting: > > usb_control/bulk_msg: timeout messages so the cam is not > recognized. > > Well, I have a similar problem but with a USB Zoom Cam. I have tried 2 > versions of the backport (usb-2.3.99-pre7-1-for-2.2.14.diff.gz and > usb-2.3.50-1-for-2.2.14.diff.gz) with kernels 2.2.14 and 2.2.15 with the > same results (SMP kernel): > > May 19 16:13:22 hal kernel: V4L-Driver for Vision CPiA based cameras > v1.0.0 > May 19 16:13:22 hal insmod: /lib/modules/2.2.14/misc/cpia_usb.o: insmod > cpia_usb failed > May 19 16:13:22 hal kernel: usb.c: registered new driver cpia > May 19 16:15:34 hal kernel: usb.c: USB new device connect, assigned > device number 2 > May 19 16:15:37 hal kernel: usb_control/bulk_msg: timeout > May 19 16:15:49 hal last message repeated 4 times > May 19 16:15:49 hal kernel: usb.c: USB device not responding, giving up > (error=-110) > May 19 16:16:14 hal kernel: usb.c: USB disconnect on device -1 > May 19 16:16:17 hal kernel: usb.c: USB new device connect, assigned > device number 2 > May 19 16:16:20 hal kernel: usb_control/bulk_msg: timeout > May 19 16:16:32 hal last message repeated 4 times > May 19 16:16:32 hal kernel: usb.c: USB device not responding, giving up > (error=-110) > > The USB subsystem is not able to contact with the cam, I think. > > Anyway, when I use the kernel 2.3.51 (SMP kernel) I can view my not very > pretty face ;) in the screen. I can use it without problems. Well my > intention is to debug the problem but I'm not a kernel hacker so I ask > you for some help in what to do to find the problem, what can I do ? I > need the cam working in 2.2.x kernels. > > Thaks you very much for any help. > > [root@hal usb]# cat /proc/interrupts > CPU0 CPU1 > 11: 0 0 IO-APIC-edge usb-uhci This is your problem. Interrupts are not getting delivered. Unfortunately this is not a USB or CPiA problem. There's a couple of things you may want to try: - Look in the BIOS for a "MPS Version" setting. Set it to the opposite - Look in the BIOS for a "Assign USB Interrpt" setting. Set it to the opposite - Upgrade your BIOS - Send a message to linux-kernel or something similar. JE From jmbuena@dia.fi.upm.es Mon, 22 May 2000 13:59:33 +0200 Date: Mon, 22 May 2000 13:59:33 +0200 From: Jose Miguel Buenaposada Biencinto jmbuena@dia.fi.upm.es Subject: [cpia] CPIA 1.0 in 2.2.14 with USB 2.3.99-pre7 Backport 2.2.14problems Johannes Erdfelt wrote: > > > > [root@hal usb]# cat /proc/interrupts > > CPU0 CPU1 > > 11: 0 0 IO-APIC-edge usb-uhci > > This is your problem. Interrupts are not getting delivered. > Unfortunately this is not a USB or CPiA problem. > > There's a couple of things you may want to try: > - Look in the BIOS for a "MPS Version" setting. Set it to the opposite Yes, that's the rigth answer. I had set in the BIOS "SMP version 1.4" and I have set it to 1.1. It is working now. I have 2.2.14 kernel version patched with 2.3.99-pre7-1 USB backport. But what I don't understand is, why it works with "SMP version 1.4" and kernel 2.3.99 ? I now there is a lot of changes but ... It's very nice when everything is working correctly. Thanks a lot for your help. I love Linux ;): [jmbuena@hal jmbuena]$ cat /proc/interrupts CPU0 CPU1 11: 2194 2075 IO-APIC-level usb-uhci ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -- ------------------------------------------------------------------- Jose Miguel Buenaposada Biencinto Facultad de Informática | Computer Science School Universidad Politécnica de Madrid (UPM) | Madrid Tech. University. Campus de Montegancedo s/n 28660 Boadilla del Monte, Madrid (ESPAÑA)| (SPAIN) Voice +34 91 336 69 47 e-mail: jmbuena@dia.fi.upm.es web : http://www.dia.fi.upm.es/~jmbuena ------------------------------------------------------------------- From claudio@conectiva.com Mon, 22 May 2000 12:34:19 -0300 (BRST) Date: Mon, 22 May 2000 12:34:19 -0300 (BRST) From: Claudio Matsuoka claudio@conectiva.com Subject: [cpia] Doubts... On Thu, 22 May 1997, Fabiano Reis wrote: > 1) What driver-module I need, and where is it over the Internet? > 2) What kernel-module I need, and what is the best kernel version to > make it work with? The recent 2.3.99-pre kernels ship with 0.7.4. You can get 1.0 and CVS snapshots at http://webcam.sourceforge.net. claudio From cloud@chool.com Tue, 23 May 2000 16:12:45 -0500 (CDT) Date: Tue, 23 May 2000 16:12:45 -0500 (CDT) From: Sam Reynolds cloud@chool.com Subject: [cpia] Parallel Webcam II + 2.2.15 troubles Didn't get any responses so I decided to repost in case someone had some new insight. Basically I haven't been able to fix the below problem yet and still can't seem to find any precidence for it. Any help is greatly appreciated -Sam Reynolds On Sun, 14 May 2000, Sam Reynolds wrote: > Hi, I am very new to this list and am trying to get my Creative Webcam 2 > (parallel version) to work with 2.2.15. I read the kernel documentation > and chose to go the "linked in" route. I also made the video device like > it said and appended the address, DMA, and IRQ in my lilo.conf. The first > time it told me that my port was not ECP compatable so i changed it to ECP > in my bios. Now it tells me: > <--snip--> > Linux video capture interface: v1.00 > V4L-Driver for Vision CPiA based cameras v0.5.0 > Parallel port driver for Vision CPiA based cameras v0.5.0 > cpia_pp.c:cpia_pp_register(1307):failed to cpia_register_camera > 0 camera(s) found > <--snip--> > > I tried to peruse the archives to see if this had been brought up before > but was unable to find any messages regarding it. Thank you in advance > for your help :) > Sam Reynolds > > > _______________________________________________ > cpia mailing list - cpia@risc.uni-linz.ac.at > http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia > From claudio@conectiva.com Tue, 23 May 2000 21:59:26 -0300 (BRT) Date: Tue, 23 May 2000 21:59:26 -0300 (BRT) From: Claudio Matsuoka claudio@conectiva.com Subject: [cpia] Parallel Webcam II + 2.2.15 troubles On Tue, 23 May 2000, Sam Reynolds wrote: > Hi, I am very new to this list and am trying to get my Creative Webcam 2 > (parallel version) to work with 2.2.15. I read the kernel documentation > and chose to go the "linked in" route. (...) > Parallel port driver for Vision CPiA based cameras v0.5.0 > cpia_pp.c:cpia_pp_register(1307):failed to cpia_register_camera I believe it would be a good idea to get a recent version of the CPiA driver (at http://webcam.sourceforge.net) and build it as a module (so the parameters could be easily changed reloading the module). Best regards, claudio From Peter_Pregler@email.com Wed, 24 May 2000 10:17:23 +0200 Date: Wed, 24 May 2000 10:17:23 +0200 From: Peter Pregler Peter_Pregler@email.com Subject: [cpia] Parallel Webcam II + 2.2.15 troubles On Tue, May 23, 2000 at 09:59:26PM -0300, Claudio Matsuoka wrote: > On Tue, 23 May 2000, Sam Reynolds wrote: > > > Hi, I am very new to this list and am trying to get my Creative Webcam 2 > > (parallel version) to work with 2.2.15. I read the kernel documentation > > and chose to go the "linked in" route. > (...) > > Parallel port driver for Vision CPiA based cameras v0.5.0 > > cpia_pp.c:cpia_pp_register(1307):failed to cpia_register_camera > > I believe it would be a good idea to get a recent version of the CPiA > driver (at http://webcam.sourceforge.net) and build it as a module > (so the parameters could be easily changed reloading the module). I try to make a reasonable patch for Alan so 2.2.16 goes out with a the latest version of the driver. -Peter -- I will not waste chalk. --Bart Simpson at the blackboard -------------------------------------------------------- Email: Peter_Pregler@email.com WWW: http://www.risc.uni-linz.ac.at/people/ppregler From cloud@chool.com Wed, 24 May 2000 22:41:54 -0500 (CDT) Date: Wed, 24 May 2000 22:41:54 -0500 (CDT) From: Sam Reynolds cloud@chool.com Subject: [cpia] Parallel Webcam II + 2.2.15 troubles That helped alot. Thanks. Now for my next problem :) I got 1.0 of the cpia module and when i insmod the cpia.o and cpia_pp.o it works like very well according to dmesg: <-snip-> V4L-Driver for Vision CPiA based cameras v1.0.0 Parallel port driver for Vision CPiA based cameras v1.0.0 using DMA mode (irq 7, DMA 3) cpia.c(1120454):goto_low_power(2645):camera now in LOW power state cpia.c(1120464):goto_high_power(2631):camera now in HIGH power state cpia.c(1120474):dispatch_commands(2350):1 1 0 0 1 1 1 1 cpia.c(1120474):dispatch_commands(2351):0 1 1 1 1 1 0 1 cpia.c(1120478):save_camera_state(2665):0/0/185/0/220/214/214/230 cpia.c(1120478):save_camera_state(2669):32/6/92 CPiA Version: 1.02 (1.0) CPiA PnP-ID: 0553:0001:0100 VP-Version: 1.0 0100 1 camera(s) found <-snip-> Everything looks great, now i compiled gqcam (the version that came with the module) and attempted to run it. I got "/dev/video: No such device". I had originally made my devices with /dev/MAKEDEV video but then I read the gqcam docs and just remade them all exactly as they said with still no luck. Any ideas are greatly appreciated (again) and i apoligize for my inconvience in advance. -Sam Reynolds On Tue, 23 May 2000, Claudio Matsuoka wrote: > On Tue, 23 May 2000, Sam Reynolds wrote: > > > Hi, I am very new to this list and am trying to get my Creative Webcam 2 > > (parallel version) to work with 2.2.15. I read the kernel documentation > > and chose to go the "linked in" route. > (...) > > Parallel port driver for Vision CPiA based cameras v0.5.0 > > cpia_pp.c:cpia_pp_register(1307):failed to cpia_register_camera > > I believe it would be a good idea to get a recent version of the CPiA > driver (at http://webcam.sourceforge.net) and build it as a module > (so the parameters could be easily changed reloading the module). > > Best regards, > claudio > > > From edd@usefulinc.com Thu, 25 May 2000 15:32:58 +0100 Date: Thu, 25 May 2000 15:32:58 +0100 From: Edd Dumbill edd@usefulinc.com Subject: [cpia] Microtek Eyestar 2 not working I seem to be having the same difficulties as mentioned in this mail: http://mailman.risc.uni-linz.ac.at/pipermail/cpia/2000-April/000667.html I include the output from dmesg below. I'm using IRQ 7, DMA 3 parport at 0x378. I'm using kernel version 2.2.13, Debian potato. Although it tells me that one camera is detected, it doesn't actually work. Trying to invoke gqcam gives '/dev/video: No such device' even though I've done the mknod etc. as specified in the gqcam INSTALL file. Any help would be much appreciated. thanks -- Edd Dumbill ----output from dmesg------ Parallel port driver for Vision CPiA based cameras v1.0.0 using DMA mode (irq 7, DMA 3) cpia_pp.c(49646):Negotiate2SetupPhase(362):Busy should be high at beginning cpia_pp.c(49679):my_wait_peripheral(327):failed 0x58 should be 0xd0 waited 33 jiffies cpia_pp.c(49679):Valid1284Termination(514):status bit did not go to the correct value cpia_pp.c(49679):Negotiate2SetupPhase(362):Busy should be high at beginning cpia_pp.c(49712):my_wait_peripheral(327):failed 0x58 should be 0xd0 waited 33 jiffies cpia_pp.c(49712):Valid1284Termination(514):status bit did not go to the correct value cpia_pp.c(49712):Negotiate2SetupPhase(362):Busy should be high at beginning cpia_pp.c(49745):my_wait_peripheral(327):failed 0x40 should be 0x0 waited 33 jiffies cpia_pp.c(49745):SimECPReadBuffer(540):nAck didn't went down after read 1 bytes no more data ? cpia_pp.c(49778):my_wait_peripheral(327):failed 0x58 should be 0xd0 waited 33 jiffies cpia_pp.c(49778):Valid1284Termination(514):status bit did not go to the correct value cpia.c(49778):do_command(1730):c003 - failed, retval=-5 1 camera(s) found From www-admin@pmail.net Sun, 28 May 2000 22:26:48 +0100 Date: Sun, 28 May 2000 22:26:48 +0100 From: Iostream www-admin@pmail.net Subject: [cpia] philips PCA635VC Parallel port? I got two of those baby´s and want to use them in linux. Does anybody know if it´s posseble to get it to work under my linux box or if I´m doom´d. I compiled my kernel 2.4.test1 with the things mention in the doc´s but my experience with v4l, webcams and cpia is very poor so I haven´t yet been able to even get /dev/video to respond. /Thanks Anders