From jylam@hangover.fr Wed, 01 Mar 2000 12:23:06 +0100 Date: Wed, 01 Mar 2000 12:23:06 +0100 From: jylam jylam@hangover.fr Subject: [cpia] mhh, you have to kill me Kill me if you think I'm boring :) I missed to say that my parallel port IS ECP (parport0: PC-style at 0x378 [SPP,ECP,ECPEPP,ECPPS2]),too. It whould be okay, now :) -- ,---------. ,------------------. |Jean-Yves \___/ Jylam@HangOver.fr | `---------------------^------------' Administrateur systeme Linux Hangover (http://www.hangover.fr) _______________________________________________ cpia mailing list - cpia@risc.uni-linz.ac.at http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia From jylam@hangover.fr Wed, 01 Mar 2000 12:20:46 +0100 Date: Wed, 01 Mar 2000 12:20:46 +0100 From: jylam jylam@hangover.fr Subject: [cpia] Oups Oups, sorry, I missed to say that I use a parallel version of Creative WebCamII, so don't talk to me about usb :) -- ,---------. ,------------------. |Jean-Yves \___/ Jylam@HangOver.fr | `---------------------^------------' Administrateur systeme Linux Hangover (http://www.hangover.fr) _______________________________________________ cpia mailing list - cpia@risc.uni-linz.ac.at http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia From jylam@hangover.fr Wed, 01 Mar 2000 12:18:39 +0100 Date: Wed, 01 Mar 2000 12:18:39 +0100 From: jylam jylam@hangover.fr Subject: [cpia] Device or resource busy Hi all. since 3-4 hours, I'm trying to make my Creative WebCamII working. But. Here is my lsmod: Module Size Used by parport_pc 5012 0 (autoclean) cpia 48476 0 parport_probe 2884 0 videodev 2400 0 [cpia] appletalk 17312 11 (autoclean) nfs 29944 1 (autoclean) lockd 30856 1 (autoclean) [nfs] sunrpc 52356 1 (autoclean) [nfs lockd] parport 7092 0 (autoclean) [parport_pc parport_probe] eepro100 12112 1 (autoclean) es1371 23212 0 soundcore 2372 4 [es1371] Everything is good, but cpia_pp. root@talisker: (bash) 1164 /home/racine/cpia-0.7.1/module > insmod cpia_pp.o cpia_pp.o: init_module: Device or resource busy here is my /var/log/messages Mar 1 12:16:17 talisker kernel: Parallel port driver for Vision CPiA based cameras v0.7.1 Mar 1 12:16:17 talisker kernel: 0 camera(s) found I tried the Patch posted the Fri, 11 Feb 2000 17:42:39, it don't work at all, it's the same result. So what's wrong ? is my MAKEDEV video wrong ? or anything ? Please help me, or I think I will eat a *big* dog :) Thanks -- ,---------. ,------------------. |Jean-Yves \___/ Jylam@HangOver.fr | `---------------------^------------' Administrateur systeme Linux Hangover (http://www.hangover.fr) _______________________________________________ cpia mailing list - cpia@risc.uni-linz.ac.at http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia From thunder@ultravision.net Tue, 29 Feb 2000 19:34:07 -0600 Date: Tue, 29 Feb 2000 19:34:07 -0600 From: Thunder thunder@ultravision.net Subject: [cpia] /dev/video hi all I have a Ezonics webcam and running 2.3.47 kernel with cpia-0.7.1. The problem I am incurring is that application xawtv or gqcam errors when ran with: open /dev/video no video grabber device available This doesnt happen all the time.. it's spaztic.. stops and starts on it's own.. I have not been able to control when it stops or when it decides to work again... I have not been able to pinpoint what is causing it, I have a site that streamer (a xawtv app.) pointed at my local webpage as a test and is supposed to take a clip every 30 seconds. But even if this function is disabled I have the same error.. My logs dont show anything out of the ordinary. Any clues or possible troubleshooting technics in this matter sure would be appreciated. Bill Espinosa From rprevidi@dsi.unive.it Wed, 1 Mar 2000 10:02:11 +0100 (CET) Date: Wed, 1 Mar 2000 10:02:11 +0100 (CET) From: Previdi Roberto rprevidi@dsi.unive.it Subject: [cpia] where can i find a faq? Hi, i'm sorry to disturb for such a silly thing: where can I find a faq with all the passages to have an usb camera (mickrotek eyestar) running with the cpia driver? (I know it is just experimental) I have compiled the kernel 2.3.34, is that version too old? I compiled the driver into the kernel, not as a module, is this a problem? If such a faq exist I could traduce it in Italian 'couse I'd like to contripute developing the driver but I'm not so good with c... Thanks for all your answers ___ (_|_) |\ Roberto Previdi From sTYLe@WtAl.De Wed, 01 Mar 2000 11:30:02 +0100 Date: Wed, 01 Mar 2000 11:30:02 +0100 From: Bastian sTYLe@WtAl.De Subject: [cpia] client probs I use the creative webcam II, kernel 2.2.13, reflection x as xserver on win98 to connect to my linux box. bringing up the modules works fine : ------------- Linux video capture interface: v1.00 V4L-Driver for Vision CPiA based cameras v0.7.1 Parallel port driver for Vision CPiA based cameras v0.7.1 using PIO mode cpia.c(49960):goto_low_power(2280):camera now in LOW power state cpia.c(49968):goto_high_power(2268):camera now in HIGH power state cpia.c(49980):dispatch_commands(2023):1 1 0 0 1 1 1 1 cpia.c(49980):dispatch_commands(2024):0 1 1 1 1 1 0 1 cpia.c(49984):save_camera_state(2300):0/0/185/0/220/214/214/230 cpia.c(49984):save_camera_state(2304):32/6/92 CPiA Version: 1.02 (1.0) CPiA PnP-ID: 0553:0001:0100 VP-Version: 1.0 0100 1 camera(s) found ------------- but when i try to start a client (xawtv, gqcam) i always get a segmentation fault. dmesg says : ------------- Unable to handle kernel NULL pointer dereference at virtual address 0000000c current->tss.cr3 = 03537000, %cr3 = 03537000 *pde = 00000000 Oops: 0000 CPU: 0 EIP: 0010:[] EFLAGS: 00010212 eax: 00000000 ebx: 00032000 ecx: c3538000 edx: 00000316 esi: c58dd000 edi: c58dd000 ebp: 0000001f esp: c3539f2c ds: 0018 es: 0018 ss: 0018 Process vidcat (pid: 582, process nr: 45, stackpage=c3539000) Stack: c5862540 c3612e00 c586ba94 00031ba5 c3311eb0 00000000 c586217f c3311eb0 00000000 00000000 c3648840 c34deff0 00000051 00000000 000000ff c01c017c c01e77e0 c01271cf c34deff0 c3648840 c3648840 00000000 c34deff0 c0125fa4 Call Trace: [] [] [] [] [] [] [] [] Code: 8b 40 0c 8b 14 90 85 d2 74 3b 81 e2 00 f0 ff ff 89 f8 c1 e8 ------------- what could it be ?? Bastian From Peter.Pregler@risc.uni-linz.ac.at Wed, 01 Mar 2000 11:55:21 +0100 (CET) Date: Wed, 01 Mar 2000 11:55:21 +0100 (CET) From: Peter Pregler Peter.Pregler@risc.uni-linz.ac.at Subject: [cpia] client probs Hi, this was solved for me too in version 0.7.2. AFAIK it has to do with the new memory allocation code in the 2.3 port. I have put 0.7.2 to http://www.risc.uni-linz.ac.at/people/ppregler/cpia/ until it is available on the standard web-site. I guess we need a new strategy for the source distribution. Is is okay for you Jarl to add a pointer and a comment to your source archive to my web-page? I guess I have more time to keep the source up to date. Actually there is also a reference missing to the control client. -Peter On 01-Mar-2000 Bastian wrote: > I use the creative webcam II, kernel 2.2.13, reflection x as xserver on > win98 > to connect to my linux box. > bringing up the modules works fine : > ------------- > Linux video capture interface: v1.00 > V4L-Driver for Vision CPiA based cameras v0.7.1 > Parallel port driver for Vision CPiA based cameras v0.7.1 > using PIO mode > cpia.c(49960):goto_low_power(2280):camera now in LOW power state > cpia.c(49968):goto_high_power(2268):camera now in HIGH power state > cpia.c(49980):dispatch_commands(2023):1 1 0 0 1 1 1 1 > cpia.c(49980):dispatch_commands(2024):0 1 1 1 1 1 0 1 > cpia.c(49984):save_camera_state(2300):0/0/185/0/220/214/214/230 > cpia.c(49984):save_camera_state(2304):32/6/92 > CPiA Version: 1.02 (1.0) > CPiA PnP-ID: 0553:0001:0100 > VP-Version: 1.0 0100 > 1 camera(s) found > ------------- > > but when i try to start a client (xawtv, gqcam) i always get a > segmentation > fault. > dmesg says : > > ------------- > Unable to handle kernel NULL pointer dereference at virtual address > 0000000c > current->tss.cr3 = 03537000, %cr3 = 03537000 > *pde = 00000000 > Oops: 0000 > CPU: 0 > EIP: 0010:[] > EFLAGS: 00010212 > eax: 00000000 ebx: 00032000 ecx: c3538000 edx: 00000316 > esi: c58dd000 edi: c58dd000 ebp: 0000001f esp: c3539f2c > ds: 0018 es: 0018 ss: 0018 > Process vidcat (pid: 582, process nr: 45, stackpage=c3539000) > Stack: c5862540 c3612e00 c586ba94 00031ba5 c3311eb0 00000000 c586217f > c3311eb0 > 00000000 00000000 c3648840 c34deff0 00000051 00000000 000000ff > c01c017c > c01e77e0 c01271cf c34deff0 c3648840 c3648840 00000000 c34deff0 > c0125fa4 > Call Trace: [] [] [] [] > [] [ 0125fa4>] [] > [] > Code: 8b 40 0c 8b 14 90 85 d2 74 3b 81 e2 00 f0 ff ff 89 f8 c1 e8 > ------------- > > what could it be ?? > > Bastian > > > _______________________________________________ > cpia mailing list - cpia@risc.uni-linz.ac.at > http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia > ------------------------------- Email: Peter.Pregler@risc.uni-linz.ac.at WWW: http://www.risc.uni-linz.ac.at/people/ppregler From nicolas.roussel@gmd.de Wed, 1 Mar 2000 12:14:11 +0100 (CET) Date: Wed, 1 Mar 2000 12:14:11 +0100 (CET) From: Nicolas Roussel nicolas.roussel@gmd.de Subject: [cpia] client probs > I guess we need a new strategy for the source distribution. Is is > okay for you Jarl to add a pointer and a comment to your source > archive to my web-page? How about moving to something like sourceforge.net ? Does anybody know how it works ? Nicolas -- ________________________________________________________________________ Nicolas Roussel mailto:nicolas.roussel@gmd.de GMD - FIT.HCI, Schloss Birlinghoven http://www-ihm.lri.fr/~roussel/ 53754 St. Augustin, Germany phone: +49 2241 14-2154 / fax: 14-2065 ________________________________________________________________________ From thunder@ultravision.net Wed, 01 Mar 2000 05:23:41 -0600 Date: Wed, 01 Mar 2000 05:23:41 -0600 From: Thunder thunder@ultravision.net Subject: [cpia] Re: cpia digest, Vol 1 #34 - 16 msgs cpia-admin@risc.uni-linz.ac.at wrote: > Send cpia mailing list submissions to > cpia@risc.uni-linz.ac.at > > To subscribe or unsubscribe via the web, visit > http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia > or, via email, send a message with subject or body 'help' to > cpia-request@risc.uni-linz.ac.at > You can reach the person managing the list at > cpia-admin@risc.uni-linz.ac.at > > When replying, please edit your Subject line so it is more specific than > "Re: Contents of cpia digest..." > > ------------------------------------------------------------------------ > Today's Topics: > > 1. Device or resource busy (jylam) > 2. Oups (jylam) > 3. mhh, you have to kill me (jylam) > 4. RE: Device or resource busy (Peter Pregler) > 5. adminsitrativa - archive problems (Peter Pregler) > 6. Re: cpia-0.7.2 (Tore Halset) > 7. Driver for Creative WebCAM III (root@cummings.uol.com.br) > 8. Re: Driver for Creative WebCAM III (Nicolas Roussel) > 9. Re: Driver for Creative WebCAM III (root@cummings.uol.com.br) > 10. Re: Driver for Creative WebCAM III (and general driver design issues) (Nicolas Roussel) > 11. Re: Driver for Creative WebCAM III (and general driver design issues) (Gleicon S. Moraes) > 12. CPiA 0.7.2 & Zoomtel camera: Colour balance strangeness (rich@annexia.org) > 13. Re: CPiA 0.7.2 & Zoomtel camera: Colour balance strangeness (Johannes Erdfelt) > 14. Re: CPiA 0.7.2 & Zoomtel camera: Colour balance strangeness (rich@annexia.org) > 15. Re: adminsitrativa - archive problems (Mads Bondo Dydensborg) > 16. /dev/video (Thunder) > > ------------------------------------------------------------------------ > > Subject: [cpia] Device or resource busy > Date: Wed, 01 Mar 2000 12:18:39 +0100 > From: jylam > Organization: HangOver > To: cpia@risc.uni-linz.ac.at > > Hi all. > > since 3-4 hours, I'm trying to make my Creative WebCamII working. > > But. > > Here is my lsmod: > > Module Size Used by > parport_pc 5012 0 (autoclean) > cpia 48476 0 > parport_probe 2884 0 > videodev 2400 0 [cpia] > appletalk 17312 11 (autoclean) > nfs 29944 1 (autoclean) > lockd 30856 1 (autoclean) [nfs] > sunrpc 52356 1 (autoclean) [nfs lockd] > parport 7092 0 (autoclean) [parport_pc parport_probe] > eepro100 12112 1 (autoclean) > es1371 23212 0 > soundcore 2372 4 [es1371] > > Everything is good, but cpia_pp. > > root@talisker: (bash) 1164 /home/racine/cpia-0.7.1/module > insmod cpia_pp.o > cpia_pp.o: init_module: Device or resource busy > > here is my /var/log/messages > > Mar 1 12:16:17 talisker kernel: Parallel port driver for Vision CPiA based cameras v0.7.1 > Mar 1 12:16:17 talisker kernel: 0 camera(s) found > > I tried the Patch posted the Fri, 11 Feb 2000 17:42:39, it don't work at all, it's the same result. > > So what's wrong ? is my MAKEDEV video wrong ? or anything ? Please help me, or I think I will eat a *big* dog :) > > Thanks > > -- > ,---------. ,------------------. > |Jean-Yves \___/ Jylam@HangOver.fr | > `---------------------^------------' > Administrateur systeme Linux > Hangover (http://www.hangover.fr) > > ------------------------------------------------------------------------ > > Subject: [cpia] Oups > Date: Wed, 01 Mar 2000 12:20:46 +0100 > From: jylam > Organization: HangOver > To: cpia@risc.uni-linz.ac.at > > Oups, sorry, I missed to say that I use a parallel version of Creative > WebCamII, so don't talk to me about usb :) > > -- > ,---------. ,------------------. > |Jean-Yves \___/ Jylam@HangOver.fr | > `---------------------^------------' > Administrateur systeme Linux > Hangover (http://www.hangover.fr) > > ------------------------------------------------------------------------ > > Subject: [cpia] mhh, you have to kill me > Date: Wed, 01 Mar 2000 12:23:06 +0100 > From: jylam > Organization: HangOver > To: cpia@risc.uni-linz.ac.at > > Kill me if you think I'm boring :) > I missed to say that my parallel port IS ECP (parport0: PC-style at > 0x378 [SPP,ECP,ECPEPP,ECPPS2]),too. > It whould be okay, now :) > > -- > ,---------. ,------------------. > |Jean-Yves \___/ Jylam@HangOver.fr | > `---------------------^------------' > Administrateur systeme Linux > Hangover (http://www.hangover.fr) > > ------------------------------------------------------------------------ > > Subject: RE: [cpia] Device or resource busy > Date: Tue, 29 Feb 2000 13:14:52 +0100 (CET) > From: Peter Pregler > Organization: RISC-Linz > To: jylam > CC: cpia@risc.uni-linz.ac.at > > On 01-Mar-2000 jylam wrote: > > > > Mar 1 12:16:17 talisker kernel: Parallel port driver for Vision CPiA > > based cameras v0.7.1 > > Mar 1 12:16:17 talisker kernel: 0 camera(s) found > > > > I tried the Patch posted the Fri, 11 Feb 2000 17:42:39, it don't work at > > all, it's the same result. > > I had a similar problem with 0.7.1. The patch to 0.7.2 posted by Scott > on Feb-27 solved the problem for me. Apparently there are some changes in > the camera-initialisation code that also affect the parport-code. If I get > the problems again with 0.7.2 I will have a deeper look into it. > > -Peter > > ------------------------------- > Email: Peter.Pregler@risc.uni-linz.ac.at > WWW: http://www.risc.uni-linz.ac.at/people/ppregler > > ------------------------------------------------------------------------ > > Subject: [cpia] adminsitrativa - archive problems > Date: Tue, 29 Feb 2000 14:52:09 +0100 (CET) > From: Peter Pregler > Organization: RISC-Linz > To: cpia@risc.uni-linz.ac.at > > Dear all, > > due to some sillyness of mine no mails were archived after 12th of > February. :( I have added what I had in my private mbox manually. Since I > keep only important stuff in my private box this should do it. :) If you > feel censored or think anything important is missing just send it to me by > e-mail and I will add it to the archive again. > > Sorry, Peter > > ------------------------------- > Email: Peter.Pregler@risc.uni-linz.ac.at > WWW: http://www.risc.uni-linz.ac.at/people/ppregler > > ------------------------------------------------------------------------ > > Subject: Re: [cpia] cpia-0.7.2 > Date: Tue, 29 Feb 2000 15:01:27 +0100 (MET) > From: Tore Halset > To: cpia@risc.uni-linz.ac.at > > On Sun, 27 Feb 2000 sbertin@mindspring.com wrote: > > > This patch is relative to cpia-0.7.1 > > Will this be included in the kernel? > > - Tore. > > ------------------------------------------------------------------------ > > Subject: [cpia] Driver for Creative WebCAM III > Date: Tue, 29 Feb 2000 14:16:02 -0300 > From: fabiano.reis@uol.com.br > Organization: Universo Online > To: cpia@risc.uni-linz.ac.at > > Some one know if there is a driver for this cam? > > TKS, > > Fabiano > > ------------------------------------------------------------------------ > > Subject: Re: [cpia] Driver for Creative WebCAM III > Date: Tue, 29 Feb 2000 18:04:51 +0100 (CET) > From: Nicolas Roussel > To: fabiano.reis@uol.com.br > CC: cpia@risc.uni-linz.ac.at > References: <38BBFED2.36BF9D78@uol.com.br> > > Oi Fabiano ! > > A driver for OV511-based cameras (including WebCam III) is included in > recent kernels (in the USB driver section). For more information, > check : > > http://people.delphi.com/mmcclelland/linux/ov511.html > > Nicolas > > -- > ________________________________________________________________________ > > Nicolas Roussel mailto:nicolas.roussel@gmd.de > GMD - FIT.HCI, Schloss Birlinghoven http://www-ihm.lri.fr/~roussel/ > 53754 St. Augustin, Germany phone: +49 2241 14-2154 / fax: 14-2065 > ________________________________________________________________________ > > ------------------------------------------------------------------------ > > Subject: Re: [cpia] Driver for Creative WebCAM III > Date: Tue, 29 Feb 2000 15:40:35 -0300 > From: fabiano.reis@uol.com.br > Organization: Universo Online > To: Nicolas Roussel > CC: cpia@risc.uni-linz.ac.at > References: <38BBFED2.36BF9D78@uol.com.br> <20000229170451.4CEEA14D@mimix.gmd.de> > > Nicolas, > > I forgot to remember: I'm using a WebCam Creative III in paralell port. > > -Fabiano (br-sp/sp) > > Nicolas Roussel wrote: > > > Oi Fabiano ! > > > > A driver for OV511-based cameras (including WebCam III) is included in > > recent kernels (in the USB driver section). For more information, > > check : > > > > http://people.delphi.com/mmcclelland/linux/ov511.html > > > > Nicolas > > > > -- > > ________________________________________________________________________ > > > > Nicolas Roussel mailto:nicolas.roussel@gmd.de > > GMD - FIT.HCI, Schloss Birlinghoven http://www-ihm.lri.fr/~roussel/ > > 53754 St. Augustin, Germany phone: +49 2241 14-2154 / fax: 14-2065 > > ________________________________________________________________________ > > > > _______________________________________________ > > cpia mailing list - cpia@risc.uni-linz.ac.at > > http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia > > ------------------------------------------------------------------------ > > Subject: Re: [cpia] Driver for Creative WebCAM III (and general driver design issues) > Date: Tue, 29 Feb 2000 19:57:25 +0100 (CET) > From: Nicolas Roussel > To: fabiano.reis@uol.com.br > CC: nicolas.roussel@gmd.de, cpia@risc.uni-linz.ac.at > References: <38BBFED2.36BF9D78@uol.com.br> <20000229170451.4CEEA14D@mimix.gmd.de> <38BC12A3.84483A7B@uol.com.br> > > > I forgot to remember: I'm using a WebCam Creative III in paralell port. > > Hum... Then I guess you might be able to use some of the cpia_pp code > and the USB OV511 driver to create a new driver. > > Maybe Peter Pregler or Scott Bertin can help you with this (I don't > know the internals of the cpia_pp driver). You should also contact > Mark McClelland, the guy responsible for the OV511 USB driver. > > I think this PP/USB question about the OV511 shows once again that the > drivers could be split into smaller parts. I can see at least three : > > - what the chip can do > - how it is attached to the computer (here, PP/USB) > > - how the capabilities of the chip are mapped onto V4L API > > The unified CPiA driver already separates the two first parts. Why not > take the V4L API out of cpia.c ? We could then have a cpia_v4l.c, a > cpia_v4l2.c or even another user space library. > > Comments anybody ? > > Nicolas > > -- > ________________________________________________________________________ > > Nicolas Roussel mailto:nicolas.roussel@gmd.de > GMD - FIT.HCI, Schloss Birlinghoven http://www-ihm.lri.fr/~roussel/ > 53754 St. Augustin, Germany phone: +49 2241 14-2154 / fax: 14-2065 > ________________________________________________________________________ > > ------------------------------------------------------------------------ > > Subject: Re: [cpia] Driver for Creative WebCAM III (and general driver design issues) > Date: Tue, 29 Feb 2000 16:11:03 -0300 > From: "Gleicon S. Moraes" > To: "Nicolas Roussel" , > CC: , > References: <38BBFED2.36BF9D78@uol.com.br> <20000229170451.4CEEA14D@mimix.gmd.de> <38BC12A3.84483A7B@uol.com.br> <20000229185725.90FC5204@mimix.gmd.de> > > Well, I think such design would be a good start point to use news features > like v4l-2, new chips, and to make the things cleaner: > > chip -> device ( parport or usb) -> access method ( v4l, v4l-2, or even > another spec , i dont know :D ). > > The only point is: we already have the driver going stable ( well, at least > for me its *very* stable and production quality) and changes like this, take > time to be stable and done... > This design in *theory* are a good step to portability, and a good way to > add features like news chips and video formats, and a good way to port it > between O.S's. > Well, Just comments ... > Best regards > > Gleicon S. Moraes > p.s.; excuse my bad english. > > ----- Original Message ----- > From: Nicolas Roussel > To: > Cc: ; > Sent: Tuesday, February 29, 2000 3:57 PM > Subject: Re: [cpia] Driver for Creative WebCAM III (and general driver > design issues) > > > > > > I forgot to remember: I'm using a WebCam Creative III in paralell port. > > > > Hum... Then I guess you might be able to use some of the cpia_pp code > > and the USB OV511 driver to create a new driver. > > > > Maybe Peter Pregler or Scott Bertin can help you with this (I don't > > know the internals of the cpia_pp driver). You should also contact > > Mark McClelland, the guy responsible for the OV511 USB driver. > > > > I think this PP/USB question about the OV511 shows once again that the > > drivers could be split into smaller parts. I can see at least three : > > > > - what the chip can do > > - how it is attached to the computer (here, PP/USB) > > > > - how the capabilities of the chip are mapped onto V4L API > > > > The unified CPiA driver already separates the two first parts. Why not > > take the V4L API out of cpia.c ? We could then have a cpia_v4l.c, a > > cpia_v4l2.c or even another user space library. > > > > Comments anybody ? > > > > Nicolas > > > > -- > > ________________________________________________________________________ > > > > Nicolas Roussel mailto:nicolas.roussel@gmd.de > > GMD - FIT.HCI, Schloss Birlinghoven http://www-ihm.lri.fr/~roussel/ > > 53754 St. Augustin, Germany phone: +49 2241 14-2154 / fax: 14-2065 > > ________________________________________________________________________ > > > > _______________________________________________ > > cpia mailing list - cpia@risc.uni-linz.ac.at > > http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia > > > > ------------------------------------------------------------------------ > > Subject: [cpia] CPiA 0.7.2 & Zoomtel camera: Colour balance strangeness > Date: Tue, 29 Feb 2000 21:42:03 +0000 > From: rich@annexia.org > To: CPiA mailing list > > Dear all: > > Running gqcam supplied with cpia-0.7.2 (kernel 2.3.48), or > running Xawtv, I get strange colour-balance problems. The > picture appears yellow most of the time, as in this example: > > http://www.annexia.org/tmp/yellow.jpg > > (about 1 in every 10 times I run the program, the colour > is correct). Note that the walls in this picture are white > and the poster on the right is turquoise. > > If I put my hand over the camera for a few seconds, then > afterwards, everything is green (:-) > > http://www.annexia.org/tmp/green.jpg > > ... for a few seconds before going dark! > > http://www.annexia.org/tmp/dark.jpg > > ... permanently. You have to restart gqcam to get back to > `normal' (ie. yellow mode). > > I have tried setting color_balance_mode and exposure_mode > to manual and auto, but to no apparent effect. I also tried > setting the {red,green,blue}_gain settings, but these seem > to have a mind of their own, and just wander back to obviously > incorrect values after I set them (independent of whether the > various exposure_mode and color_balance_mode are manual or > not). > > Oh, and these problems only really occur in low light conditions > (with a 60W bulb). In very bright daylight the results are much > better. Being a hacker I'm obviously mainly interested in the low > light situation :-) > > Any ideas what's going on? > > Rich. > > read-only > ----------------------- > CPIA Version: 1.30 (2.10) > CPIA PnP-ID: 0553:0002:0100 > VP-Version: 1.0 0100 > system_state: 0x02 > grab_state: 0x10 > stream_state: 0x00 > fatal_error: 0x00 > cmd_error: 0x00 > debug_flags: 0x00 > vp_status: 0x10 > error_code: 0x80 > video_size: CIF > sub_sample: 422 > yuv_order: YUYV > roi: ( 0, 0) to (352, 288) > actual_fps: 4 > transfer_rate: 918kB/s > > read-write > ----------------------- current min max default comment > brightness: 50 0 100 50 > contrast: 48 0 96 48 steps of 8 > saturation: 49 0 100 50 > sensor_fps: 15.000 3 30 15 > stream_start_line: 240 0 288 240 > ecp_timing: normal slow normal normal > color_balance_mode: manual manual auto auto > red_gain: 6 0 212 32 > green_gain: 208 0 212 6 > blue_gain: 210 0 212 92 > max_gain: 2 1,2,4,8 2 > exposure_mode: manual manual auto auto > centre_weight: off off on on > gain: 2 1 max_gain 1 1,2,4,8 possible > fine_exp: 0 0 511 0 > coarse_exp: 256 0 65535 185 > red_comp: 0 220 255 220 > green1_comp: 0 214 255 214 > green2_comp: 192 214 255 214 > blue_comp: 128 230 255 230 > apcor_gain1: 0x1c 0x0 0xff 0x1c > apcor_gain2: 0x1a 0x0 0xff 0x1a > apcor_gain4: 0x2d 0x0 0xff 0x2d > apcor_gain8: 0x2a 0x0 0xff 0x2a > vl_offset_gain1: 24 0 255 24 > vl_offset_gain2: 28 0 255 28 > vl_offset_gain4: 30 0 255 30 > vl_offset_gain8: 30 0 255 30 > flicker_control: off off on off > mains_frequency: 50 50 60 50 only 50/60 > allowable_overexposure: 0 0 255 0 > compression_mode: auto none,auto,manual auto > decimation_enable: off off off off > compression_target: framerate framerate quality quality > target_framerate: 7 0 30 7 > target_quality: 10 0 255 10 > y_threshold: 3 0 31 15 > uv_threshold: 3 0 31 15 > hysteresis: 3 0 255 3 > threshold_max: 11 0 255 11 > small_step: 1 0 255 1 > large_step: 3 0 255 3 > decimation_hysteresis: 2 0 255 2 > fr_diff_step_thresh: 5 0 255 5 > q_diff_step_thresh: 3 0 255 3 > decimation_thresh_mod: 2 0 255 2 > > -- > rich@annexia.org | Is your school part of http://www.schoolmaster.net ? > BiblioTech Ltd, Unit 2 Piper Centre, 50 Carnwath Road, London, SW6 3EG. > +44 20 7384 6917 | Click here to play XRacer: http://xracer.annexia.org > Copyright © 2000 Richard Jones | GnuPG/PGP key from www.annexia.org > > ------------------------------------------------------------------------ > > Subject: Re: [cpia] CPiA 0.7.2 & Zoomtel camera: Colour balance strangeness > Date: Tue, 29 Feb 2000 17:05:12 -0500 > From: Johannes Erdfelt > To: rich@annexia.org > CC: CPiA mailing list > References: <20000229214202.B11723@www.annexia.org> > > On Tue, Feb 29, 2000, rich@annexia.org wrote: > > Dear all: > > > > Running gqcam supplied with cpia-0.7.2 (kernel 2.3.48), or > > running Xawtv, I get strange colour-balance problems. The > > picture appears yellow most of the time, as in this example: > > > > http://www.annexia.org/tmp/yellow.jpg > > > > (about 1 in every 10 times I run the program, the colour > > is correct). Note that the walls in this picture are white > > and the poster on the right is turquoise. > > > > If I put my hand over the camera for a few seconds, then > > afterwards, everything is green (:-) > > > > http://www.annexia.org/tmp/green.jpg > > > > ... for a few seconds before going dark! > > > > http://www.annexia.org/tmp/dark.jpg > > > > ... permanently. You have to restart gqcam to get back to > > `normal' (ie. yellow mode). > > > > I have tried setting color_balance_mode and exposure_mode > > to manual and auto, but to no apparent effect. I also tried > > setting the {red,green,blue}_gain settings, but these seem > > to have a mind of their own, and just wander back to obviously > > incorrect values after I set them (independent of whether the > > various exposure_mode and color_balance_mode are manual or > > not). > > > > Oh, and these problems only really occur in low light conditions > > (with a 60W bulb). In very bright daylight the results are much > > better. Being a hacker I'm obviously mainly interested in the low > > light situation :-) > > FWIW, I've seen this as well. It sometimes is yellowish, or purplish (I > think). Mostly yellow. > > JE > > ------------------------------------------------------------------------ > > Subject: Re: [cpia] CPiA 0.7.2 & Zoomtel camera: Colour balance strangeness > Date: Tue, 29 Feb 2000 22:09:13 +0000 > From: rich@annexia.org > To: CPiA mailing list > References: <20000229214202.B11723@www.annexia.org> <20000229170512.X16908@sventech.com> > > On Tue, Feb 29, 2000 at 05:05:12PM -0500, Johannes Erdfelt wrote: > > FWIW, I've seen this as well. It sometimes is yellowish, or purplish (I > > think). Mostly yellow. > > Yeah, purplish. Seen that too, but only very rarely. > > Rich. > > -- > rich@annexia.org | Is your school part of http://www.schoolmaster.net ? > BiblioTech Ltd, Unit 2 Piper Centre, 50 Carnwath Road, London, SW6 3EG. > +44 20 7384 6917 | Click here to play XRacer: http://xracer.annexia.org > Copyright © 2000 Richard Jones | GnuPG/PGP key from www.annexia.org > > ------------------------------------------------------------------------ > > Subject: Re: [cpia] adminsitrativa - archive problems > Date: Wed, 1 Mar 2000 00:47:52 +0100 (CET) > From: Mads Bondo Dydensborg > To: Peter Pregler > CC: cpia@risc.uni-linz.ac.at > > On Tue, 29 Feb 2000, Peter Pregler wrote: > > > Dear all, > > > > due to some sillyness of mine no mails were archived after 12th of > > February. :( I have added what I had in my private mbox manually. Since I > > keep only important stuff in my private box this should do it. :) If you > > feel censored or think anything important is missing just send it to me by > > e-mail and I will add it to the archive again. > > In case you need it, I should have every mail. > > Mads > > You know you're a Linux geek when... > > You can reconstruct your fstab from scratch, and not even think about it. > > - segfault > > ------------------------------------------------------------------------ > > Subject: [cpia] /dev/video > Date: Tue, 29 Feb 2000 19:34:07 -0600 > From: Thunder > To: cpia@risc.uni-linz.ac.at > > hi all > > I have a Ezonics webcam and running 2.3.47 kernel with cpia-0.7.1. > The problem I am incurring is that application xawtv or gqcam > errors when ran with: > > open /dev/video > no video grabber device available > > This doesnt happen all the time.. it's spaztic.. stops and starts > on it's own.. I have not been able to control when it stops or > when it decides to work again... > > I have not been able to pinpoint what is causing it, I have a site > that streamer (a xawtv app.) pointed at my local webpage as > a test and is supposed to take a clip every 30 seconds. But even > if this function is disabled I have the same error.. My logs dont show > anything out of the ordinary. Any clues or possible troubleshooting > technics in this matter sure would be appreciated. > > Bill Espinosa > > ------------------------------------------------------------------------ > _______________________________________________ > cpia mailing list - cpia@risc.uni-linz.ac.at > http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia :) I just re-read this post ... hmm it doesnt tell much... the cam is a USB. Ps is'nt showing any other app using it and rebooting appears to help for a bit.. Is there any output i should be watching while troubleshooting this? Thanks inadvance Bill Espinosa From jto@bdc.no Wed, 01 Mar 2000 12:35:36 +0100 Date: Wed, 01 Mar 2000 12:35:36 +0100 From: Jarl Totland jto@bdc.no Subject: Sourceforge (Was: Re: [cpia] client probs) Peter: >> I guess we need a new strategy for the source distribution. Is is >> okay for you Jarl to add a pointer and a comment to your source >> archive to my web-page? This has now been done. Nicolas: > How about moving to something like sourceforge.net ? Does anybody know > how it works ? This is a very good idea. I'm working on the registration right now. This will give us integrated forums, mailinglist, bugtraq, cvs and ftp. It also opens up for other people to do updates to the webpage. Hopefully all this can be up this week, depends on how much automation there is. Vyrdsamt, -Jarl From sTYLe@WtAl.De Wed, 01 Mar 2000 14:14:34 +0100 Date: Wed, 01 Mar 2000 14:14:34 +0100 From: Bastian sTYLe@WtAl.De Subject: [cpia] client probs At 11:55 1.3.2000 +0100, Peter Pregler wrote: >Hi, > >this was solved for me too in version 0.7.2. AFAIK it has to do with the changed to 0.7.2 but still have the probleme below. what about the kernel.patch ? is this just to add the newest version of cpia to the kernel sources or do i need to run the patch ? and what about causing my kernel version 2.2.13 this problem ? better stepping up to 2.2.14 ? i am very sad, because it was hard to get that old model (webcam II). >On 01-Mar-2000 Bastian wrote: > > I use the creative webcam II, kernel 2.2.13, reflection x as xserver on > > win98 > > to connect to my linux box. > > bringing up the modules works fine : > > ------------- > > Linux video capture interface: v1.00 > > V4L-Driver for Vision CPiA based cameras v0.7.1 > > Parallel port driver for Vision CPiA based cameras v0.7.1 > > using PIO mode > > cpia.c(49960):goto_low_power(2280):camera now in LOW power state > > cpia.c(49968):goto_high_power(2268):camera now in HIGH power state > > cpia.c(49980):dispatch_commands(2023):1 1 0 0 1 1 1 1 > > cpia.c(49980):dispatch_commands(2024):0 1 1 1 1 1 0 1 > > cpia.c(49984):save_camera_state(2300):0/0/185/0/220/214/214/230 > > cpia.c(49984):save_camera_state(2304):32/6/92 > > CPiA Version: 1.02 (1.0) > > CPiA PnP-ID: 0553:0001:0100 > > VP-Version: 1.0 0100 > > 1 camera(s) found > > ------------- > > > > but when i try to start a client (xawtv, gqcam) i always get a > > segmentation > > fault. > > dmesg says : > > > > ------------- > > Unable to handle kernel NULL pointer dereference at virtual address > > 0000000c > > current->tss.cr3 = 03537000, %cr3 = 03537000 > > *pde = 00000000 > > Oops: 0000 > > CPU: 0 > > EIP: 0010:[] > > EFLAGS: 00010212 > > eax: 00000000 ebx: 00032000 ecx: c3538000 edx: 00000316 > > esi: c58dd000 edi: c58dd000 ebp: 0000001f esp: c3539f2c > > ds: 0018 es: 0018 ss: 0018 > > Process vidcat (pid: 582, process nr: 45, stackpage=c3539000) > > Stack: c5862540 c3612e00 c586ba94 00031ba5 c3311eb0 00000000 c586217f > > c3311eb0 > > 00000000 00000000 c3648840 c34deff0 00000051 00000000 000000ff > > c01c017c > > c01e77e0 c01271cf c34deff0 c3648840 c3648840 00000000 c34deff0 > > c0125fa4 > > Call Trace: [] [] [] [] > > [] [ > 0125fa4>] [] > > [] > > Code: 8b 40 0c 8b 14 90 85 d2 74 3b 81 e2 00 f0 ff ff 89 f8 c1 e8 > > ------------- > > Bastian From lists@sprawl.net Wed, 1 Mar 2000 10:55:07 -0500 Date: Wed, 1 Mar 2000 10:55:07 -0500 From: Adam Lynch lists@sprawl.net Subject: [cpia] unresolved symbols I've been trying to get my Creative Webcam II working for awhile now, and haven't really played with the CPiA driver since 0.4.4 . I went to give 0.7.2 a shot today, and I get all sorts of fun errors upon the attempted loading of the cpia.o and cpia_pp.o modules. Here's an lsmmod output before I go to load the drivers: Module Size Used by smbfs 29688 1 (autoclean) nfs 31960 1 (autoclean) lockd 33736 1 (autoclean) [nfs] sunrpc 57732 1 (autoclean) [nfs lockd] 3c59x 18664 1 (autoclean) vfat 11004 0 (unused) fat 33120 0 [vfat] supermount 14912 2 (autoclean) opl3 13928 1 sb 37588 1 uart401 6480 1 [sb] sound 66328 0 [opl3 sb uart401] soundlow 304 0 [sound] soundcore 4164 6 [sb sound] aic7xxx 111152 4 And here are the unresolved symbol errors I get upon attempting to load the CPiA modules: cpia.o: unresolved symbol remap_page_range cpia.o: unresolved symbol schedule_timeout cpia.o: unresolved symbol schedule cpia.o: unresolved symbol kmalloc cpia.o: unresolved symbol _ctype cpia.o: unresolved symbol create_proc_entry cpia.o: unresolved symbol kernel_flag cpia.o: unresolved symbol vfree cpia.o: unresolved symbol video_register_device cpia.o: unresolved symbol video_unregister_device cpia.o: unresolved symbol request_module cpia.o: unresolved symbol kfree cpia.o: unresolved symbol vmalloc cpia.o: unresolved symbol remove_proc_entry cpia.o: unresolved symbol mem_map cpia.o: unresolved symbol simple_strtoul cpia.o: unresolved symbol sprintf cpia.o: unresolved symbol jiffies cpia.o: unresolved symbol printk cpia.o: unresolved symbol __generic_copy_to_user cpia_pp.o: unresolved symbol __wake_up cpia_pp.o: unresolved symbol parport_unregister_device cpia_pp.o: unresolved symbol schedule cpia_pp.o: unresolved symbol tq_immediate cpia_pp.o: unresolved symbol bh_active cpia_pp.o: unresolved symbol parport_enumerate cpia_pp.o: unresolved symbol kmalloc cpia_pp.o: unresolved symbol cpia_unregister_camera cpia_pp.o: unresolved symbol __global_cli cpia_pp.o: unresolved symbol cpia_register_camera cpia_pp.o: unresolved symbol free_dma cpia_pp.o: unresolved symbol kernel_flag cpia_pp.o: unresolved symbol parport_register_device cpia_pp.o: unresolved symbol request_module cpia_pp.o: unresolved symbol tqueue_lock cpia_pp.o: unresolved symbol request_dma cpia_pp.o: unresolved symbol interruptible_sleep_on cpia_pp.o: unresolved symbol kfree cpia_pp.o: unresolved symbol __global_save_flags cpia_pp.o: unresolved symbol tq_scheduler cpia_pp.o: unresolved symbol parport_claim cpia_pp.o: unresolved symbol dma_spin_lock cpia_pp.o: unresolved symbol __global_restore_flags cpia_pp.o: unresolved symbol parport_release cpia_pp.o: unresolved symbol simple_strtoul cpia_pp.o: unresolved symbol jiffies cpia_pp.o: unresolved symbol printk cpia_pp.o: unresolved symbol __const_udelay And here's what dmesg has to say: Linux video capture interface: v1.00 parport0: PC-style at 0x378 (0x778) [SPP,ECP,ECPPS2] parport0: read2 timeout. parport0: Multimedia device, VLSI Vision Ltd DUAL Camera parport0: PC-style at 0x378 (0x778) [SPP,ECP,ECPPS2] The machine is a dual PPro-200 running Mandrake 7.0 (kernel 2.2.14-15). Before I did a make on the modules, I made sure to define -D__SMP__ on the right line. Any ideas? -- --- AdamL. alynch@sprawl.net http://sprawl.net Never attribute to malice that which can be adequately explained by stupidity. -Robert Heinlein, 'Logic of Empire' Any view of the universe that is not strange is false. -Neil Gaiman From Peter.Pregler@risc.uni-linz.ac.at Wed, 01 Mar 2000 17:19:21 +0100 (CET) Date: Wed, 01 Mar 2000 17:19:21 +0100 (CET) From: Peter Pregler Peter.Pregler@risc.uni-linz.ac.at Subject: [cpia] unresolved symbols On 01-Mar-2000 Adam Lynch wrote: > The machine is a dual PPro-200 running Mandrake 7.0 (kernel > 2.2.14-15). Before > I did a make on the modules, I made sure to define -D__SMP__ on the > right line. > > Any ideas? Are you sure you have the the include path in the makefile to point to the actual kernel include tree with which the running kernel was compiled? From your lsmod-output I guess you have compiled parport and videodev into the kernel? -Peter ------------------------------- Email: Peter.Pregler@risc.uni-linz.ac.at WWW: http://www.risc.uni-linz.ac.at/people/ppregler From lists@sprawl.net Wed, 1 Mar 2000 12:22:03 -0500 Date: Wed, 1 Mar 2000 12:22:03 -0500 From: Adam Lynch lists@sprawl.net Subject: [cpia] unresolved symbols And thus spoke Peter Pregler: > > Are you sure you have the the include path in the makefile to point to the > actual kernel include tree with which the running kernel was compiled? From > your lsmod-output I guess you have compiled parport and videodev into the > kernel? > > -Peter Peter- It points to /usr/src/linux/include, which is where the Mandrake kernel-headers RPM placed the kernel includes.. Also, I'm lazy, so I went with the "loadpp" script. And I didn't have the parport drivers installed. I had rmmod'd 'em before the testing procedure. I'm about to d/l a fresh (non-Mandrake) kernel. I'll give that a go. -- --- AdamL. alynch@sprawl.net http://sprawl.net Never attribute to malice that which can be adequately explained by stupidity. -Robert Heinlein, 'Logic of Empire' Any view of the universe that is not strange is false. -Neil Gaiman From sTYLe@WtAl.De Wed, 01 Mar 2000 20:35:31 +0100 Date: Wed, 01 Mar 2000 20:35:31 +0100 From: Bastian sTYLe@WtAl.De Subject: [cpia] client probs At 14:14 1.3.2000 +0100, Bastian wrote: >At 11:55 1.3.2000 +0100, Peter Pregler wrote: >>Hi, >> >>this was solved for me too in version 0.7.2. AFAIK it has to do with the > >changed to 0.7.2 but still have the probleme below. >what about the kernel.patch ? is this just to add the newest version of >cpia to the kernel sources or do i need to run the patch ? >and what about causing my kernel version 2.2.13 this problem ? >better stepping up to 2.2.14 ? >i am very sad, because it was hard to get that old model (webcam II). > >>On 01-Mar-2000 Bastian wrote: >> > I use the creative webcam II, kernel 2.2.13, reflection x as xserver on >> > win98 >> > to connect to my linux box. >> > bringing up the modules works fine : >> > ------------- >> > Linux video capture interface: v1.00 >> > V4L-Driver for Vision CPiA based cameras v0.7.1 >> > Parallel port driver for Vision CPiA based cameras v0.7.1 >> > using PIO mode >> > cpia.c(49960):goto_low_power(2280):camera now in LOW power state >> > cpia.c(49968):goto_high_power(2268):camera now in HIGH power state >> > cpia.c(49980):dispatch_commands(2023):1 1 0 0 1 1 1 1 >> > cpia.c(49980):dispatch_commands(2024):0 1 1 1 1 1 0 1 >> > cpia.c(49984):save_camera_state(2300):0/0/185/0/220/214/214/230 >> > cpia.c(49984):save_camera_state(2304):32/6/92 >> > CPiA Version: 1.02 (1.0) >> > CPiA PnP-ID: 0553:0001:0100 >> > VP-Version: 1.0 0100 >> > 1 camera(s) found >> > ------------- >> > >> > but when i try to start a client (xawtv, gqcam) i always get a >> > segmentation >> > fault. >> > dmesg says : >> > >> > ------------- >> > Unable to handle kernel NULL pointer dereference at virtual address >> > 0000000c >> > current->tss.cr3 = 03537000, %cr3 = 03537000 >> > *pde = 00000000 >> > Oops: 0000 >> > CPU: 0 >> > EIP: 0010:[] >> > EFLAGS: 00010212 >> > eax: 00000000 ebx: 00032000 ecx: c3538000 edx: 00000316 >> > esi: c58dd000 edi: c58dd000 ebp: 0000001f esp: c3539f2c >> > ds: 0018 es: 0018 ss: 0018 >> > Process vidcat (pid: 582, process nr: 45, stackpage=c3539000) >> > Stack: c5862540 c3612e00 c586ba94 00031ba5 c3311eb0 00000000 c586217f >> > c3311eb0 >> > 00000000 00000000 c3648840 c34deff0 00000051 00000000 000000ff >> > c01c017c >> > c01e77e0 c01271cf c34deff0 c3648840 c3648840 00000000 c34deff0 >> > c0125fa4 >> > Call Trace: [] [] [] [] >> > [] [> > 0125fa4>] [] >> > [] >> > Code: 8b 40 0c 8b 14 90 85 d2 74 3b 81 e2 00 f0 ff ff 89 f8 c1 e8 >> > ------------- >> > just wanted to add that the settings in bios are : ECP, DMA 3. Bastian From sbertin@mindspring.com Wed, 1 Mar 2000 18:04:36 -0500 (EST) Date: Wed, 1 Mar 2000 18:04:36 -0500 (EST) From: sbertin@mindspring.com sbertin@mindspring.com Subject: [cpia] unresolved symbols On 1 Mar, Adam Lynch wrote: > I went to give 0.7.2 a shot today, and I get all sorts of fun errors upon > the attempted loading of the cpia.o and cpia_pp.o modules. This looks like a mismatch between a versioned kernel and non-versioned modules. What does "grep printk /proc/ksyms" tell you? If you get something like "c0113ba4 printk_R1b7d4074", then this is the case and I would guess that the kernel sources you have installed are not configured the same as the kernel you are running. Scott J. Bertin sbertin@mindspring.com From sbertin@mindspring.com Wed, 1 Mar 2000 18:06:39 -0500 (EST) Date: Wed, 1 Mar 2000 18:06:39 -0500 (EST) From: sbertin@mindspring.com sbertin@mindspring.com Subject: [cpia] client probs On 1 Mar, Bastian wrote: > but when i try to start a client (xawtv, gqcam) i always get a segmentation > fault. > dmesg says : > > ------------- > Unable to handle kernel NULL pointer dereference at virtual address 0000000c What do you see just before this? Scott J. Bertin sbertin@mindspring.com From sTYLe@WtAl.De Thu, 02 Mar 2000 20:04:48 +0100 Date: Thu, 02 Mar 2000 20:04:48 +0100 From: Bastian sTYLe@WtAl.De Subject: [cpia] client probs At 18:06 1.3.2000 -0500, sbertin@mindspring.com wrote: >On 1 Mar, Bastian wrote: > > but when i try to start a client (xawtv, gqcam) i always get a > segmentation > > fault. > > dmesg says : > > > > ------------- > > Unable to handle kernel NULL pointer dereference at virtual address > 0000000c > >What do you see just before this? THIS is the first line in dmesg (after the lines telling that loading modules is ok) after starting gqcam there is only one line displayed in term : Segmentation fault. no further output. btw, making a depmod -a says : depmod: *** Unresolved symbols in /lib/modules/2.2.14/net/ppp_deflate.o could it be that my parport is not properly loaded ? and that may cause the problems ? >Scott J. Bertin >sbertin@mindspring.com regards, bastian From sTYLe@WtAl.De Thu, 02 Mar 2000 20:31:49 +0100 Date: Thu, 02 Mar 2000 20:31:49 +0100 From: Bastian sTYLe@WtAl.De Subject: [cpia] client probs At 20:04 2.3.2000 +0100, Bastian wrote: >At 18:06 1.3.2000 -0500, sbertin@mindspring.com wrote: >>On 1 Mar, Bastian wrote: >> > but when i try to start a client (xawtv, gqcam) i always get a >> segmentation >> > fault. >> > dmesg says : >> > >> > ------------- >> > Unable to handle kernel NULL pointer dereference at virtual address >> 0000000c >> >>What do you see just before this? another thing is that after modprob'ing parport and cpia_pp in /var/log/messsages it says the following Mar 2 20:30:45 Little modprobe: modprobe: Can't locate module char-major-6 refering to conf.modules char-major-6 is aliased to lp. is this a problem ? i do not use a printer on that machine. >THIS is the first line in dmesg (after the lines telling that loading >modules is ok) > >after starting gqcam there is only one line displayed in term : >Segmentation fault. >no further output. > >>Scott J. Bertin >>sbertin@mindspring.com > >regards, bastian > > >_______________________________________________ >cpia mailing list - cpia@risc.uni-linz.ac.at >http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia Bastian From sbertin@mindspring.com Thu, 2 Mar 2000 17:53:36 -0500 (EST) Date: Thu, 2 Mar 2000 17:53:36 -0500 (EST) From: sbertin@mindspring.com sbertin@mindspring.com Subject: [cpia] client probs --1037094400-1804289383-952037626=:860 Content-Type: TEXT/plain; charset=us-ascii On 2 Mar, Bastian wrote: > At 18:06 1.3.2000 -0500, sbertin@mindspring.com wrote: >>On 1 Mar, Bastian wrote: >> > but when i try to start a client (xawtv, gqcam) i always get a >> segmentation >> > fault. >> > dmesg says : >> > >> > ------------- >> > Unable to handle kernel NULL pointer dereference at virtual address >> 0000000c >> >>What do you see just before this? > > THIS is the first line in dmesg (after the lines telling that loading > modules is ok) Sorry, I was expecting more. I did find a case where a NULL pointer dereference would occur if the driver was unable to create the /proc entry for the camera. The attached patch will fix that. Scott J. Bertin sbertin@mindspring.com --1037094400-1804289383-952037626=:860 Content-Type: TEXT/plain; CHARSET=US-ASCII Content-Disposition: attachment; filename="fix_proc.patch" diff -u -r cpia-0.7.2/module/cpia.c cpia/module/cpia.c --- cpia-0.7.2/module/cpia.c Sun Feb 27 14:19:32 2000 +++ cpia/module/cpia.c Thu Mar 2 17:49:33 2000 @@ -1332,11 +1332,12 @@ { char name[7]; - if (!cam->proc_entry) + if (!cam || !cam->proc_entry) return; sprintf(name, "video%d", cam->vdev.minor); remove_proc_entry(name, cpia_proc_root); + cam->proc_entry = NULL; } #if (LINUX_VERSION_CODE < KERNEL_VERSION(2,3,0)) @@ -2525,7 +2526,8 @@ } /* Set ownership of /proc/cpia/videoX to current user */ - cam->proc_entry->uid = current->uid; + if(cam->proc_entry) + cam->proc_entry->uid = current->uid; /* set mark for loading first frame uncompressed */ cam->first_frame = 1; @@ -2548,7 +2550,8 @@ if (cam->ops) { /* Return ownership of /proc/cpia/videoX to root */ - cam->proc_entry->uid = 0; + if(cam->proc_entry) + cam->proc_entry->uid = 0; /* save camera state for later open (developers guide ch 3.5.3) */ save_camera_state(cam); --1037094400-1804289383-952037626=:860-- From c64c128@hotmail.com Thu, 02 Mar 2000 14:55:46 PST Date: Thu, 02 Mar 2000 14:55:46 PST From: Kyle Summers c64c128@hotmail.com Subject: [cpia] Intel Play QX3 Microscope Hello. I know it's been a while since I last posted on this list, but I am pleased to announce that we have made significant progress towards our MacOS USB Intel Play QX3 Microscope driver. Currently our driver properly loads and unloads when the microscope is hotplugged and upplugged into the mac, the driver supports a basic API allowing applications to call a few basic functions, and an application has been created which can call these driver functions (making sure the microscope has not been unplugged and all =). Now, our group would very much like to know the extra commands that control illumination and enable snapshot. It would be really nice to see the lights go on and off when we puch the buttons on our application instead of our driver just SysBeeping happily. If anybody can possibly send us some information on these commands we would be very appreciative. Thanks in advance. Regards, Kyle University of Michigan Department of Computer Science ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com From c64c128@hotmail.com Thu, 02 Mar 2000 14:56:33 PST Date: Thu, 02 Mar 2000 14:56:33 PST From: Kyle Summers c64c128@hotmail.com Subject: [cpia] Intel Play QX3 Microscope Hello. I know it's been a while since I last posted on this list, but I am pleased to announce that we have made significant progress towards our MacOS USB Intel Play QX3 Microscope driver. Currently our driver properly loads and unloads when the microscope is hotplugged and upplugged into the mac, the driver supports a basic API allowing applications to call a few basic functions, and an application has been created which can call these driver functions (making sure the microscope has not been unplugged and all =). Now, our group would very much like to know the extra commands that control illumination and enable snapshot. It would be really nice to see the lights go on and off when we puch the buttons on our application instead of our driver just SysBeeping happily. If anybody can possibly send us some information on these commands we would be very appreciative. Thanks in advance. Regards, Kyle University of Michigan Department of Computer Science ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com From sTYLe@WtAl.De Fri, 03 Mar 2000 01:23:15 +0100 Date: Fri, 03 Mar 2000 01:23:15 +0100 From: Bastian sTYLe@WtAl.De Subject: [cpia] client probs At 17:53 2.3.2000 -0500, sbertin@mindspring.com wrote: >On 2 Mar, Bastian wrote: > > At 18:06 1.3.2000 -0500, sbertin@mindspring.com wrote: > >>On 1 Mar, Bastian wrote: > >> > but when i try to start a client (xawtv, gqcam) i always get a > >> segmentation > >> > fault. > >> > dmesg says : > >> > > >> > ------------- > >> > Unable to handle kernel NULL pointer dereference at virtual address > >> 0000000c > >> > >>What do you see just before this? > > > > THIS is the first line in dmesg (after the lines telling that loading > > modules is ok) > >Sorry, I was expecting more. I did find a case where a NULL pointer >dereference would occur if the driver was unable to create the >/proc entry for the camera. The attached patch will fix that. well, still got : parport0: PC-style at 0x378 (0x778) [SPP,ECP,ECPPS2] Linux video capture interface: v1.00 V4L-Driver for Vision CPiA based cameras v0.7.1 parport0: read2 timeout. parport0: Multimedia device, VLSI Vision Ltd DUAL Camera Parallel port driver for Vision CPiA based cameras v0.7.1 using PIO mode cpia.c(1311818):goto_low_power(2317):10 10 10 10 10 10 10 10 1 camera(s) found Unable to handle kernel NULL pointer dereference at virtual address 0000000c is it correct that there is 0.7.1 although i dl'ed 0.7.2 ??? and someone told me about bugs in the cpia chip's firmware 1-00 ??? fixed is 1-20 ?? i got 1-00.... anyway. at the last possibility i have to switch to windoze. tooooo bad. >Scott J. Bertin >sbertin@mindspring.com > regards, Bastian From Peter.Pregler@risc.uni-linz.ac.at Fri, 03 Mar 2000 08:43:19 +0100 (CET) Date: Fri, 03 Mar 2000 08:43:19 +0100 (CET) From: Peter Pregler Peter.Pregler@risc.uni-linz.ac.at Subject: [cpia] client probs On 03-Mar-2000 Bastian wrote: > > parport0: PC-style at 0x378 (0x778) [SPP,ECP,ECPPS2] > Linux video capture interface: v1.00 > V4L-Driver for Vision CPiA based cameras v0.7.1 > parport0: read2 timeout. > parport0: Multimedia device, VLSI Vision Ltd DUAL Camera > Parallel port driver for Vision CPiA based cameras v0.7.1 > using PIO mode > cpia.c(1311818):goto_low_power(2317):10 10 10 10 10 10 10 10 > 1 camera(s) found > Unable to handle kernel NULL pointer dereference at virtual address > 0000000c That is exactly what I got too with 0.7.1. The goto_low_power failure is important. I will mail a more elaborate oops-trace as soon as I have access to my box at home where the traces are. BTW, Scott forgot to update the version-numbers. So if you downloaded the 0.7.2 tarball and used that it is 0.7.2. I will put out a 0.7.3 with Scotts latest patch in a few minutes to correct this. -Peter ------------------------------- Email: Peter.Pregler@risc.uni-linz.ac.at WWW: http://www.risc.uni-linz.ac.at/people/ppregler From Peter.Pregler@risc.uni-linz.ac.at Fri, 03 Mar 2000 08:56:39 +0100 (CET) Date: Fri, 03 Mar 2000 08:56:39 +0100 (CET) From: Peter Pregler Peter.Pregler@risc.uni-linz.ac.at Subject: [cpia] cpia-0.7.3 Hi, I have updated the wrong version number and incorporated Scotts latest patch for a 0.7.3-version. You find it as always until Jarl catches up at http://www.risc.uni-linz.ac.at/people/ppregler/cpia 2000-03-23 v0.7.3 Patch from Scott J. Bertin - some obscurre null-pointer dereference in case of failed proc-create Patches from Peter Pregler : - fixed version number Enjoy, Peter ------------------------------- Email: Peter.Pregler@risc.uni-linz.ac.at WWW: http://www.risc.uni-linz.ac.at/people/ppregler From Peter.Pregler@risc.uni-linz.ac.at Fri, 03 Mar 2000 09:10:23 +0100 (CET) Date: Fri, 03 Mar 2000 09:10:23 +0100 (CET) From: Peter Pregler Peter.Pregler@risc.uni-linz.ac.at Subject: [cpia] CPiA 0.7.2 & Zoomtel camera: Colour balance strangene On 29-Feb-2000 Johannes Erdfelt wrote: > On Tue, Feb 29, 2000, rich@annexia.org wrote: >> >> Oh, and these problems only really occur in low light conditions >> (with a 60W bulb). In very bright daylight the results are much >> better. Being a hacker I'm obviously mainly interested in the low >> light situation :-) > > FWIW, I've seen this as well. It sometimes is yellowish, or purplish (I > think). Mostly yellow. I have done short tests with the M$-driver and the 0.7.2 driver (parport, kernerl-2.2.14) under low-light conditions. Under M$ the behavior is pretty strange. In the beginning the picture is very dark and very reddish. After a few seconds it does a snap and from one frame to the next it is much brighter. Apparently some correction is triggered. After that it settles down close to the same as the linux result. But the end-result is still way too redish (see my web-page, url in the signature). So my wild guess is that this is a more fundamental problem with the color-correction firmware of the CPiA. Can you post your version information? I have also seen people posting CPiA-versions 1.30. Mine is: CPiA Version: 1.20 (2.0) CPiA PnP-ID: 0553:0002:0100 VP-Version: 1.0 0100 The developers guide does only cover 1.20. So maybe we should ask for an updated document? -Peter ------------------------------- Email: Peter.Pregler@risc.uni-linz.ac.at WWW: http://www.risc.uni-linz.ac.at/people/ppregler From nicolas.roussel@gmd.de Fri, 3 Mar 2000 10:35:27 +0100 (CET) Date: Fri, 3 Mar 2000 10:35:27 +0100 (CET) From: Nicolas Roussel nicolas.roussel@gmd.de Subject: [cpia] ANNOUNCE: videoSpace, a video streaming toolkit for Linux and SGI What VideoSpace is a toolkit for integrating video streams in documents and applications. It consits of a video server and several client applications for the users, and a C++ API for developers. The API allows applications to retrieve and display video from local sources (video hardware or files) as well as networked sources. The new release is called "karnaval"... Where More info: http://www-ihm.lri.fr/~roussel/videoSpace/ Source code: http://www-ihm.lri.fr/~roussel/videoSpace/codebase/ -- ________________________________________________________________________ Nicolas Roussel mailto:nicolas.roussel@gmd.de GMD - FIT.HCI, Schloss Birlinghoven http://www-ihm.lri.fr/~roussel/ 53754 St. Augustin, Germany phone: +49 2241 14-2154 / fax: 14-2065 ________________________________________________________________________ From claudio@helllabs.org Fri, 3 Mar 2000 08:39:23 -0300 (BRT) Date: Fri, 3 Mar 2000 08:39:23 -0300 (BRT) From: Claudio Matsuoka claudio@helllabs.org Subject: [cpia] CPiA 0.7.2 & Zoomtel camera: Colour balance strangene On Fri, 3 Mar 2000, Peter Pregler wrote: > > FWIW, I've seen this as well. It sometimes is yellowish, or purplish (I > > think). Mostly yellow. > > I have done short tests with the M$-driver and the 0.7.2 driver (parport, > kernerl-2.2.14) under low-light conditions. Under M$ the behavior is > pretty strange. In the beginning the picture is very dark and very > reddish. After a few seconds it does a snap and from one frame to the next > it is much brighter. Apparently some correction is triggered. After that > it settles down close to the same as the linux result. But the end-result > is still way too redish (see my web-page, url in the signature). Under low-light conditions (sunlight), my camera at http://helllabs.org tends to grab dark-greenish images. This is a consistent behaviour, I think I never got reddish or yellowish images with this camera. BTW, w3cam just doesn't work here. It grabs a single frame then freezes for a random amount of time. gqcam works just fine, I moved the image acquisition code from gqcam to w3cam and surprisingly the behaviour remains the same. camserv (which is now running at the lab page) works better than w3cam, but freezes at random after a client breaks connection, requiring the server to be restarted. claudio From sTYLe@WtAl.De Fri, 03 Mar 2000 17:44:20 +0100 Date: Fri, 03 Mar 2000 17:44:20 +0100 From: Bastian sTYLe@WtAl.De Subject: [cpia] client probs At 08:43 3.3.2000 +0100, Peter Pregler wrote: >On 03-Mar-2000 Bastian wrote: > > > > parport0: PC-style at 0x378 (0x778) [SPP,ECP,ECPPS2] > > Linux video capture interface: v1.00 > > V4L-Driver for Vision CPiA based cameras v0.7.1 > > parport0: read2 timeout. > > parport0: Multimedia device, VLSI Vision Ltd DUAL Camera > > Parallel port driver for Vision CPiA based cameras v0.7.1 > > using PIO mode > > cpia.c(1311818):goto_low_power(2317):10 10 10 10 10 10 10 10 > > 1 camera(s) found > > Unable to handle kernel NULL pointer dereference at virtual address > > 0000000c > >That is exactly what I got too with 0.7.1. The goto_low_power failure is >important. oh. to prevent misunderstandings, the line Unable to handle[...] is NOT DIRECTLY a result of trying to power low the cam. this line just appears AFTER i started any client app like gqcam or xawtv. >I will mail a more elaborate oops-trace as soon as I have access >to my box at home where the traces are. BTW, Scott forgot to update the >version-numbers. So if you downloaded the 0.7.2 tarball and used that it is >0.7.2. I will put out a 0.7.3 with Scotts latest patch in a few minutes to >correct this. > >-Peter > > >------------------------------- >Email: Peter.Pregler@risc.uni-linz.ac.at >WWW: http://www.risc.uni-linz.ac.at/people/ppregler Bastian From Peter.Pregler@risc.uni-linz.ac.at Fri, 03 Mar 2000 17:47:32 +0100 (CET) Date: Fri, 03 Mar 2000 17:47:32 +0100 (CET) From: Peter Pregler Peter.Pregler@risc.uni-linz.ac.at Subject: [cpia] client probs On 03-Mar-2000 Bastian wrote: > > oh. to prevent misunderstandings, the line Unable to handle[...] is NOT > DIRECTLY > a result of trying to power low the cam. this line just appears AFTER i > started any > client app like gqcam or xawtv. I know, but in my case the power-down failure (and it is a failure, the correct status is not '10 10 ...') _always_ appeared together with the ooops. -Peter ------------------------------- Email: Peter.Pregler@risc.uni-linz.ac.at WWW: http://www.risc.uni-linz.ac.at/people/ppregler From sTYLe@WtAl.De Fri, 03 Mar 2000 18:01:10 +0100 Date: Fri, 03 Mar 2000 18:01:10 +0100 From: Bastian sTYLe@WtAl.De Subject: [cpia] cpia-0.7.3 At 08:56 3.3.2000 +0100, Peter Pregler wrote: >Hi, > >I have updated the wrong version number and incorporated Scotts latest >patch for a 0.7.3-version. You find it as always until Jarl catches up at >http://www.risc.uni-linz.ac.at/people/ppregler/cpia > >2000-03-23 v0.7.3 > > Patch from Scott J. Bertin > - some obscurre null-pointer dereference in case of > failed proc-create still no success with my camera. everything seems to be ok until starting a client to access the cam. so again, AFTER starting gqcam i get the following recorded by syslogd : Mar 3 17:52:14 Little kernel: Unable to handle kernel NULL pointer dereference at virtual address 0000000c Mar 3 17:52:14 Little kernel: current->tss.cr3 = 034c6000, %cr3 = 034c6000 Mar 3 17:52:14 Little kernel: *pde = 00000000 Mar 3 17:52:14 Little kernel: Oops: 0000 Mar 3 17:52:14 Little kernel: CPU: 0 Mar 3 17:52:14 Little kernel: EIP: 0010:[isdn:isdn_ppp_unregister_compressor+334479/258652773] Mar 3 17:52:14 Little kernel: EFLAGS: 00010212 Mar 3 17:52:14 Little kernel: eax: 00000000 ebx: 00032000 ecx: c2d6c000 edx: 00000316 Mar 3 17:52:14 Little kernel: esi: c5884000 edi: c5884000 ebp: 0000001f esp: c2d6df2c Mar 3 17:52:14 Little kernel: ds: 0018 es: 0018 ss: 0018 Mar 3 17:52:14 Little kernel: Process gqcam (pid: 605, process nr: 44, stackpage=c2d6d000) Mar 3 17:52:14 Little kernel: Stack: c586d540 c2445820 c5876f44 00031ba5 c329eeb0 00000000 c586d17f c329eeb0 Mar 3 17:52:14 Little kernel: 00000000 00000000 c35f68a0 c2af6880 00000051 00000000 000000ff c01c0d9c Mar 3 17:52:14 Little kernel: c01e8b20 c01273eb c2af6880 c35f68a0 c35f68a0 00000000 c2af6880 c01261b8 Mar 3 17:52:14 Little kernel: Call Trace: [isdn:isdn_ppp_unregister_compressor+327452/258659800] [isdn:isdn_ppp_unregister_compressor+366880/258620372] [isdn:isdn_ppp_unregister_compressor+326491/258660761] [tvecs+10012/13216] [chrdev_open+63/76] [filp_open+172/240] [sys_open+82/172] Mar 3 17:52:14 Little kernel: [system_call+52/56] Mar 3 17:52:14 Little kernel: Code: 8b 40 0c 8b 14 90 85 d2 74 3b 81 e2 00 f0 ff ff 89 f8 c1 e8 weird to me are thoses isdn entries !? if you need more information then let me know. (btw the camera is ok, tested it under windoze) > Patches from Peter Pregler : > - fixed version number > > >Enjoy, Peter > > >_______________________________________________ >cpia mailing list - cpia@risc.uni-linz.ac.at >http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia Regards, Bastian From claudio@helllabs.org Fri, 3 Mar 2000 14:14:20 -0300 (BRT) Date: Fri, 3 Mar 2000 14:14:20 -0300 (BRT) From: Claudio Matsuoka claudio@helllabs.org Subject: [cpia] cpia-0.7.3 On Fri, 3 Mar 2000, Bastian wrote: > EIP: 0010:[isdn:isdn_ppp_unregister_compressor+334479/258652773] > [isdn:isdn_ppp_unregister_compressor+327452/258659800] > [isdn:isdn_ppp_unregister_compressor+366880/258620372] > [isdn:isdn_ppp_unregister_compressor+326491/258660761] [tvecs+10012/13216] > > weird to me are thoses isdn entries !? Do you have an up to date System.map in /boot? claudio From jerdfelt@sventech.com Fri, 3 Mar 2000 12:11:46 -0500 Date: Fri, 3 Mar 2000 12:11:46 -0500 From: Johannes Erdfelt jerdfelt@sventech.com Subject: [cpia] cpia-0.7.3 On Fri, Mar 03, 2000, Claudio Matsuoka wrote: > > On Fri, 3 Mar 2000, Bastian wrote: > > > EIP: 0010:[isdn:isdn_ppp_unregister_compressor+334479/258652773] > > [isdn:isdn_ppp_unregister_compressor+327452/258659800] > > [isdn:isdn_ppp_unregister_compressor+366880/258620372] > > [isdn:isdn_ppp_unregister_compressor+326491/258660761] [tvecs+10012/13216] > > > > weird to me are thoses isdn entries !? > > Do you have an up to date System.map in /boot? ksymoops doesn't use System.map for modules since they can be loaded anywhere in memory. It will tell you where it's getting it's information (at the top) in recent versions. More importantly, those offsets are entirely too high. I'm sure the ISDN unregister function is not that large. I bet you it can't find the cpia.o and cpia_pp.o modules. Throw them into /lib/modules/`uname -r`/misc and try again. JE From sTYLe@WtAl.De Fri, 03 Mar 2000 18:13:00 +0100 Date: Fri, 03 Mar 2000 18:13:00 +0100 From: Bastian sTYLe@WtAl.De Subject: [cpia] cpia-0.7.3 At 14:14 3.3.2000 -0300, Claudio Matsuoka wrote: >On Fri, 3 Mar 2000, Bastian wrote: > > > EIP: 0010:[isdn:isdn_ppp_unregister_compressor+334479/258652773] > > [isdn:isdn_ppp_unregister_compressor+327452/258659800] > > [isdn:isdn_ppp_unregister_compressor+366880/258620372] > > [isdn:isdn_ppp_unregister_compressor+326491/258660761] [tvecs+10012/13216] > > > > weird to me are thoses isdn entries !? > >Do you have an up to date System.map in /boot? > yes, the one just compiled with 2.2.14. >claudio Bastian From sTYLe@WtAl.De Fri, 03 Mar 2000 18:24:39 +0100 Date: Fri, 03 Mar 2000 18:24:39 +0100 From: Bastian sTYLe@WtAl.De Subject: [cpia] cpia-0.7.3 At 12:11 3.3.2000 -0500, Johannes Erdfelt wrote: >On Fri, Mar 03, 2000, Claudio Matsuoka wrote: > > > > On Fri, 3 Mar 2000, Bastian wrote: > > > > > EIP: 0010:[isdn:isdn_ppp_unregister_compressor+334479/258652773] > > > [isdn:isdn_ppp_unregister_compressor+327452/258659800] > > > [isdn:isdn_ppp_unregister_compressor+366880/258620372] > > > [isdn:isdn_ppp_unregister_compressor+326491/258660761] > [tvecs+10012/13216] > > > > > > weird to me are thoses isdn entries !? > > > > Do you have an up to date System.map in /boot? > >ksymoops doesn't use System.map for modules since they can be loaded >anywhere in memory. > >It will tell you where it's getting it's information (at the top) in >recent versions. > >More importantly, those offsets are entirely too high. I'm sure the ISDN >unregister function is not that large. > >I bet you it can't find the cpia.o and cpia_pp.o modules. Throw them >into /lib/modules/`uname -r`/misc and try again. that's the place where they always have been. the modules seem to be loaded properly : Module Size Used by parport_probe 2980 0 (autoclean) cpia_pp 18712 0 cpia 48604 0 [cpia_pp] videodev 2368 1 [cpia] parport_pc 7232 1 [cpia_pp] parport 7272 1 [parport_probe cpia_pp parport_pc] ip_masq_irc 1360 0 (unused) ip_masq_raudio 2736 0 (unused) ip_masq_ftp 2352 0 (unused) ne 6560 1 (autoclean) 8390 6628 0 (autoclean) [ne] hisax 125480 3 isdn 85312 4 [hisax] >JE Bastian From tadavis@lbl.gov Fri, 03 Mar 2000 10:19:48 -0800 Date: Fri, 03 Mar 2000 10:19:48 -0800 From: Thomas Davis tadavis@lbl.gov Subject: [cpia] CPiA 0.7.2 & Zoomtel camera: Colour balance strangene This is a multi-part message in MIME format. --------------E125F4922989C0FC442E0310 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Peter Pregler wrote: > it is much brighter. Apparently some correction is triggered. After that > it settles down close to the same as the linux result. But the end-result > is still way too redish (see my web-page, url in the signature). So my > wild guess is that this is a more fundamental problem with the > color-correction firmware of the CPiA. Can you post your version > information? I have also seen people posting CPiA-versions > 1.30. Mine is: > > CPiA Version: 1.20 (2.0) > CPiA PnP-ID: 0553:0002:0100 > VP-Version: 1.0 0100 > > The developers guide does only cover 1.20. So maybe we should ask for an > updated document? > Interesting. I've got a v1.20 (2.10) camera, and I get the yellowish values no matter what I do. It's from ezonics. I've attached the /proc/cpia/video0 file. -- ------------------------+-------------------------------------------------- Thomas Davis | PDSF Project Leader tadavis@lbl.gov | (510) 486-4524 | "Only a petabyte of data this year?" --------------E125F4922989C0FC442E0310 Content-Type: text/plain; charset=us-ascii; name="cpia.proc.txt" Content-Disposition: inline; filename="cpia.proc.txt" Content-Transfer-Encoding: 7bit read-only ----------------------- CPIA Version: 1.30 (2.10) CPIA PnP-ID: 0553:0002:0100 VP-Version: 1.0 0100 system_state: 0x03 grab_state: 0x38 stream_state: 0x00 fatal_error: 0x00 cmd_error: 0x00 debug_flags: 0x00 vp_status: 0xe0 error_code: 0x02 video_size: CIF sub_sample: 422 yuv_order: YUYV roi: ( 0, 0) to (352, 288) actual_fps: 14 transfer_rate: 60kB/s read-write ----------------------- current min max default comment brightness: 50 0 100 50 contrast: 48 0 96 48 steps of 8 saturation: 50 0 100 50 sensor_fps: 15.000 3 30 15 stream_start_line: 240 0 288 240 ecp_timing: normal slow normal normal color_balance_mode: auto manual auto auto red_gain: 5 0 212 32 green_gain: 3 0 212 6 blue_gain: 212 0 212 92 max_gain: 2 1,2,4,8 2 exposure_mode: auto manual auto auto centre_weight: on off on on gain: 1 1 max_gain 1 1,2,4,8 possible fine_exp: 236 0 511 0 coarse_exp: 4 0 65535 185 red_comp: 0 220 255 220 green1_comp: 0 214 255 214 green2_comp: 192 214 255 214 blue_comp: 128 230 255 230 apcor_gain1: 0x1c 0x0 0xff 0x1c apcor_gain2: 0x1a 0x0 0xff 0x1a apcor_gain4: 0x2d 0x0 0xff 0x2d apcor_gain8: 0x2a 0x0 0xff 0x2a vl_offset_gain1: 24 0 255 24 vl_offset_gain2: 28 0 255 28 vl_offset_gain4: 30 0 255 30 vl_offset_gain8: 30 0 255 30 flicker_control: off off on off mains_frequency: 50 50 60 50 only 50/60 allowable_overexposure: 0 0 255 0 compression_mode: auto none,auto,manual auto decimation_enable: off off off off compression_target: quality framerate quality quality target_framerate: 7 0 30 7 target_quality: 10 0 255 10 y_threshold: 15 0 31 15 uv_threshold: 15 0 31 15 hysteresis: 3 0 255 3 threshold_max: 11 0 255 11 small_step: 1 0 255 1 large_step: 3 0 255 3 decimation_hysteresis: 2 0 255 2 fr_diff_step_thresh: 5 0 255 5 q_diff_step_thresh: 3 0 255 3 decimation_thresh_mod: 2 0 255 2 --------------E125F4922989C0FC442E0310-- From Peter.Pregler@risc.uni-linz.ac.at Sat, 04 Mar 2000 17:22:05 +0100 (CET) Date: Sat, 04 Mar 2000 17:22:05 +0100 (CET) From: Peter Pregler Peter.Pregler@risc.uni-linz.ac.at Subject: [cpia] CPiA 0.7.2 & Zoomtel camera: Colour balance strangene On 03-Mar-2000 Thomas Davis wrote: > Peter Pregler wrote: >> it is much brighter. Apparently some correction is triggered. After that >> it settles down close to the same as the linux result. But the end-result >> is still way too redish (see my web-page, url in the signature). So my >> wild guess is that this is a more fundamental problem with the >> color-correction firmware of the CPiA. Can you post your version >> information? I have also seen people posting CPiA-versions >> 1.30. Mine is: >> >> CPiA Version: 1.20 (2.0) >> CPiA PnP-ID: 0553:0002:0100 >> VP-Version: 1.0 0100 >> >> The developers guide does only cover 1.20. So maybe we should ask for an >> updated document? >> > > Interesting. I've got a v1.20 (2.10) camera, and I get the yellowish > values no matter what I do. Hmmm, I read 1.30 as CPiA-version in your attachment. Where do you take that 1.20 value from? -Peter ------------------------------- Even the thought that a ship was waiting to take him back to Earth did not wipe out the sense of loss he felt at that moment. ------------------------------- Email: Peter.Pregler@risc.uni-linz.ac.at Peter Pregler / RISC, University of Linz, Austria From tadavis@lbl.gov Sat, 04 Mar 2000 08:48:26 -0800 Date: Sat, 04 Mar 2000 08:48:26 -0800 From: Thomas Davis tadavis@lbl.gov Subject: [cpia] CPiA 0.7.2 & Zoomtel camera: Colour balance strangene Peter Pregler wrote: > > > > Interesting. I've got a v1.20 (2.10) camera, and I get the yellowish > > values no matter what I do. > > Hmmm, I read 1.30 as CPiA-version in your attachment. Where do you take that > 1.20 value from? > Typo. Brain Fart. Bad Fingers. It's a v1.30 camera. From dirk@lison.com Sat, 04 Mar 2000 12:33:49 -0500 Date: Sat, 04 Mar 2000 12:33:49 -0500 From: Dirk Lison dirk@lison.com Subject: [cpia] CPiA 0.7.2 & Zoomtel camera: Colour balance strangene I'm having color problems with my Ezonics EZCams too even in bright light. But only using gqcam. Using vidcat from the w3cam package results always in correct colors but the pics are very dark in low light conditions. Hope this helps. Camera info from gqcam: Name: CPiA USB Camera Type: 513 Can capture Can capture subareas of the image Channels: 1 Audios: 0 Maxwidth: 352 Maxheight: 288 Minwidth: 8 Minheight: 4 --------- X: 0 Y: 0 Width: 352 Height: 288 Chromakey: 0 Flags: 30 --------- Brightness: 46080 (180) Hue: 32768 (128) Color: 32768 (128) Contrast: 49152 (192) Whiteness: 26880 (105) Depth: 24 Palette: 4 Dirk Peter Pregler wrote: > > On 03-Mar-2000 Thomas Davis wrote: > > Peter Pregler wrote: > >> it is much brighter. Apparently some correction is triggered. After that > >> it settles down close to the same as the linux result. But the end-result > >> is still way too redish (see my web-page, url in the signature). So my > >> wild guess is that this is a more fundamental problem with the > >> color-correction firmware of the CPiA. Can you post your version > >> information? I have also seen people posting CPiA-versions > >> 1.30. Mine is: > >> > >> CPiA Version: 1.20 (2.0) > >> CPiA PnP-ID: 0553:0002:0100 > >> VP-Version: 1.0 0100 > >> > >> The developers guide does only cover 1.20. So maybe we should ask for an > >> updated document? > >> > > > > Interesting. I've got a v1.20 (2.10) camera, and I get the yellowish > > values no matter what I do. > > Hmmm, I read 1.30 as CPiA-version in your attachment. Where do you take that > 1.20 value from? > > -Peter > > ------------------------------- > Even the thought that a ship was waiting to take him back to Earth > did not wipe out the sense of loss he felt at that moment. > ------------------------------- > Email: Peter.Pregler@risc.uni-linz.ac.at > Peter Pregler / RISC, University of Linz, Austria > > _______________________________________________ > cpia mailing list - cpia@risc.uni-linz.ac.at > http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia From rich@annexia.org Sat, 4 Mar 2000 18:22:15 +0000 Date: Sat, 4 Mar 2000 18:22:15 +0000 From: rich@annexia.org rich@annexia.org Subject: [cpia] CPiA 0.7.2 & Zoomtel camera: Colour balance strangene On Fri, Mar 03, 2000 at 09:10:23AM +0100, Peter Pregler wrote: > I have done short tests with the M$-driver and the 0.7.2 driver (parport, > kernerl-2.2.14) under low-light conditions. Under M$ the behavior is > pretty strange. In the beginning the picture is very dark and very > reddish. After a few seconds it does a snap and from one frame to the next > it is much brighter. Apparently some correction is triggered. After that > it settles down close to the same as the linux result. But the end-result > is still way too redish (see my web-page, url in the signature). So my > wild guess is that this is a more fundamental problem with the > color-correction firmware of the CPiA. Can you post your version > information? I have also seen people posting CPiA-versions > 1.30. Mine is: > > CPiA Version: 1.20 (2.0) > CPiA PnP-ID: 0553:0002:0100 > VP-Version: 1.0 0100 I've not used the Windows drivers (don't have Windows), so I can't comment on whether or not the camera works under Windows or not. Anyway, here's my version numbers: Feb 29 20:03:51 arctor kernel: USB CPiA camera found Feb 29 20:03:52 arctor kernel: CPiA Version: 1.30 (2.10) Feb 29 20:03:52 arctor kernel: CPiA PnP-ID: 0553:0002:0100 Feb 29 20:03:52 arctor kernel: VP-Version: 1.0 0100 (It's a brand new camera). Is there a way to upgrade the firmware on these cameras? Rich. -- rich@annexia.org | Is your school part of http://www.schoolmaster.net ? BiblioTech Ltd, Unit 2 Piper Centre, 50 Carnwath Road, London, SW6 3EG. +44 20 7384 6917 | Click here to play XRacer: http://xracer.annexia.org Copyright © 2000 Richard Jones | GnuPG/PGP key from www.annexia.org From jack_diederich@email.com Sat, 4 Mar 2000 14:11:12 -0500 (EST) Date: Sat, 4 Mar 2000 14:11:12 -0500 (EST) From: Jack Diederich jack_diederich@email.com Subject: [cpia] modified gqcam source avail Long time lurker, first time poster. I noticed alot of you use gqcam, for those that want to be on the cutting edge, you can find a hacked version heregqcam-0.6+.tar.gz. The server is on a cable modem, so the upstream isn't great but it should be OK. If I screwed up the link, just go to the host, there is a link to the source from the homepage. I've been trading emails with the author, and at least some of the changes will go into the next release of gqcam. The basic change is that now gqcam is multi threaded, so at the same time an image is being displayed, another thread is grabbing an image. On my EZcam, this means I can get 30 frames per second (when there is no motion, of course) and about 15 fps when there is alot of activity. There is a little status box in the software that displays the fps from the last second, as well as a running average for the whole session. I think I've licked all the deadlocks, but if you find any please let me know. To get over 15 fps you have to change the sensor_fps value to something higher (like the max). The CPU load is about 40% on my PIII 500Mhz, half in gqcam/X and half in the driver. That said, I have a couple random questions. my setup: kernel 2.3.48, cpia 7.1, Ezonics EZcam CPiA ver 1.30 (2.10) 1) I can't unload my cpia module, which means I have to reboot anytime I change the driver, does anyone else have this problem or know of a solution? I can unload cpia_usb.o, but not cpia.o 2) Where does the DBG() output go? /var/log/message? 3) None of the hue/color/brightness/image size ioctls succeed, is this normal? (I was trying to track it down w/ DBG message) 4) When I crank the sensor_fps to 30, and the target_fps to 30, /proc/cpia/video0 reports that the camera actual_fps is 128 fps, I'm guessing this is a bug -john smallberries ----------------------------------------------- FREE! The World's Best Email Address @email.com Reserve your name now at http://www.email.com From Peter.Pregler@risc.uni-linz.ac.at Sun, 05 Mar 2000 00:03:53 +0100 (CET) Date: Sun, 05 Mar 2000 00:03:53 +0100 (CET) From: Peter Pregler Peter.Pregler@risc.uni-linz.ac.at Subject: [cpia] modified gqcam source avail On 04-Mar-2000 Jack Diederich wrote: > > 2) Where does the DBG() output go? /var/log/message? Depends on your syslog.conf. It is a normal printk with priority KERNEL_DEBUG. So something like the line below in syslog.conf should catch it (and all other kernel-stuff): kern.* -/var/log/kern.log > 3) None of the hue/color/brightness/image size ioctls succeed, > is this normal? (I was trying to track it down w/ DBG message) Nope, hardly a bug with the driver. AFAIK, it workes for the gqcam-port shipped with the driver. Did you compare the ioctls used. My suggestion: do a read-ioctl and change only the respective value. That should succeed. -Peter ------------------------------- Even the thought that a ship was waiting to take him back to Earth did not wipe out the sense of loss he felt at that moment. ------------------------------- Email: Peter.Pregler@risc.uni-linz.ac.at Peter Pregler / RISC, University of Linz, Austria From rich@annexia.org Sun, 5 Mar 2000 14:25:44 +0000 Date: Sun, 5 Mar 2000 14:25:44 +0000 From: rich@annexia.org rich@annexia.org Subject: [cpia] CPiA colour balance problem [patch] --KsGdsel6WgEHnImy Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Dear developers: I've had a deeper look at the CPiA colour balance / 1.3 firmware problem, with respect to the developer documentation provided by Vision. My analysis is that there appear to be two unrelated bugs here. Firstly, with reference to section 2.4.4 in developer.pdf, it states that the SetColourBalance command BalanceMode argument has four possible values: BalanceMode Function ------------------------------------------------------------------- 0 No effect. 1 Set the red_gain, blue_gain, green_gain parameters. According to the documentation, this has *no effect* on whether colour_balance_mode is enabled or disabled. 2 Enable auto colour_balance_mode algorithm. The red_gain, blue_gain and green_gain parameters appear to be *ignored*. 3 Disable auto colour_balance_mode algorithm. The red_gain, blue_gain and green_gain parameters appear to be *ignored*. Now that's not exactly what the CPiA version 0.7.1 driver was doing. Attached is a patch which makes the driver do what the documentation says it should. The patch is against 0.7.1. Secondly, there must be a bug in the camera firmware (!). The yellow hue which I found seems to come from the fact that when you switch the camera into automatic mode, about 90% of the time, the camera adjusts the blue_gain parameter so it increases and increases up to 212 (where it stops). However, instead of giving this a blue hue, it seems to just ignore the blue channel altogether ... This results in only the red+green channels being displayed => a yellow picture :-( What's strange here is obviously the fact that blue_gain goes AWOL like this. Clearly there's an actual problem with the blue channel, and the camera itself things that it's getting no signal from that channel. Rich. -- rich@annexia.org | Is your school part of http://www.schoolmaster.net ? BiblioTech Ltd, Unit 2 Piper Centre, 50 Carnwath Road, London, SW6 3EG. +44 20 7384 6917 | Click here to play XRacer: http://xracer.annexia.org Copyright © 2000 Richard Jones | GnuPG/PGP key from www.annexia.org --KsGdsel6WgEHnImy Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="cpia-cb-fix.patch" diff -ur cpia-0.7.1/module/cpia.c cpia-0.7.1-cb-fix/module/cpia.c --- cpia-0.7.1/module/cpia.c Mon Feb 7 08:53:28 2000 +++ cpia-0.7.1-cb-fix/module/cpia.c Sun Mar 5 14:11:14 2000 @@ -411,17 +411,10 @@ cam->params.ecpTiming ? "slow" : "normal", "slow", "normal", "normal"); - switch(cam->params.colourBalance.balanceMode) { - case 1: - // FIXME case 3: - sprintf(tmpstr, "manual"); - break; - case 2: + if (cam->params.colourBalance.balanceModeIsAuto) { sprintf(tmpstr, "auto"); - break; - default: - sprintf(tmpstr, "unknown"); - break; + } else { + sprintf(tmpstr, "manual"); } out += sprintf(out, "color_balance_mode: %8s %8s %8s" " %8s\n", tmpstr, "manual", "auto", "auto"); @@ -759,11 +752,11 @@ if(!retval && MATCH("manual")) { buffer += len; count -= len; - new_params.colourBalance.balanceMode=1; + new_params.colourBalance.balanceModeIsAuto=0; } else if(!retval && MATCH("auto")) { buffer += len; count -= len; - new_params.colourBalance.balanceMode=2; + new_params.colourBalance.balanceModeIsAuto=1; } else { retval = -EINVAL; } @@ -2086,11 +2079,18 @@ cam->params.exposure.blueComp); } if( cam->cmd_queue & COMMAND_SETCOLOURBALANCE ) { - do_command(cam, CPIA_COMMAND_SetColourBalance, - cam->params.colourBalance.balanceMode, - cam->params.colourBalance.redGain, - cam->params.colourBalance.greenGain, - cam->params.colourBalance.blueGain); + if (cam->params.colourBalance.balanceModeIsAuto) { + do_command(cam, CPIA_COMMAND_SetColourBalance, + 2, 0, 0, 0); + } else { + do_command(cam, CPIA_COMMAND_SetColourBalance, + 1, + cam->params.colourBalance.redGain, + cam->params.colourBalance.greenGain, + cam->params.colourBalance.blueGain); + do_command(cam, CPIA_COMMAND_SetColourBalance, + 3, 0, 0, 0); + } } if( cam->cmd_queue & COMMAND_SETSENSORFPS ) { do_command(cam, CPIA_COMMAND_SetSensorFPS, @@ -2308,15 +2308,18 @@ static void set_camera_state(struct cam_data *cam) { - if(cam->params.colourBalance.balanceMode != 1) { + if(cam->params.colourBalance.balanceModeIsAuto) { + do_command(cam, CPIA_COMMAND_SetColourBalance, + 2, 0, 0, 0); + } else { do_command(cam, CPIA_COMMAND_SetColourBalance, 1, cam->params.colourBalance.redGain, cam->params.colourBalance.greenGain, cam->params.colourBalance.blueGain); + do_command(cam, CPIA_COMMAND_SetColourBalance, + 3, 0, 0, 0); } - if(cam->params.colourBalance.balanceMode == 0) - cam->params.colourBalance.balanceMode = 2; do_command_extended(cam, CPIA_COMMAND_SetExposure, cam->params.exposure.gainMode, 1, 1, @@ -3063,7 +3066,7 @@ cam->params.exposure.green1Comp = 214; cam->params.exposure.green2Comp = 214; cam->params.exposure.blueComp = 230; - cam->params.colourBalance.balanceMode = 2; /* auto color balance */ + cam->params.colourBalance.balanceModeIsAuto = 1; cam->params.colourBalance.redGain = 32; cam->params.colourBalance.greenGain = 6; cam->params.colourBalance.blueGain = 92; diff -ur cpia-0.7.1/module/cpia.h cpia-0.7.1-cb-fix/module/cpia.h --- cpia-0.7.1/module/cpia.h Mon Feb 7 08:53:28 2000 +++ cpia-0.7.1-cb-fix/module/cpia.h Sun Mar 5 14:01:19 2000 @@ -150,7 +150,7 @@ u8 blueComp; } exposure; struct { - u8 balanceMode; + u8 balanceModeIsAuto; u8 redGain; u8 greenGain; u8 blueGain; --KsGdsel6WgEHnImy-- From rich@annexia.org Sun, 5 Mar 2000 14:58:56 +0000 Date: Sun, 5 Mar 2000 14:58:56 +0000 From: rich@annexia.org rich@annexia.org Subject: [cpia] CPiA colour balance problem [patch] --uAKRQypu60I7Lcqm Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit On Sun, Mar 05, 2000 at 02:25:44PM +0000, rich@annexia.org wrote: [...] By popular demand, I've updated the patch to be against version 0.7.3 of the CPiA driver. Rich. -- rich@annexia.org | Is your school part of http://www.schoolmaster.net ? BiblioTech Ltd, Unit 2 Piper Centre, 50 Carnwath Road, London, SW6 3EG. +44 20 7384 6917 | Click here to play XRacer: http://xracer.annexia.org Copyright © 2000 Richard Jones | GnuPG/PGP key from www.annexia.org --uAKRQypu60I7Lcqm Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="cpia-cb-fix.patch" diff -ur cpia-0.7.3/module/cpia.c cpia-0.7.3-cb-fix/module/cpia.c --- cpia-0.7.3/module/cpia.c Fri Mar 3 07:44:09 2000 +++ cpia-0.7.3-cb-fix/module/cpia.c Sun Mar 5 14:54:55 2000 @@ -419,17 +419,10 @@ cam->params.ecpTiming ? "slow" : "normal", "slow", "normal", "normal"); - switch(cam->params.colourBalance.balanceMode) { - case 1: - // FIXME case 3: - sprintf(tmpstr, "manual"); - break; - case 2: + if (cam->params.colourBalance.balanceModeIsAuto) { sprintf(tmpstr, "auto"); - break; - default: - sprintf(tmpstr, "unknown"); - break; + } else { + sprintf(tmpstr, "manual"); } out += sprintf(out, "color_balance_mode: %8s %8s %8s" " %8s\n", tmpstr, "manual", "auto", "auto"); @@ -763,9 +756,9 @@ command_flags |= COMMAND_SETECPTIMING; } else if (MATCH("color_balance_mode")) { if (!retval && MATCH("manual")) - new_params.colourBalance.balanceMode=1; + new_params.colourBalance.balanceModeIsAuto = 0; else if (!retval && MATCH("auto")) - new_params.colourBalance.balanceMode=2; + new_params.colourBalance.balanceModeIsAuto = 1; else retval = -EINVAL; @@ -2102,12 +2095,20 @@ cam->params.exposure.green2Comp, cam->params.exposure.blueComp); - if (cam->cmd_queue & COMMAND_SETCOLOURBALANCE) - do_command(cam, CPIA_COMMAND_SetColourBalance, - cam->params.colourBalance.balanceMode, - cam->params.colourBalance.redGain, - cam->params.colourBalance.greenGain, - cam->params.colourBalance.blueGain); + if (cam->cmd_queue & COMMAND_SETCOLOURBALANCE) { + if (cam->params.colourBalance.balanceModeIsAuto) { + do_command(cam, CPIA_COMMAND_SetColourBalance, + 2, 0, 0, 0); + } else { + do_command(cam, CPIA_COMMAND_SetColourBalance, + 1, + cam->params.colourBalance.redGain, + cam->params.colourBalance.greenGain, + cam->params.colourBalance.blueGain); + do_command(cam, CPIA_COMMAND_SetColourBalance, + 3, 0, 0, 0); + } + } if (cam->cmd_queue & COMMAND_SETSENSORFPS) do_command(cam, CPIA_COMMAND_SetSensorFPS, @@ -2340,16 +2341,19 @@ static void set_camera_state(struct cam_data *cam) { - if (cam->params.colourBalance.balanceMode != 1) { + if(cam->params.colourBalance.balanceModeIsAuto) { + do_command(cam, CPIA_COMMAND_SetColourBalance, + 2, 0, 0, 0); + } else { do_command(cam, CPIA_COMMAND_SetColourBalance, 1, cam->params.colourBalance.redGain, cam->params.colourBalance.greenGain, cam->params.colourBalance.blueGain); + do_command(cam, CPIA_COMMAND_SetColourBalance, + 3, 0, 0, 0); } - if (!cam->params.colourBalance.balanceMode) - cam->params.colourBalance.balanceMode = 2; do_command_extended(cam, CPIA_COMMAND_SetExposure, cam->params.exposure.gainMode, 1, 1, @@ -3105,7 +3109,7 @@ cam->params.exposure.green1Comp = 214; cam->params.exposure.green2Comp = 214; cam->params.exposure.blueComp = 230; - cam->params.colourBalance.balanceMode = 2; /* auto color balance */ + cam->params.colourBalance.balanceModeIsAuto = 1; cam->params.colourBalance.redGain = 32; cam->params.colourBalance.greenGain = 6; cam->params.colourBalance.blueGain = 92; diff -ur cpia-0.7.3/module/cpia.h cpia-0.7.3-cb-fix/module/cpia.h --- cpia-0.7.3/module/cpia.h Fri Mar 3 07:44:23 2000 +++ cpia-0.7.3-cb-fix/module/cpia.h Sun Mar 5 14:52:05 2000 @@ -150,7 +150,7 @@ u8 blueComp; } exposure; struct { - u8 balanceMode; + u8 balanceModeIsAuto; u8 redGain; u8 greenGain; u8 blueGain; --uAKRQypu60I7Lcqm-- From rich@annexia.org Sun, 5 Mar 2000 15:04:43 +0000 Date: Sun, 5 Mar 2000 15:04:43 +0000 From: rich@annexia.org rich@annexia.org Subject: [cpia] CPiA colour balance problem [patch] It turns out that the second part of the problem (I accused a bug in the firmware, if you recall) may well not actually be a problem with the camera :-) I looked closely at what was being returned from the GetExposure call, and the values being returned appear to be completely bogus. For example: $ grep '_comp' /proc/cpia/video0 red_comp: 0 220 255 220 green1_comp: 0 214 255 214 green2_comp: 192 214 255 214 blue_comp: 128 230 255 230 and also with debugging turned on in the kernel: Mar 5 14:59:17 arctor kernel: usb.c: cpia driver claimed interface d3f6f440 Mar 5 15:00:25 arctor kernel: cpia.c(49441230):goto_low_power(2315):camera now in LOW power state Mar 5 15:00:25 arctor kernel: cpia.c(49441239):goto_high_power(2301):camera now in HIGH power state Mar 5 15:00:26 arctor kernel: cpia.c(49441252):dispatch_commands(2032):1 1 0 0 1 1 1 1 Mar 5 15:00:26 arctor kernel: cpia.c(49441252):dispatch_commands(2033):0 1 1 1 1 1 0 1 Mar 5 15:00:26 arctor kernel: cpia.c(49441257):save_camera_state(2335):1/0/0/1/0/0/192/128 Note that the values printed out for red_comp, green?_comp and blue_comp in save_camera_state are wrong. Any ideas? These seem to be read straight from the camera. Rich. -- rich@annexia.org | Is your school part of http://www.schoolmaster.net ? BiblioTech Ltd, Unit 2 Piper Centre, 50 Carnwath Road, London, SW6 3EG. +44 20 7384 6917 | Click here to play XRacer: http://xracer.annexia.org Copyright © 2000 Richard Jones | GnuPG/PGP key from www.annexia.org From bas@brijn.nu Sun, 05 Mar 2000 21:49:37 +0100 Date: Sun, 05 Mar 2000 21:49:37 +0100 From: Bas Rijniersce bas@brijn.nu Subject: [cpia] Simple webcam perl script Hi, Created it for my own use, but might be useful to others: a small perl script that uses vidcat to get a picture from the cam, then uses convert to add some text and date and time. Have a look at http://www.brijn.nu/Programming/ Bas ---- Bas Rijniersce Phone +31 341 550545 Oude Telgterweg 81 Fax +31 341 562940 3851 EA Ermelo http://www.brijn.nu The Netherlands bas@brijn.nu From Peter.Pregler@risc.uni-linz.ac.at Sun, 05 Mar 2000 23:08:25 +0100 (CET) Date: Sun, 05 Mar 2000 23:08:25 +0100 (CET) From: Peter Pregler Peter.Pregler@risc.uni-linz.ac.at Subject: [cpia] patch for cpia_pp.c - free_dma was missing and some comments on the '10 10' This message is in MIME format --_=XFMail.1.4.4.Linux:20000305230825:1773=_ Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Hi, I think I have found the reason for the oopses _I_ encountered. Apparently during the restructure of the init-process to adapt for usb the DMA-ifdef t= hat freed the registered DMA vanished in cpia_pp.c. This leads to very strange oopses if one tries to load cpia_pp twice. I have attached the patch. This should solve problems of the sort 'cannot reload cpia_pp if dma was used'. I don't think it is a solution for the '10 10 10 ...' problem. Actually, I = am not able to reproduce that one. I think I have to fetch a new 2.3-kernel fi= rst. The problem must be in reset_camera, the first goto_low_power at the beginn= ing of the function. Could someone with a not-working camera play around with t= hat initalisation ('see the trial-and-error comment') a bit. The developers gui= de does say nothing about what to do if we read '10 10'-garbage from the camer= a. As for the segfault I got in the '10 10'-case I think I have found the reas= on. Can anyone comment about the following change of return values. The functio= n in question is cpia_register_camera. Someone changed the return values ENXIO (maybe EIO would have been better) to success??? Here is 0.5.0 /* get version information from camera: open/reset/close */ /* open cpia */ if (camera[i]->ops->open(camera[i]->index, &camera[i]->lowlevel_dat= a)) { return -ENXIO; } =20 /* reset the camera */ if(reset_camera(camera[i]) !=3D 0) { camera[i]->ops->close(camera[i]->lowlevel_data); return -ENXIO; } /* close cpia */ camera[i]->ops->close(camera[i]->lowlevel_data); And here is the latest 0.7.3: /* get version information from camera: open/reset/close */ /* open cpia */ if (camera->ops->open(camera->lowlevel_data)) return camera; =20 /* reset the camera */ if (reset_camera(camera) !=3D 0) { camera->ops->close(camera->lowlevel_data); return camera; } /* close cpia */ camera->ops->close(camera->lowlevel_data); If the open/reset of the camera fails there is not much reason to report success. Actually I am pretty sure that is a road to hell, i.e. segmentatio= n faults and the like. IMHO the register of the device must fail if the open/reset fails. -Peter ------------------------------- Even the thought that a ship was waiting to take him back to Earth did not wipe out the sense of loss he felt at that moment. ------------------------------- Email: Peter.Pregler@risc.uni-linz.ac.at Peter Pregler / RISC, University of Linz, Austria --_=XFMail.1.4.4.Linux:20000305230825:1773=_ Content-Disposition: attachment; filename="dma-free-patch" Content-Description: dma-free-patch Content-Type: text/plain; charset=iso-8859-1; name=dma-free-patch; SizeOnDisk=866 Content-Transfer-Encoding: base64 LS0tIGNwaWFfcHAuYy5vcmlnCVN1biBNYXIgIDUgMjI6Mjk6NTIgMjAwMAorKysgY3BpYV9wcC5j CVN1biBNYXIgIDUgMjI6MjU6MjAgMjAwMApAQCAtMTUxNiw3ICsxNTE2LDcgQEAKIAkJY2FtLT5k bWFfYnVmPWttYWxsb2MoRE1BX0JVRkZFUl9TSVpFLCBHRlBfRE1BKTsKIAkJaWYoY2FtLT5kbWFf YnVmID09IE5VTEwpIHsKIAkJCWZyZWVfZG1hKGNhbS0+cGRldi0+cG9ydC0+ZG1hKTsKLQkJCUxP RygiZmFpbGVkIHRvIGFsbG9jYXRlIGRtYSBidWZmZXIsIHVzaW5nIEZJRk8gbW9kZVxuIik7CisJ CQlMT0coImZhaWxlZCB0byBhbGxvY2F0ZSBkbWEgYnVmZmVyLCB1c2luZyBQSU8gbW9kZVxuIik7 CiAJCX0gZWxzZSB7CiAJCQlpbml0X3dhaXRxdWV1ZSgmY2FtLT53cV9kbWEpOwogCQkJcHJpbnRr KEtFUk5fSU5GTyAiICB1c2luZyBETUEgbW9kZSAoaXJxICVkLCBETUEgJWQpXG4iLCBwZGV2LT5w b3J0LT5pcnEsIHBkZXYtPnBvcnQtPmRtYSk7CkBAIC0xNTUzLDYgKzE1NTMsMTMgQEAKIAkJaWYg KGNhbSAmJiBjYW0tPnBvcnQtPm51bWJlciA9PSBwb3J0LT5udW1iZXIpIHsKIAkJCVJFTU9WRV9G Uk9NX0xJU1QoY3BpYSk7CiAJCQkKKyNpZmRlZiBDT05GSUdfVklERU9fQ1BJQV9QUF9ETUEKKwkg ICAgICAgICAgICAgICAgaWYgKGNhbS0+ZG1hX2J1ZikgeworCSAgICAgICAgICAgICAgICAgICAg ICAgIGZyZWVfZG1hKGNhbS0+cGRldi0+cG9ydC0+ZG1hKTsKKyAgICAgICAgCSAgICAgICAgICAg ICAgICBrZnJlZShjYW0tPmRtYV9idWYpOworICAgICAgICAgICAgICAgIAl9CisjZW5kaWYKKwog CQkJY3BpYV91bnJlZ2lzdGVyX2NhbWVyYShjcGlhKTsKIAkJCQogCQkJaWYoY2FtLT5vcGVuX2Nv dW50ID4gMCkgewo= --_=XFMail.1.4.4.Linux:20000305230825:1773=_-- End of MIME message From nicolas.faivret@ago.fr Mon, 6 Mar 2000 14:43:34 +0100 Date: Mon, 6 Mar 2000 14:43:34 +0100 From: Nicolas FAIVRET nicolas.faivret@ago.fr Subject: [cpia] webcamII + USB + vic Hello I have been trying to get vic-2.8ucl-1.1.3 to work with my USB webcamII. Vic detects my webcam but the capture doesn't work. I see a green screen. The output is: ioctl VIDIOMCAPTURE: Paramètre invalide ioctl VIDIOCSYNC: Paramètre invalide It seems that vic try to grab with the format VIDEO_PALETTE_YUV422. (In file grabber-video4linux.cpp : vid_mmap.format = VIDEO_PALETTE_YUV422) And the cpia driver work with a different palette ( In file cpia.c : case VIDIOCMCAPTURE: { if (vm.format != VIDEO_PALETTE_RGB24) return -EINVAL; ..... ) Is there a solution ? Thanks Nicolas Faivret nfaivret@gerpi.fr From Peter.Pregler@risc.uni-linz.ac.at Mon, 06 Mar 2000 15:07:11 +0100 (CET) Date: Mon, 06 Mar 2000 15:07:11 +0100 (CET) From: Peter Pregler Peter.Pregler@risc.uni-linz.ac.at Subject: [cpia] webcamII + USB + vic On 06-Mar-2000 Nicolas FAIVRET wrote: > Hello > > I have been trying to get vic-2.8ucl-1.1.3 to work with my USB webcamII. > > Vic detects my webcam but the capture doesn't work. I see a green > screen. > The output is: > ioctl VIDIOMCAPTURE: Paramètre invalide > ioctl VIDIOCSYNC: Paramètre invalide Hmmm, which driver for the camera do you use? I get the following: [lugburz:ppregler!221] vic localhost/8000 V4l: trying /dev/video0... ok, CPiA Camera V4l: color; size: 48x48 => 352x288 V4l: ports: Camera V4l: depth=24, palette=rgb24 V4l: ==> format { 411 422 cif } size { small cif } port { Camera } V4l: trying /dev/video1... open: No such device V4l: trying /dev/video2... open: No such device V4l: trying /dev/video3... open: No such device v4l: mmap()'ed buffer size = 0xc6000 So at least with the latest 0.7.3 it is still working. This should not be a parport/usb issue since all that stuff about yuyv etc. is in the generic cpia-layer. My version of vic is the standard debian-potato package version: 2.8ucl4-2. Greetings, Peter ------------------------------- Email: Peter.Pregler@risc.uni-linz.ac.at WWW: http://www.risc.uni-linz.ac.at/people/ppregler From sTYLe@WtAl.De Mon, 06 Mar 2000 15:55:35 +0100 Date: Mon, 06 Mar 2000 15:55:35 +0100 From: Bastian sTYLe@WtAl.De Subject: [cpia] patch for cpia_pp.c - free_dma was missing and some comments on the '10 10' At 23:08 5.3.2000 +0100, Peter Pregler wrote: >Hi, > >As for the segfault I got in the '10 10'-case I think I have found the reason. >Can anyone comment about the following change of return values. The >function in >question is cpia_register_camera. Someone changed the return values ENXIO >(maybe EIO would have been better) to success??? Here is 0.5.0 > > /* get version information from camera: open/reset/close */ > > /* open cpia */ > if (camera[i]->ops->open(camera[i]->index, > &camera[i]->lowlevel_data)) >{ return -ENXIO; > } > > /* reset the camera */ > if(reset_camera(camera[i]) != 0) { > camera[i]->ops->close(camera[i]->lowlevel_data); > return -ENXIO; > } > > /* close cpia */ > camera[i]->ops->close(camera[i]->lowlevel_data); > >And here is the latest 0.7.3: > > /* get version information from camera: open/reset/close */ > > /* open cpia */ > if (camera->ops->open(camera->lowlevel_data)) > return camera; > > /* reset the camera */ > if (reset_camera(camera) != 0) { > camera->ops->close(camera->lowlevel_data); > return camera; > } > > /* close cpia */ > camera->ops->close(camera->lowlevel_data); > if have changed the two return-parts. now i get a segfault during loading the cpia_pp module. btw, it was me (maybe others) who got the 10-10-... problem >If the open/reset of the camera fails there is not much reason to report >success. Actually I am pretty sure that is a road to hell, i.e. segmentation >faults and the like. IMHO the register of the device must fail if the >open/reset fails. maby some additional information about my cam : MFG:VLSI Vision Ltd;MDL:DUAL Camera;CMD:CPIA_1-00;CLS:MEDIA;DES:Parallel Port Camera; >-Peter > >------------------------------- >Even the thought that a ship was waiting to take him back to Earth >did not wipe out the sense of loss he felt at that moment. >------------------------------- >Email: Peter.Pregler@risc.uni-linz.ac.at >Peter Pregler / RISC, University of Linz, Austria Bastian From tadavis@lbl.gov Mon, 06 Mar 2000 08:46:31 -0800 Date: Mon, 06 Mar 2000 08:46:31 -0800 From: Thomas Davis tadavis@lbl.gov Subject: [cpia] webcamII + USB + vic Peter Pregler wrote: > > On 06-Mar-2000 Nicolas FAIVRET wrote: > > Hello > > > > I have been trying to get vic-2.8ucl-1.1.3 to work with my USB webcamII. > > > > Vic detects my webcam but the capture doesn't work. I see a green > > screen. > > The output is: > > ioctl VIDIOMCAPTURE: Paramètre invalide > > ioctl VIDIOCSYNC: Paramètre invalide > > Hmmm, which driver for the camera do you use? I get the following: > He's using the driver that comes with the Linux kernel. VIC won't work with this driver. VIC does work the cpia-0.7.3 drivers, at http://home.eunet.no/~jtotland/vision/ -- ------------------------+-------------------------------------------------- Thomas Davis | PDSF Project Leader tadavis@lbl.gov | (510) 486-4524 | "Only a petabyte of data this year?" From Peter.Pregler@risc.uni-linz.ac.at Sun, 05 Mar 2000 23:19:51 +0100 (CET) Date: Sun, 05 Mar 2000 23:19:51 +0100 (CET) From: Peter Pregler Peter.Pregler@risc.uni-linz.ac.at Subject: [cpia] CPiA colour balance problem [patch] On 05-Mar-2000 rich@annexia.org wrote: > cpia.c(49441257):save_camera_state(2335):1/0/0/1/0/0/192/128 > > Note that the values printed out for red_comp, green?_comp and > blue_comp in save_camera_state are wrong. > > Any ideas? These seem to be read straight from the camera. No idea, but please try the following. There are exactly two points in cpia.c that control if the _comp-values are actually written to the camera. If you switch that off the compensation is only controlled by firmware. So we should be able to determine if this is a firmware-problem or some driver stuff. The lines in question are: - in reset_camera_struct set cam->params.exposure.compMode = 0; - in set_camera_state change the first do_command_extened from do_command_extended(cam, CPIA_COMMAND_SetExposure cam->params.exposure.gainMode, 1, 1, to do_command_extended(cam, CPIA_COMMAND_SetExposure cam->params.exposure.gainMode, 1, 0, After that the exposure compensations for the color channels are not changed anymore by the driver (unless I missed something ;). Before I forget it: your color-balance patch works fine! Checked it with the control-client and a watch of /proc. I guess I have to implement status-readback in the control-client so one can see the color-gain sliders move automagically. That would be cool. :) -Peter ------------------------------- Even the thought that a ship was waiting to take him back to Earth did not wipe out the sense of loss he felt at that moment. ------------------------------- Email: Peter.Pregler@risc.uni-linz.ac.at Peter Pregler / RISC, University of Linz, Austria From rich@annexia.org Mon, 6 Mar 2000 21:48:02 +0000 Date: Mon, 6 Mar 2000 21:48:02 +0000 From: rich@annexia.org rich@annexia.org Subject: [cpia] CPiA colour balance problem [patch] On Sun, Mar 05, 2000 at 11:19:51PM +0100, Peter Pregler wrote: > No idea, but please try the following. There are exactly two points in cpia.c > that control if the _comp-values are actually written to the camera. If you > switch that off the compensation is only controlled by firmware. So we should > be able to determine if this is a firmware-problem or some driver stuff. The > lines in question are: > > - in reset_camera_struct set cam->params.exposure.compMode = 0; > - in set_camera_state change the first do_command_extened from > > do_command_extended(cam, CPIA_COMMAND_SetExposure > cam->params.exposure.gainMode, 1, 1, > to > do_command_extended(cam, CPIA_COMMAND_SetExposure > cam->params.exposure.gainMode, 1, 0, > > After that the exposure compensations for the color channels are not changed > anymore by the driver (unless I missed something ;). Erm, that fixes it, indeed :-) I've attached an `official' patch, so that other people can try it out too, in particular David Cougle who had a similar problem with the 1.20 firmware version. I'm going to take a deeper look at this problem. Rich. PS. egrep '_comp' /proc/cpia/video0 with the patch gives much more believable results ... red_comp: 220 220 255 220 green1_comp: 214 214 255 214 green2_comp: 214 214 255 214 blue_comp: 230 230 255 230 ---------------------------------------------------------------------- --- cpia.c~ Sun Mar 5 14:54:55 2000 +++ cpia.c Mon Mar 6 21:45:21 2000 @@ -2356,7 +2356,7 @@ do_command_extended(cam, CPIA_COMMAND_SetExposure, - cam->params.exposure.gainMode, 1, 1, + cam->params.exposure.gainMode, 1, 0, // RWMJ cam->params.exposure.centreWeight, cam->params.exposure.gain, cam->params.exposure.fineExp, @@ -3099,7 +3099,7 @@ cam->params.colourParams.saturation = 50; cam->params.exposure.gainMode = 2; cam->params.exposure.expMode = 2; /* AEC */ - cam->params.exposure.compMode = 1; + cam->params.exposure.compMode = 0; // RWMJ cam->params.exposure.centreWeight = 1; cam->params.exposure.gain = 0; cam->params.exposure.fineExp = 0; -- rich@annexia.org | Is your school part of http://www.schoolmaster.net ? BiblioTech Ltd, Unit 2 Piper Centre, 50 Carnwath Road, London, SW6 3EG. +44 20 7384 6917 | Click here to play XRacer: http://xracer.annexia.org Copyright © 2000 Richard Jones | GnuPG/PGP key from www.annexia.org From rich@annexia.org Mon, 6 Mar 2000 22:18:39 +0000 Date: Mon, 6 Mar 2000 22:18:39 +0000 From: rich@annexia.org rich@annexia.org Subject: [cpia] CPiA colour balance problem [patch] On Mon, Mar 06, 2000 at 09:48:02PM +0000, rich@annexia.org wrote: [...] > I'm going to take a deeper look at this problem. Fixed it. I hope you're all going to be suitably embarrassed by the fix :-) By the way - I left a warning in place in the patch. If the patch is working correctly, then the warning should *never* be printed out. You also have to apply this patch after applying my previous colour balance patch. Rich. ---------------------------------------------------------------------- diff -ur cpia-0.7.3-cb-fix/module/cpia.c cpia-0.7.3-cb-fix-comp-fix/module/cpia.c --- cpia-0.7.3-cb-fix/module/cpia.c Mon Mar 6 21:53:44 2000 +++ cpia-0.7.3-cb-fix-comp-fix/module/cpia.c Mon Mar 6 22:12:14 2000 @@ -1700,6 +1700,29 @@ cam->params.exposure.green1Comp = data[5]; cam->params.exposure.green2Comp = data[6]; cam->params.exposure.blueComp = data[7]; + /* If the *Comp parameters are wacko, generate + * a warning, and reset them back to default + * values. - rich@annexia.org + */ + if (cam->params.exposure.redComp < 220 || + cam->params.exposure.redComp > 255 || + cam->params.exposure.green1Comp < 214 || + cam->params.exposure.green1Comp > 255 || + cam->params.exposure.green2Comp < 214 || + cam->params.exposure.green2Comp > 255 || + cam->params.exposure.blueComp < 230 || + cam->params.exposure.blueComp > 255) + { + printk (KERN_WARNING "*_comp parameters have gone AWOL (%d/%d/%d/%d) - reseting them\n", + cam->params.exposure.redComp, + cam->params.exposure.green1Comp, + cam->params.exposure.green2Comp, + cam->params.exposure.blueComp); + cam->params.exposure.redComp = 220; + cam->params.exposure.green1Comp = 214; + cam->params.exposure.green2Comp = 214; + cam->params.exposure.blueComp = 230; + } up(&cam->param_lock); break; default: @@ -2362,10 +2385,10 @@ cam->params.exposure.fineExp, cam->params.exposure.coarseExpLo, cam->params.exposure.coarseExpHi, - cam->params.exposure.redComp, - cam->params.exposure.green1Comp, - cam->params.exposure.green2Comp, - cam->params.exposure.blueComp); + cam->params.exposure.redComp, + cam->params.exposure.green1Comp, + cam->params.exposure.green2Comp, + cam->params.exposure.blueComp); do_command_extended(cam, CPIA_COMMAND_SetExposure, 0, 3, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0); diff -ur cpia-0.7.3-cb-fix/module/cpia_usb.c cpia-0.7.3-cb-fix-comp-fix/module/cpia_usb.c --- cpia-0.7.3-cb-fix/module/cpia_usb.c Wed Mar 1 10:47:44 2000 +++ cpia-0.7.3-cb-fix-comp-fix/module/cpia_usb.c Mon Mar 6 22:17:51 2000 @@ -276,7 +276,7 @@ * WritePacket * ***************************************************************************/ -static int WritePacket(struct usb_device *udev, const u8 *packet) +static int WritePacket(struct usb_device *udev, const u8 *packet, u8 *buf, size_t size) { if (!packet) return -EINVAL; @@ -285,7 +285,7 @@ packet[1] + (packet[0] << 8), USB_TYPE_VENDOR | USB_RECIP_DEVICE, packet[2] + (packet[3] << 8), - packet[4] + (packet[5] << 8), NULL, 0, HZ); + packet[4] + (packet[5] << 8), buf, size, HZ); } /**************************************************************************** @@ -338,7 +338,7 @@ memcpy(data, buffer, databytes); } else if(command[0] == DATA_OUT) - WritePacket(udev, command); + WritePacket(udev, command, data, databytes); else { DBG("Unexpected first byte of command: %x\n", command[0]); err = -EINVAL; ---------------------------------------------------------------------- -- rich@annexia.org | Is your school part of http://www.schoolmaster.net ? BiblioTech Ltd, Unit 2 Piper Centre, 50 Carnwath Road, London, SW6 3EG. +44 20 7384 6917 | Click here to play XRacer: http://xracer.annexia.org Copyright © 2000 Richard Jones | GnuPG/PGP key from www.annexia.org From tadavis@lbl.gov Mon, 06 Mar 2000 15:20:04 -0800 Date: Mon, 06 Mar 2000 15:20:04 -0800 From: Thomas Davis tadavis@lbl.gov Subject: [cpia] CPiA colour balance problem [patch] rich@annexia.org wrote: > > You also have to apply this patch after applying my previous > colour balance patch. > Hey, this fixed it! Yea! -- ------------------------+-------------------------------------------------- Thomas Davis | PDSF Project Leader tadavis@lbl.gov | (510) 486-4524 | "Only a petabyte of data this year?" From jerdfelt@sventech.com Mon, 6 Mar 2000 21:46:55 -0500 Date: Mon, 6 Mar 2000 21:46:55 -0500 From: Johannes Erdfelt jerdfelt@sventech.com Subject: [cpia] CPiA colour balance problem [patch] On Mon, Mar 06, 2000, rich@annexia.org wrote: > On Mon, Mar 06, 2000 at 09:48:02PM +0000, rich@annexia.org wrote: > [...] > > I'm going to take a deeper look at this problem. > > Fixed it. I hope you're all going to be suitably embarrassed > by the fix :-) Fixed it for me as well. I was looking all over that code recently and I didn't even put 2 and 2 together. Thanks! JE From Peter.Pregler@risc.uni-linz.ac.at Tue, 07 Mar 2000 08:28:15 +0100 (CET) Date: Tue, 07 Mar 2000 08:28:15 +0100 (CET) From: Peter Pregler Peter.Pregler@risc.uni-linz.ac.at Subject: [cpia] CPiA colour balance problem [patch] On 06-Mar-2000 rich@annexia.org wrote: > > Erm, that fixes it, indeed :-) I've attached an `official' patch, > so that other people can try it out too, in particular David Cougle > who had a similar problem with the 1.20 firmware version. > > I'm going to take a deeper look at this problem. Hmmm, I guess it was my fault. :( I seem to have mixed up exposure control and color balance. After rereading the developers guide I think the exposure control should only be touched in case of flicker control whereas the color balance state should be saved between open/close. I'll try to reproduce the '10 10' problem and solve it in the evening. If that works out I will put together a 0.7.4. A question to Johannes: shouln't we replace the kernel-driver with this version? What is the procedure to do so? I have submitted 0.5.0 (parport only) to Alan for inclusion in 2.2.16. But I guess that has not much to do with the recent 2.3.X-kernels. -Peter ------------------------------- Email: Peter.Pregler@risc.uni-linz.ac.at WWW: http://www.risc.uni-linz.ac.at/people/ppregler From nicolas.faivret@ago.fr Tue, 7 Mar 2000 14:02:36 +0100 Date: Tue, 7 Mar 2000 14:02:36 +0100 From: Nicolas FAIVRET nicolas.faivret@ago.fr Subject: [cpia] webcamII + USB + vic : kernel BUG at cpia.c:245! First of all, Many thanks to Peter Pregler and to Thomas Davis. I get the cpia-0.7.3 drivers, at http://home.eunet.no/~jtotland/vision/. During the installation, I encounter some problems of unresolved symbol because my kernel was compiled with the option version information on module symbols. And now everything seem to work fine, # dmesg V4L-Driver for Vision CPiA based cameras v0.7.3 usb.c: registered new driver cpia USB CPiA camera found cpia.c(30411):goto_low_power(2317):04 00 00 00 00 00 10 00 cpia.c(30419):goto_high_power(2300):camera now in HIGH power state cpia.c(30421):goto_low_power(2314):camera now in LOW power state cpia.c(30430):goto_high_power(2300):camera now in HIGH power state cpia.c(30443):dispatch_commands(2039):1 1 0 0 1 1 1 1 cpia.c(30443):dispatch_commands(2040):0 1 1 1 1 1 0 1 cpia.c(30448):save_camera_state(2334):1/0/0/1/0/0/0/0 cpia.c(30448):save_camera_state(2338):32/6/92 CPiA Version: 1.20 (2.0) CPiA PnP-ID: 0553:0002:0100 VP-Version: 1.0 0100 usb.c: cpia driver claimed interface c3a191e0 but when I try # vic localhost/8000 V4l: trying /dev/video0... Segmentation fault # dmesg V4L-Driver for Vision CPiA based cameras v0.7.3 usb.c: registered new driver cpia USB CPiA camera found cpia.c(30411):goto_low_power(2317):04 00 00 00 00 00 10 00 cpia.c(30419):goto_high_power(2300):camera now in HIGH power state cpia.c(30421):goto_low_power(2314):camera now in LOW power state cpia.c(30430):goto_high_power(2300):camera now in HIGH power state cpia.c(30443):dispatch_commands(2039):1 1 0 0 1 1 1 1 cpia.c(30443):dispatch_commands(2040):0 1 1 1 1 1 0 1 cpia.c(30448):save_camera_state(2334):1/0/0/1/0/0/0/0 cpia.c(30448):save_camera_state(2338):32/6/92 CPiA Version: 1.20 (2.0) CPiA PnP-ID: 0553:0002:0100 VP-Version: 1.0 0100 usb.c: cpia driver claimed interface c3a191e0 kernel BUG at cpia.c:245! invalid operand: 0000 CPU: 0 EIP: 0010:[] EFLAGS: 00010292 eax: 0000001a ebx: 00026000 ecx: 00000019 edx: 00000031 esi: 000e53c8 edi: c4972000 ebp: c4966000 esp: c33bff10 ds: 0018 es: 0018 ss: 0018 Process vic (pid: 527, stackpage=c33bf000) Stack: c1d26600 00000000 c033d6e0 c3a3e6c0 000005c8 c482e2b0 00031ba5 c1d266d8 00000000 c01ba3b7 c1d266d8 00000000 00000000 c0b7a140 c3d8ccc0 00000051 00000000 000000ff c02392e1 c028dec0 c013b47a c3d8ccc0 c0b7a140 c0b7a140 Call Trace: [] [] [] [] [] [] [] Code: 0f 0b 8b 15 2c c5 28 c0 89 f9 81 e1 ff 0f 00 00 0b 4c 32 40 Is there anyone who solve this problem ? Nicolas. From jerdfelt@sventech.com Tue, 7 Mar 2000 11:27:12 -0500 Date: Tue, 7 Mar 2000 11:27:12 -0500 From: Johannes Erdfelt jerdfelt@sventech.com Subject: [cpia] CPiA colour balance problem [patch] On Tue, Mar 07, 2000, Peter Pregler wrote: > > On 06-Mar-2000 rich@annexia.org wrote: > > > > Erm, that fixes it, indeed :-) I've attached an `official' patch, > > so that other people can try it out too, in particular David Cougle > > who had a similar problem with the 1.20 firmware version. > > > > I'm going to take a deeper look at this problem. > > Hmmm, I guess it was my fault. :( I seem to have mixed up exposure control > and color balance. After rereading the developers guide I think the > exposure control should only be touched in case of flicker control whereas > the color balance state should be saved between open/close. > > I'll try to reproduce the '10 10' problem and solve it in the evening. If > that works out I will put together a 0.7.4. > > A question to Johannes: shouln't we replace the kernel-driver with this > version? What is the procedure to do so? I have submitted 0.5.0 (parport > only) to Alan for inclusion in 2.2.16. But I guess that has not much to do > with the recent 2.3.X-kernels. I can handle it if you like. We'll most likely have to remove the 2.2isms to get it into 2.3, but that's not much code. Everyone on the linux-usb list agrees with me and I'm sure Linus won't have any problems with removing my old driver and getting this newer one into the kernel. JE From jerdfelt@sventech.com Tue, 7 Mar 2000 11:29:41 -0500 Date: Tue, 7 Mar 2000 11:29:41 -0500 From: Johannes Erdfelt jerdfelt@sventech.com Subject: [cpia] webcamII + USB + vic : kernel BUG at cpia.c:245! On Tue, Mar 07, 2000, Nicolas FAIVRET wrote: > First of all, Many thanks to Peter Pregler and to Thomas Davis. > > I get the cpia-0.7.3 drivers, at http://home.eunet.no/~jtotland/vision/. > During the installation, I encounter some problems of unresolved symbol > because my kernel was compiled with the option version information on module > > symbols. > And now everything seem to work fine, > > # dmesg > V4L-Driver for Vision CPiA based cameras v0.7.3 > usb.c: registered new driver cpia > USB CPiA camera found > cpia.c(30411):goto_low_power(2317):04 00 00 00 00 00 10 00 > cpia.c(30419):goto_high_power(2300):camera now in HIGH power state > cpia.c(30421):goto_low_power(2314):camera now in LOW power state > cpia.c(30430):goto_high_power(2300):camera now in HIGH power state > cpia.c(30443):dispatch_commands(2039):1 1 0 0 1 1 1 1 > cpia.c(30443):dispatch_commands(2040):0 1 1 1 1 1 0 1 > cpia.c(30448):save_camera_state(2334):1/0/0/1/0/0/0/0 > cpia.c(30448):save_camera_state(2338):32/6/92 > CPiA Version: 1.20 (2.0) > CPiA PnP-ID: 0553:0002:0100 > VP-Version: 1.0 0100 > usb.c: cpia driver claimed interface c3a191e0 > > > but when I try > # vic localhost/8000 > V4l: trying /dev/video0... Segmentation fault > # dmesg > V4L-Driver for Vision CPiA based cameras v0.7.3 > usb.c: registered new driver cpia > USB CPiA camera found > cpia.c(30411):goto_low_power(2317):04 00 00 00 00 00 10 00 > cpia.c(30419):goto_high_power(2300):camera now in HIGH power state > cpia.c(30421):goto_low_power(2314):camera now in LOW power state > cpia.c(30430):goto_high_power(2300):camera now in HIGH power state > cpia.c(30443):dispatch_commands(2039):1 1 0 0 1 1 1 1 > cpia.c(30443):dispatch_commands(2040):0 1 1 1 1 1 0 1 > cpia.c(30448):save_camera_state(2334):1/0/0/1/0/0/0/0 > cpia.c(30448):save_camera_state(2338):32/6/92 > CPiA Version: 1.20 (2.0) > CPiA PnP-ID: 0553:0002:0100 > VP-Version: 1.0 0100 > usb.c: cpia driver claimed interface c3a191e0 > kernel BUG at cpia.c:245! > invalid operand: 0000 > CPU: 0 > EIP: 0010:[] > EFLAGS: 00010292 > eax: 0000001a ebx: 00026000 ecx: 00000019 edx: 00000031 > esi: 000e53c8 edi: c4972000 ebp: c4966000 esp: c33bff10 > ds: 0018 es: 0018 ss: 0018 > Process vic (pid: 527, stackpage=c33bf000) > Stack: c1d26600 00000000 c033d6e0 c3a3e6c0 000005c8 c482e2b0 00031ba5 > c1d266d8 > 00000000 c01ba3b7 c1d266d8 00000000 00000000 c0b7a140 c3d8ccc0 > 00000051 > 00000000 000000ff c02392e1 c028dec0 c013b47a c3d8ccc0 c0b7a140 > c0b7a140 > Call Trace: [] [] [] [] [] > [] [] > Code: 0f 0b 8b 15 2c c5 28 c0 89 f9 81 e1 ff 0f 00 00 0b 4c 32 40 > > Is there anyone who solve this problem ? I got this when I compiled my kernel for SMP but the CPiA modules were compiled for UP. JE From Peter.Pregler@risc.uni-linz.ac.at Tue, 07 Mar 2000 21:01:58 +0100 (CET) Date: Tue, 07 Mar 2000 21:01:58 +0100 (CET) From: Peter Pregler Peter.Pregler@risc.uni-linz.ac.at Subject: [cpia] webcamII + USB + vic : kernel BUG at cpia.c:245! On 07-Mar-2000 Nicolas FAIVRET wrote: [oops deleted] > Is there anyone who solve this problem ? I cannot reproduce the problem with 2.3.49 and my parport anymore. It just does not ooops, so I think it was in my case also some configuration-mismatch between kernel- and module-compilation. However, I noted one thing during compilation. In cpia_usb.c there is an absolute reference to an include file burried in the kernel-source, namely to /usr/src/linux/drivers/usb/usb.h. If this is not the include your running-kernel was built from this might be a cause for your ooops. -Peter ------------------------------- Even the thought that a ship was waiting to take him back to Earth did not wipe out the sense of loss he felt at that moment. ------------------------------- Email: Peter.Pregler@risc.uni-linz.ac.at Peter Pregler / RISC, University of Linz, Austria From zioivy@libero.it Tue, 07 Mar 2000 22:21:32 +0100 Date: Tue, 07 Mar 2000 22:21:32 +0100 From: ZioIvy zioivy@libero.it Subject: [cpia] Quality When I start gqcam the grabbed image is perfect for about 1 second. From now on is very "pixelate" (sorry for my English...). Someone else noticed that? My problem is that I want such a perfect image always, even at 1 frame per minute because I have to do image segmentation and object recognition. Can anyone help me? Thanks. From nicolas.faivret@ago.fr Wed, 8 Mar 2000 18:02:03 +0100 Date: Wed, 8 Mar 2000 18:02:03 +0100 From: Nicolas FAIVRET nicolas.faivret@ago.fr Subject: [cpia] webcamII + USB + vic : segmentation fault >I got this when I compiled my kernel for SMP but the CPiA modules were >compiled for UP. Thanks, It works. V4l: trying /dev/video0... ok, CPiA Camera V4l: color; size: 48x48 => 352x288 V4l: ports: Camera V4l: depth=0, palette=rgb24 V4l: ==> format { 411 422 cif } size { small cif } port { Camera } V4l: trying /dev/video1... open: Aucun périphérique de ce type V4l: trying /dev/video2... open: Aucun périphérique de ce type V4l: trying /dev/video3... open: Aucun périphérique de ce type v4l: mmap()'ed buffer size = 0xc6000 But I can't grab, I get a segmentation fault on void V4lGrabber::start() { ---->>> if (-1 == ioctl(fd_, VIDIOCMCAPTURE, &gb_even)) with gb_even.frame = 0 gb_even.height = 288 gb_even.width = 352 gb_even.format = 7 fd_ = 15 Where can I see the cpia error returned ? If someone have a USB webcamII which works fine with vic under linux, I would like to know the linux kernel version to use. From jerdfelt@sventech.com Wed, 8 Mar 2000 12:20:05 -0500 Date: Wed, 8 Mar 2000 12:20:05 -0500 From: Johannes Erdfelt jerdfelt@sventech.com Subject: [cpia] webcamII + USB + vic : segmentation fault On Wed, Mar 08, 2000, Nicolas FAIVRET wrote: > >I got this when I compiled my kernel for SMP but the CPiA modules were > >compiled for UP. > > Thanks, It works. > > V4l: trying /dev/video0... ok, CPiA Camera > V4l: color; size: 48x48 => 352x288 > V4l: ports: Camera > V4l: depth=0, palette=rgb24 > V4l: ==> format { 411 422 cif } size { small cif } port { Camera } > V4l: trying /dev/video1... open: Aucun périphérique de ce type > V4l: trying /dev/video2... open: Aucun périphérique de ce type > V4l: trying /dev/video3... open: Aucun périphérique de ce type > v4l: mmap()'ed buffer size = 0xc6000 > > But I can't grab, I get a segmentation fault on > > void V4lGrabber::start() > { > ---->>> if (-1 == ioctl(fd_, VIDIOCMCAPTURE, &gb_even)) > > with gb_even.frame = 0 > gb_even.height = 288 > gb_even.width = 352 > gb_even.format = 7 > > fd_ = 15 > > Where can I see the cpia error returned ? > > If someone have a USB webcamII which works fine with vic under linux, > I would like to know the linux kernel version to use. Check your kernel log (ie run dmesg). A seg fault in ioctl usually means the kernel oopsed (not always, but usually). JE From jack_diederich@email.com Wed, 8 Mar 2000 23:18:52 -0500 (EST) Date: Wed, 8 Mar 2000 23:18:52 -0500 (EST) From: Jack Diederich jack_diederich@email.com Subject: [cpia] profiling device drivers hi all, I did some searches on google, redhat & the LDP, but I couldn't find any articles on how to profile/benchmark device drivers. Does anyone know how this works? The reason I ask is that I was playing around w/ yuvconvert to streamline it a bit (it seemed like the kind of frequently called math heavy routine that might benefit). If my changes sped it up at all, it isn't noticeable. I'd still like to know where the driver spends most of its time. thanks, -smallberries ----------------------------------------------- FREE! The World's Best Email Address @email.com Reserve your name now at http://www.email.com From jerdfelt@sventech.com Wed, 8 Mar 2000 23:30:25 -0500 Date: Wed, 8 Mar 2000 23:30:25 -0500 From: Johannes Erdfelt jerdfelt@sventech.com Subject: [cpia] profiling device drivers On Wed, Mar 08, 2000, Jack Diederich wrote: > hi all, > > I did some searches on google, redhat & the LDP, but I couldn't > find any articles on how to profile/benchmark device drivers. > Does anyone know how this works? > > The reason I ask is that I was playing around w/ yuvconvert to > streamline it a bit (it seemed like the kind of frequently called > math heavy routine that might benefit). If my changes sped it > up at all, it isn't noticeable. I'd still like to know where > the driver spends most of its time. Take a look at http://www.tux.org/hypermail/linux-kernel/1999week20/1079.html for profiling information. There are some patches floating around. I've never used any tho. I recently was talking to the X developer here and explaining to him the current CPiA driver, he urged me to use xvimage support under the new version of XFree (4.0). It'll do color conversion and scaling all through hardware which supports it (Matrox, etc). JE From nfaivret@gerpi.fr Thu, 9 Mar 2000 11:57:11 +0100 Date: Thu, 9 Mar 2000 11:57:11 +0100 From: Nicolas Faivret nfaivret@gerpi.fr Subject: [cpia] webcamII + USB + vic : GOAL !! Hello, It works. The changes since yesterday are : - I get the last kernel 2.3.50 - I compile it with USB core not as a module but as a part of the kernel. - I get the last version of vic vic-2.8ucl-1.1.3-linux-2.2 - I compile again the cpia-0.7.3 drivers,( at http://home.eunet.no/~jtotland/vision/ ) with -D__SMP__ as my kernel. Thanks for the help. I'm ok for any test. Nicolas Faivret Tél : 06 63 03 28 36 Consultant GERPI Alma City 3 rue du Bosphore 35074 Rennes Tél : 02 99 51 17 18 ----------------------------------------------------- From zioivy@libero.it Thu, 09 Mar 2000 21:01:38 +0100 Date: Thu, 09 Mar 2000 21:01:38 +0100 From: ZioIvy zioivy@libero.it Subject: [cpia] Problem with isa parallel port I have a double parallel port on isa bus. Linux detects both ports correctly, I can print and use them with the kernel 2.3.34, but not with the 2.2.x (2.2.12-2.2.14). Cpia detects the camera, the ecp port etc. but when I start gqcam it freezes and I have to kill it. With dmesg I get an Input/Output Read Error. Solutions? Thank's From Peter.Pregler@risc.uni-linz.ac.at Fri, 10 Mar 2000 08:55:43 +0100 (CET) Date: Fri, 10 Mar 2000 08:55:43 +0100 (CET) From: Peter Pregler Peter.Pregler@risc.uni-linz.ac.at Subject: [cpia] Problem with isa parallel port On 09-Mar-2000 ZioIvy wrote: > I have a double parallel port on isa bus. Linux detects both ports > correctly, I can print and use them with the kernel 2.3.34, but not with > the 2.2.x (2.2.12-2.2.14). Cpia detects the camera, the ecp port etc. > but when I start gqcam it freezes and I have to kill it. With dmesg I > get an Input/Output Read Error. > Solutions? - reading your mind? - hacking your computer to get the relevant syslog-info? - posting more information, esp. info from the syslog-files and the proc-filesystem (dma/interrupt/parport/cpia/modules) Choose what you like best. ;) -Peter ------------------------------- Email: Peter.Pregler@risc.uni-linz.ac.at WWW: http://www.risc.uni-linz.ac.at/people/ppregler From zioivy@libero.it Fri, 10 Mar 2000 13:05:38 +0100 Date: Fri, 10 Mar 2000 13:05:38 +0100 From: ZioIvy zioivy@libero.it Subject: [cpia] Problem with isa parallel port Peter Pregler wrote: > > On 09-Mar-2000 ZioIvy wrote: > > I have a double parallel port on isa bus. Linux detects both ports > > correctly, I can print and use them with the kernel 2.3.34, but not with > > the 2.2.x (2.2.12-2.2.14). Cpia detects the camera, the ecp port etc. > > but when I start gqcam it freezes and I have to kill it. With dmesg I > > get an Input/Output Read Error. > > Solutions? > > - reading your mind? > - hacking your computer to get the relevant syslog-info? > - posting more information, esp. info from the syslog-files and the > proc-filesystem (dma/interrupt/parport/cpia/modules) Sorry 8-( It was late and I was tired. Sometimes I disconnect my brain 8-) If I insert modules without dma support dmesg gives: parport0: PC-style at 0x3bc (0x7bc) [SPP,ECP,ECPPS2] parport0: detected irq 7; use procfs to enable interrupt-driven operation. parport1: PC-style at 0x378 (0x778) [SPP,ECP,ECPPS2] parport1: detected irq 4; use procfs to enable interrupt-driven operation. parport2: PC-style at 0x278 (0x678) [SPP,ECP,ECPPS2] parport2: detected irq 10; use procfs to enable interrupt-driven operation. Linux video capture interface: v1.00 V4L-Driver for Vision CPiA based cameras v0.7.3 parport0: Printer, HEWLETT-PACKARD DESKJET 880C parport1: read2 timeout. parport1: Multimedia device, VLSI Vision Ltd PPC2 Camera parport2: no IEEE-1284 device present. Parallel port driver for Vision CPiA based cameras v0.7.3 using PIO mode cpia.c(5502):goto_low_power(2314):camera now in LOW power state cpia.c(5510):goto_high_power(2300):camera now in HIGH power state cpia.c(5522):dispatch_commands(2039):1 1 0 0 1 1 1 1 cpia.c(5522):dispatch_commands(2040):0 1 1 1 1 1 0 1 cpia.c(5524):save_camera_state(2334):0/0/185/0/220/214/214/230 cpia.c(5524):save_camera_state(2338):32/6/92 CPiA Version: 1.20 (2.0) CPiA PnP-ID: 0553:0002:0100 VP-Version: 1.0 0100 1 camera(s) found Than I start gqcam, it freezes, I kill it and I get: cpia.c(8299):goto_low_power(2314):camera now in LOW power state cpia.c(8307):goto_high_power(2300):camera now in HIGH power state cpia.c(8320):dispatch_commands(2039):1 1 0 0 1 1 1 1 cpia.c(8320):dispatch_commands(2040):0 1 1 1 1 1 0 1 cpia.c(8321):save_camera_state(2334):0/0/185/0/220/214/214/230 cpia.c(8321):save_camera_state(2338):32/6/92 cpia.c(8321):cpia_ioctl(2677):VIDIOCGCAP cpia.c(8321):cpia_ioctl(2789):VIDIOCGWIN cpia.c(8321):cpia_ioctl(2736):VIDIOCGPICT cpia.c(8321):cpia_ioctl(2745):VIDIOCSPICT cpia.c(8321):cpia_ioctl(2754):palette: 4 cpia.c(8321):cpia_ioctl(2755):depth: 24 cpia.c(8321):cpia_ioctl(2783):VIDIOCSPICT: 24 / 4 // 32768 / 32768 / 32768 / 32768 cpia.c(8322):cpia_ioctl(2799):VIDIOCSWIN cpia.c(8322):cpia_ioctl(2842):1/352:288 cpia_pp.c(8361):while_out(305):WhileoutError at line waited 10 cpia_pp.c(8361):cpia_pp_streamRead(1231):incomplete image: 8361 / 0 / 1 cpia.c(8361):fetch_frame(2207):streamRead failed: -5 cpia.c(8361):fetch_frame(2159):retry=1 cpia.c(8457):cpia_read(2633):upload failed 0/0 cpia.c(8457):save_camera_state(2334):0/0/185/0/220/214/214/230 cpia.c(8457):save_camera_state(2338):35/9/88 cpia.c(8458):goto_low_power(2314):camera now in LOW power state cpia.c(8597):cpia_unregister_camera(3277):unregistering video cpia.c(8597):cpia_unregister_camera(3287):destroying /proc/cpia/video0 cpia.c(8597):cpia_unregister_camera(3291):freeing camera But this mornign I found that if I insert parport_pc with: insmod parport_pc io=0x378 irq=4 dma=1 I obtain: parport0: PC-style at 0x378 (0x778), irq 4, dma 1 [SPP,ECP,ECPPS2] Linux video capture interface: v1.00 V4L-Driver for Vision CPiA based cameras v0.7.3 parport0: read2 timeout. parport0: Multimedia device, VLSI Vision Ltd PPC2 Camera Parallel port driver for Vision CPiA based cameras v0.7.3 using DMA mode (irq 4, DMA 1) cpia.c(9023):goto_low_power(2314):camera now in LOW power state cpia.c(9031):goto_high_power(2300):camera now in HIGH power state cpia.c(9043):dispatch_commands(2039):1 1 0 0 1 1 1 1 cpia.c(9043):dispatch_commands(2040):0 1 1 1 1 1 0 1 cpia.c(9045):save_camera_state(2334):0/0/185/0/220/214/214/230 cpia.c(9045):save_camera_state(2338):32/6/92 CPiA Version: 1.20 (2.0) CPiA PnP-ID: 0553:0002:0100 VP-Version: 1.0 0100 1 camera(s) found cpia_pp.c(10613):cpia_pp_irq_handler(1066):image skipped? cpia.c(10615):goto_low_power(2314):camera now in LOW power state cpia.c(10623):goto_high_power(2300):camera now in HIGH power state cpia.c(10636):dispatch_commands(2039):1 1 0 0 1 1 1 1 cpia.c(10636):dispatch_commands(2040):0 1 1 1 1 1 0 1 cpia.c(10637):save_camera_state(2334):0/0/185/0/220/214/214/230 cpia.c(10637):save_camera_state(2338):32/6/92 cpia.c(10638):cpia_ioctl(2677):VIDIOCGCAP cpia.c(10638):cpia_ioctl(2789):VIDIOCGWIN cpia.c(10638):cpia_ioctl(2736):VIDIOCGPICT cpia.c(10638):cpia_ioctl(2745):VIDIOCSPICT cpia.c(10638):cpia_ioctl(2754):palette: 4 cpia.c(10638):cpia_ioctl(2755):depth: 24 cpia.c(10638):cpia_ioctl(2783):VIDIOCSPICT: 24 / 4 // 32768 / 32768 / 32768 / 32768 cpia.c(10638):cpia_ioctl(2799):VIDIOCSWIN cpia.c(10638):cpia_ioctl(2842):1/352:288 cpia.c(11667):fetch_frame(2207):streamRead failed: -5 cpia.c(11667):fetch_frame(2159):retry=1 cpia.c(11667):cpia_read(2633):upload failed 0/0 cpia.c(11667):save_camera_state(2334):0/0/185/0/220/214/214/230 cpia.c(11667):save_camera_state(2338):30/6/77 cpia.c(11669):goto_low_power(2314):camera now in LOW power state The same problem except the firts message about cpia_pp_irq_handler. Than, if I remove modules and I insert them again without dma, after that the camera it's ok! parport0: PC-style at 0x3bc (0x7bc) [SPP,ECP,ECPPS2] parport0: detected irq 7; use procfs to enable interrupt-driven operation. parport1: PC-style at 0x378 (0x778) [SPP,ECP,ECPPS2] parport1: detected irq 4; use procfs to enable interrupt-driven operation. parport2: PC-style at 0x278 (0x678) [SPP,ECP,ECPPS2] parport2: detected irq 10; use procfs to enable interrupt-driven operation. Linux video capture interface: v1.00 V4L-Driver for Vision CPiA based cameras v0.7.3 parport0: Printer, HEWLETT-PACKARD DESKJET 880C parport1: read2 timeout. parport1: Multimedia device, VLSI Vision Ltd PPC2 Camera parport2: no IEEE-1284 device present. Parallel port driver for Vision CPiA based cameras v0.7.3 using PIO mode cpia.c(18603):goto_low_power(2314):camera now in LOW power state cpia.c(18611):goto_high_power(2300):camera now in HIGH power state cpia.c(18623):dispatch_commands(2039):1 1 0 0 1 1 1 1 cpia.c(18623):dispatch_commands(2040):0 1 1 1 1 1 0 1 cpia.c(18625):save_camera_state(2334):0/0/185/0/220/214/214/230 cpia.c(18625):save_camera_state(2338):32/6/92 CPiA Version: 1.20 (2.0) CPiA PnP-ID: 0553:0002:0100 VP-Version: 1.0 0100 1 camera(s) found cpia.c(20625):goto_low_power(2314):camera now in LOW power state cpia.c(20633):goto_high_power(2300):camera now in HIGH power state cpia.c(20645):dispatch_commands(2039):1 1 0 0 1 1 1 1 cpia.c(20645):dispatch_commands(2040):0 1 1 1 1 1 0 1 cpia.c(20647):save_camera_state(2334):0/0/185/0/220/214/214/230 cpia.c(20647):save_camera_state(2338):32/6/92 cpia.c(20647):cpia_ioctl(2677):VIDIOCGCAP cpia.c(20647):cpia_ioctl(2789):VIDIOCGWIN cpia.c(20647):cpia_ioctl(2736):VIDIOCGPICT cpia.c(20647):cpia_ioctl(2745):VIDIOCSPICT cpia.c(20647):cpia_ioctl(2754):palette: 4 cpia.c(20647):cpia_ioctl(2755):depth: 24 cpia.c(20647):cpia_ioctl(2783):VIDIOCSPICT: 24 / 4 // 32768 / 32768 / 32768 / 32768 cpia.c(20647):cpia_ioctl(2799):VIDIOCSWIN cpia.c(20647):cpia_ioctl(2842):1/352:288 cpia.c(20711):dispatch_commands(2039):0 0 0 0 0 1 0 0 cpia.c(20711):dispatch_commands(2040):0 0 0 0 0 0 0 0 cpia.c(20751):dispatch_commands(2039):0 0 0 0 0 0 0 1 cpia.c(20751):dispatch_commands(2040):0 0 0 0 0 0 1 0 cpia.c(20948):save_camera_state(2334):0/1/27/1/220/214/214/230 cpia.c(20948):save_camera_state(2338):32/6/91 cpia.c(20949):goto_low_power(2314):camera now in LOW power state In the proc fs dma and irq are set correctly when I insert parport_pc with the irq and dma options. Sorry for the long email. I hope you have enougth informations now. Thanks From tdat@yahoo.com Fri, 10 Mar 2000 10:08:02 -0800 (PST) Date: Fri, 10 Mar 2000 10:08:02 -0800 (PST) From: Sang Y. Yum tdat@yahoo.com Subject: [cpia] Can't load cpia/cpia_pp modules Hi, I've been trying to get Creative WebCam II Parallel Port configured under Linux-Mandrake 7.0 without much success. I installed kernel-source RPM for the version of kernel on my machine. I downloaded 0.7.3 version of cpia driver and compiled it. When I tried to load cpia and cpia_pp modules, I got these messages in /var/log/messages: Mar 10 08:47:52 localhost kernel: V4L-Driver for Vision CPiA based cameras v0.7.3 Mar 10 08:47:52 localhost kernel: parport0: PC-style at 0x378 [SPP] Mar 10 08:47:53 localhost insmod: /lib/modules/2.2.14-15mdk/video/cpia_pp.o: unresolved symbol cpia_unregister_camera Mar 10 08:47:53 localhost insmod: /lib/modules/2.2.14-15mdk/video/cpia_pp.o: unresolved symbol cpia_register_camera Mar 10 08:48:04 localhost kernel: parport0: no IEEE-1284 device present. Mar 10 08:48:04 localhost kernel: Parallel port driver for Vision CPiA based cameras v0.7.3 Mar 10 08:48:04 localhost kernel: 0 camera(s) found Based on the information I picked up the maling list archive, I decided to recompile my kernel. After the kernel was compiled, I recompiled cpia driver and tried the following: [root@pikatsu module]# /sbin/insmod cpia.o cpia.o: unresolved symbol video_register_device cpia.o: unresolved symbol video_unregister_device [root@pikatsu module]# /sbin/insmod cpia_pp.o cpia_pp.o: unresolved symbol parport_unregister_device cpia_pp.o: unresolved symbol parport_enumerate cpia_pp.o: unresolved symbol cpia_unregister_camera cpia_pp.o: unresolved symbol cpia_register_camera cpia_pp.o: unresolved symbol parport_pc_read_fifo cpia_pp.o: unresolved symbol parport_register_device cpia_pp.o: unresolved symbol parport_pc_enable_irq cpia_pp.o: unresolved symbol parport_claim cpia_pp.o: unresolved symbol parport_release cpia_pp.o: unresolved symbol parport_pc_disable_irq I don't know what else to try.... Help! Sang ===== Sang Y. Yum http://www.yumnet.dyndns.org/~sang San Diego, CA mailto:tdat@yahoo.com __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com From gleicon@uol.com.br Fri, 10 Mar 2000 15:12:27 -0300 Date: Fri, 10 Mar 2000 15:12:27 -0300 From: Gleicon S. Moraes gleicon@uol.com.br Subject: [cpia] Can't load cpia/cpia_pp modules parport suport compiled in the kernel or as module ? videodev compiled as module or built-in ? try to review your steps including the parport module and the videodev module... you must be forgetting something ... regards. Gleicon From tdat@yahoo.com Fri, 10 Mar 2000 10:19:55 -0800 (PST) Date: Fri, 10 Mar 2000 10:19:55 -0800 (PST) From: Sang Y. Yum tdat@yahoo.com Subject: [cpia] Can't load cpia/cpia_pp modules --- "Gleicon S. Moraes" wrote: > parport suport compiled in the kernel or as module ? > videodev compiled as module or built-in ? > try to review your steps including the parport > module and the videodev > module... > you must be forgetting something ... > I don't have access to my machine at this point but I remember doing /sbin/lsmod and seeing all necessary modules specified in README file already loaded. I will post the output from /sbin/lsmod tonight. Sang ===== Sang Y. Yum http://www.yumnet.dyndns.org/~sang San Diego, CA mailto:tdat@yahoo.com __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com From tdat@yahoo.com Fri, 10 Mar 2000 18:52:32 -0800 (PST) Date: Fri, 10 Mar 2000 18:52:32 -0800 (PST) From: Sang Y. Yum tdat@yahoo.com Subject: [cpia] Can't load cpia/cpia_pp modules As promised, here is the output from /sbin/lsmod: [root@pikatsu module]# /sbin/lsmod Module Size Used by tuner 2060 0 videodev 2592 0 (autoclean) i2c 4192 1 (autoclean) [tuner] [snip] [root@pikatsu module]# /sbin/modprobe parport [root@pikatsu module]# /sbin/modprobe parport_pc [root@pikatsu module]# /sbin/lsmod Module Size Used by parport_pc 7604 0 (unused) parport 8084 0 [parport_pc] tuner 2060 0 videodev 2592 0 (autoclean) i2c 4192 1 (autoclean) [tuner] [snip] So far, so good. When I did this: [root@pikatsu module]# /sbin/insmod parport_probe I got this in /var/log/messages: Mar 10 18:50:47 localhost kernel: parport0: no IEEE-128 Hmmm, it looks like my WebCamII isn't even detected. It's all downhill from here. [root@pikatsu module]# /sbin/insmod cpia.o /var/log/messages:Mar 10 18:54:17 localhost kernel: V4L-Driver for Vision CPiA based cameras v0.7.3 Mar 10 18:54:17 localhost insmod: /lib/modules/2.2.14-15mdk/video/cpia_pp.o: unresolved symbol cpia_unregister_camera Mar 10 18:54:17 localhost insmod: /lib/modules/2.2.14-15mdk/video/cpia_pp.o: unresolved symbol cpia_register_camera [root@pikatsu module]# /sbin/insmod cpia_pp.o cpia_pp.o: init_module: Device or resource busy /var/log/messages: Mar 10 18:55:03 localhost kernel: Parallel port driver for Vision CPiA based cameras v0.7.3 Mar 10 18:55:03 localhost kernel: 0 camera(s) found I would appreciate any help. Sang ===== Sang Y. Yum http://www.yumnet.dyndns.org/~sang San Diego, CA mailto:tdat@yahoo.com __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com From tdat@yahoo.com Sat, 11 Mar 2000 00:41:15 -0800 (PST) Date: Sat, 11 Mar 2000 00:41:15 -0800 (PST) From: Sang Y. Yum tdat@yahoo.com Subject: [cpia] Can't load cpia/cpia_pp modules Ok, I made some progress. I went over to creative.com and noticed that one of the requirement for WebCam II is that the parallel port has to be set to "ECP" mode. After I made that change, I retried loadig the drivers and this is what I got: parport0: PC-style at 0x378 (0x778) [SPP,ECP,ECPPS2] parport0: read2 timeout. parport0: Multimedia device, VLSI Vision Ltd PPC2 Camera V4L-Driver for Vision CPiA based cameras v0.7.3 Parallel port driver for Vision CPiA based cameras v0.7.3 using PIO mode cpia.c(31360):goto_low_power(2317):04 00 00 00 00 00 10 00 cpia.c(31368):goto_high_power(2300):camera now in HIGH power state cpia.c(31369):goto_low_power(2314):camera now in LOW power state cpia.c(31377):goto_high_power(2300):camera now in HIGH power state cpia.c(31377):reset_camera(2448):fatal_error: 0x20 cpia.c(31377):reset_camera(2450):vp_status: 0x09 1 camera(s) found Even though the second and third line from the bottom are a bit scary, I proceeded with compiling gqcam in client directory. But, executing it gives: [sang@pikatsu client]$ gqcam ioctl (VIDIOCSWIN): Invalid argument Sigh. Now what? Sang ===== Sang Y. Yum http://www.yumnet.dyndns.org/~sang San Diego, CA mailto:tdat@yahoo.com __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com From sbertin@mindspring.com Sat, 11 Mar 2000 17:04:08 -0500 (EST) Date: Sat, 11 Mar 2000 17:04:08 -0500 (EST) From: sbertin@mindspring.com sbertin@mindspring.com Subject: [cpia] cpia-0.7.4 & SourceForge update SourceForge is now up to date and I've released cpia-0.7.4 there. If you haven't been to the SourceForge page yet, the address is http://webcam.sourceforge.net. The Project Home link on the left will take you to the SourceForge project page where you can access the CVS repository and previous releases. If you want CVS write access, please contact either Jarl of myself with your SourceForge username to be added to the list of developers. 2000-03-11 v0.7.4 Patch from Peter Pregler : - Fix missing free_dma Patch from Rich I recently was talking to the X developer here and explaining to him the > current CPiA driver, he urged me to use xvimage support under the new > version of XFree (4.0). It'll do color conversion and scaling all through > hardware which supports it (Matrox, etc). Hmmm, I am tempted to play around with my G400 as soon as I have 4.0 running. :) But I still think this should be part of the v4l-layer (some sort of internal auxilliary library) and not the cpia-driver. Was there any discussion about this on the v4l-lists? If not I will raise the issue there. -Peter ------------------------------- Even the thought that a ship was waiting to take him back to Earth did not wipe out the sense of loss he felt at that moment. ------------------------------- Email: Peter.Pregler@risc.uni-linz.ac.at Peter Pregler / RISC, University of Linz, Austria From jerdfelt@sventech.com Sun, 12 Mar 2000 23:38:45 -0500 Date: Sun, 12 Mar 2000 23:38:45 -0500 From: Johannes Erdfelt jerdfelt@sventech.com Subject: [cpia] profiling device drivers On Sun, Mar 12, 2000, Peter Pregler wrote: > > On 09-Mar-2000 Johannes Erdfelt wrote: > > I recently was talking to the X developer here and explaining to him the > > current CPiA driver, he urged me to use xvimage support under the new > > version of XFree (4.0). It'll do color conversion and scaling all through > > hardware which supports it (Matrox, etc). > > Hmmm, I am tempted to play around with my G400 as soon as I have 4.0 running. > :) But I still think this should be part of the v4l-layer (some sort of > internal auxilliary library) and not the cpia-driver. Was there any discussion > about this on the v4l-lists? If not I will raise the issue there. I don't think so. He was also telling me about an X extension which is a wrapper around V4L which handles all of this stuff and allows user space drivers to be written. I haven't looked up anything about it yet, but it sounds like something to investigate. JE From tdat@yahoo.com Sun, 12 Mar 2000 20:56:56 -0800 (PST) Date: Sun, 12 Mar 2000 20:56:56 -0800 (PST) From: Sang Y. Yum tdat@yahoo.com Subject: [cpia] gqcam with Creative WebCam II Cory, I hope you don't mind me asking for technical assitance but I practically ran out of things to try. As specified in the subject, I'm trying to get WebCam II Parallel port version with gqcam. I've successfully loaded all the drivers without any error. My camera is detected by the drivers, as shown below: Mar 12 20:51:11 localhost kernel: bttv0: Brooktree Bt878 (rev 2) bus: 0, devfn: 120, irq: 10, memory: 0xeddfd000. Mar 12 20:51:11 localhost kernel: PCI: Enabling bus mastering for device 00:78 Mar 12 20:51:11 localhost kernel: bttv: 1 Bt8xx card(s) found. Mar 12 20:51:11 localhost kernel: bttv0: Hauppauge eeprom: tuner=Philips FI1236 MK2 (2) Mar 12 20:51:11 localhost kernel: bttv0: NO fader chip: TEA6300 Mar 12 20:51:11 localhost kernel: bttv0: model: BT878(Hauppauge new) Mar 12 20:51:23 localhost kernel: parport0: PC-style at 0x378 (0x778) [SPP,ECP,ECPPS2] Mar 12 20:51:26 localhost kernel: parport0: read2 timeout. Mar 12 20:51:26 localhost kernel: parport0: Multimedia device, VLSI Vision Ltd PPC2 Camera Mar 12 20:51:47 localhost kernel: V4L-Driver for Vision CPiA based cameras v0.7.3 Mar 12 20:51:47 localhost modprobe: can't locate module cpia_pp Mar 12 20:51:52 localhost kernel: Parallel port driver for Vision CPiA based cameras v0.7.3 Mar 12 20:51:52 localhost kernel: using PIO mode Mar 12 20:51:52 localhost kernel: 1 camera(s) found When I execute gqcam (0.6 version), the window comes up but fails to show anything. When I do File->Open Camera and select /dev/video, gqcam terminates with the message: [sang@pikatsu gqcam-0.6]$ ./gqcam /dev/video: Device or resource busy As you might have guess from the first output, I also have WinTV tuner card installed, which is configured and working. I have a feeling that it's somehow interfering with my WebCam. When gqcam comes up, it has "Gqcam - BT878 (Hauppaug new)" in the title bar. Hauppaug is the manufacturer of WinTV tuner card. Here is the list of modules loaded before I execute gqcam: [sang@pikatsu gqcam-0.6]$ /sbin/lsmod Module Size Used by cpia_pp 18904 0 cpia 48252 0 [cpia_pp] parport_probe 3588 0 parport_pc 7604 1 [cpia_pp] parport 8084 1 [cpia_pp parport_probe parport_pc] bttv 37432 0 videodev 2592 3 [cpia bttv] i2c 4192 1 [bttv] ip_masq_irc 1456 0 (unused) ip_masq_raudio 2896 0 (unused) ip_masq_ftp 3696 0 (unused) 3c59x 18632 1 (autoclean) ide-scsi 7584 0 supermount 14880 3 (autoclean) nls_iso8859-1 2052 1 (autoclean) nls_cp437 3580 1 (autoclean) vfat 11004 1 (autoclean) fat 32640 1 (autoclean) [vfat] emu10k1 56212 0 soundcore 3524 5 [emu10k1] I tried gqcam with bttv module unloaded but that seemed to remove /dev/video deivce altogether. Sorry for a length note. If you have any suggestion, I would really appreciate it. Sang ===== Sang Y. Yum http://www.yumnet.dyndns.org/~sang San Diego, CA mailto:tdat@yahoo.com __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com From Peter.Pregler@risc.uni-linz.ac.at Mon, 13 Mar 2000 09:47:35 +0100 (CET) Date: Mon, 13 Mar 2000 09:47:35 +0100 (CET) From: Peter Pregler Peter.Pregler@risc.uni-linz.ac.at Subject: [cpia] gqcam with Creative WebCam II On 13-Mar-2000 Sang Y. Yum wrote: > When I execute gqcam (0.6 version), the window comes > up but fails to show anything. When I do File->Open > Camera and select /dev/video, gqcam terminates with > the message: > > [sang@pikatsu gqcam-0.6]$ ./gqcam > /dev/video: Device or resource busy > > > As you might have guess from the first output, I also > have WinTV tuner card installed, which is configured > and working. I have a feeling that it's somehow > interfering with my WebCam. When gqcam comes up, it > has "Gqcam - BT878 (Hauppaug new)" in the title bar. > Hauppaug is the manufacturer of WinTV tuner card. Check in /proc/cpia what file is there. Is it video0 or video1. Depending on the insmod-order the device attached to the two video-devices varies. Try to start gqcam with the correct device file (either /dev/video0 or /dev/video1) and have a look at the syslog-output. -Peter ------------------------------- Email: Peter.Pregler@risc.uni-linz.ac.at WWW: http://www.risc.uni-linz.ac.at/people/ppregler From tdat@yahoo.com Mon, 13 Mar 2000 07:39:07 -0800 (PST) Date: Mon, 13 Mar 2000 07:39:07 -0800 (PST) From: Sang Y. Yum tdat@yahoo.com Subject: [cpia] gqcam with Creative WebCam II > > Check in /proc/cpia what file is there. Is it video0 > or video1. Depending > on the insmod-order the device attached to the two > video-devices varies. > Try to start gqcam with the correct device file > (either /dev/video0 or > /dev/video1) and have a look at the syslog-output. > > -Peter > Depending on how the videodev module and others were loaded (either manually or automatically by executing xawtv), cpia_pp.o fails to load properly. In any case, I was able to load cpia and cpia_pp without any error and I have video1 in /proc/cpia: [root@pikatsu module]# insmod cpia.o [root@pikatsu module]# insmod cpia_pp.o [root@pikatsu module]# ls /proc/cpia video1 I executed gqcam and selected /dev/video1 by going File->Open Camera menu. I received this error: [sang@pikatsu gqcam-0.6]$ gqcam /dev/video: Input/output error I dont' think this is a permission problem. [root@pikatsu gqcam-0.6]# chmod og+rw /dev/video1 [root@pikatsu gqcam-0.6]# ls -l /dev/video1 crw-rw-rw- 1 sang root 81, 1 Sep 21 07:05 /dev/video1 [root@pikatsu gqcam-0.6]# ls -l /dev/video1 crw-rw-rw- 1 sang root 81, 1 Sep 21 07:05 /dev/video1 [root@pikatsu gqcam-0.6]# ls -l /dev/video lrwxrwxrwx 1 root root 6 Feb 28 09:34 /dev/video -> video0 Still same error. Thanks. Sang ===== Sang Y. Yum http://www.yumnet.dyndns.org/~sang San Diego, CA mailto:tdat@yahoo.com __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com From Peter.Pregler@risc.uni-linz.ac.at Mon, 13 Mar 2000 16:47:13 +0100 (CET) Date: Mon, 13 Mar 2000 16:47:13 +0100 (CET) From: Peter Pregler Peter.Pregler@risc.uni-linz.ac.at Subject: [cpia] gqcam with Creative WebCam II On 13-Mar-2000 Sang Y. Yum wrote: > > I executed gqcam and selected /dev/video1 by going > File->Open Camera menu. I received this error: > > [sang@pikatsu gqcam-0.6]$ gqcam > /dev/video: Input/output error > > I dont' think this is a permission problem. I agree. But /dev/video apparently points to video0 on your system which is not where your camera is. So either the message above is incorrect, gqcam has a bug or there is something else. As a short test try out to link /dev/video to /dev/video1 or wherever the cpia-camera is. That should remove problems related to applications opening the wrong device. In any case the output of syslog is important. You should see there some messages from the driver if it was compiled with _CPIA_DEBUG_. -Peter ------------------------------- Email: Peter.Pregler@risc.uni-linz.ac.at WWW: http://www.risc.uni-linz.ac.at/people/ppregler From vincent@linuxbe.org Mon, 13 Mar 2000 22:19:03 +0100 (CET) Date: Mon, 13 Mar 2000 22:19:03 +0100 (CET) From: vincent vincent@linuxbe.org Subject: [cpia] usage under the 2.3.51 kernel This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1877363535-952982338=:18479 Content-Type: TEXT/PLAIN; charset=US-ASCII I try to use the CPIA driver and I ve got the following error: [root@jukebox module]# /sbin/insmod cpia.o cpia.o: unresolved symbol video_register_device cpia.o: unresolved symbol video_unregister_device I give you my "dmesg" on attach also I don't know how the /dev/video is created /dev/video: No such device in the doc it s talk about "video 4 linux" but I don't see that in the kernel config .. Hope somene can help me .. --0-1877363535-952982338=:18479 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="dmesg.txt" Content-ID: Content-Description: Content-Disposition: attachment; filename="dmesg.txt" Content-Transfer-Encoding: BASE64 KQ0KQUNQSTogIkFTVVMiIGZvdW5kIGF0IDB4MDAwZjU2MDANCmFwbTogQklP UyB2ZXJzaW9uIDEuMiBGbGFncyAweDAzIChEcml2ZXIgdmVyc2lvbiAxLjEz KQ0KYXBtOiBvdmVycmlkZGVuIGJ5IEFDUEkuDQpTdGFydGluZyBrc3dhcGQg djEuNg0KU2VyaWFsIGRyaXZlciB2ZXJzaW9uIDQuOTIgKDIwMDAtMS0yNykg d2l0aCBNQU5ZX1BPUlRTIFNIQVJFX0lSUSBTRVJJQUxfUENJIElTQVBOUCBl bmFibGVkDQp0dHlTMDAgYXQgMHgwM2Y4IChpcnEgPSA0KSBpcyBhIDE2NTUw QQ0KdHR5UzAxIGF0IDB4MDJmOCAoaXJxID0gMykgaXMgYSAxNjU1MEENCnB0 eTogMjU2IFVuaXg5OCBwdHlzIGNvbmZpZ3VyZWQNClVuaWZvcm0gTXVsdGkt UGxhdGZvcm0gRS1JREUgZHJpdmVyIFJldmlzaW9uOiA2LjMwDQppZGU6IEFz c3VtaW5nIDQwTUh6IHN5c3RlbSBidXMgc3BlZWQgZm9yIFBJTyBtb2Rlczsg b3ZlcnJpZGUgd2l0aCBpZGVidXM9eHgNClZQX0lERTogSURFIGNvbnRyb2xs ZXIgb24gUENJIGJ1cyAwMCBkZXYgMjENClZQX0lERTogbm90IDEwMCUgbmF0 aXZlIG1vZGU6IHdpbGwgcHJvYmUgaXJxcyBsYXRlcg0KaGRhOiBJQk0tRFBU QS0zNzIwNTAsIEFUQSBESVNLIGRyaXZlDQpoZGM6IEFUQVBJIENEUk9NLCBB VEFQSSBDRFJPTSBkcml2ZQ0KaWRlMCBhdCAweDFmMC0weDFmNywweDNmNiBv biBpcnEgMTQNCmlkZTEgYXQgMHgxNzAtMHgxNzcsMHgzNzYgb24gaXJxIDE1 DQpoZGE6IElCTS1EUFRBLTM3MjA1MCwgMTk1NzRNQiB3LzE5NjFrQiBDYWNo ZSwgQ0hTPTI0OTUvMjU1LzYzDQpodWIuYzogcG9ydCAxIGNvbm5lY3Rpb24g Y2hhbmdlDQpoZGM6IEFUQVBJIDRYIENELVJPTSBkcml2ZSwgMTI4a0IgQ2Fj aGUNClVuaWZvcm0gQ0QtUk9NIGRyaXZlciBSZXZpc2lvbjogMy4wNw0KUGFy dGl0aW9uIGNoZWNrOg0KIGhkYTo8Nz5odWIuYzogcG9ydHN0YXR1cyAzMDAs IGNoYW5nZSAzLCBMb3cgU3BlZWQNCmh1Yi5jOiBwb3J0IDEgZW5hYmxlIGNo YW5nZSwgc3RhdHVzIDMwMA0KaHViLmM6IHBvcnQgMiBjb25uZWN0aW9uIGNo YW5nZQ0KIGhkYTEgaGRhMiBoZGEzIGhkYTQgPCBoZGE1IGhkYTYgPg0KRmxv cHB5IGRyaXZlKHMpOiBmZDAgaXMgMS40NE0NCkZEQyAwIGlzIGEgcG9zdC0x OTkxIDgyMDc3DQpbZHJtXSBJbml0aWFsaXplZCB0ZGZ4IDAuMC4xIDE5OTkx MDA5IG9uIG1pbm9yIDYzDQpWRlM6IE1vdW50ZWQgcm9vdCAoZXh0MiBmaWxl c3lzdGVtKSByZWFkb25seS4NCkZyZWVpbmcgdW51c2VkIGtlcm5lbCBtZW1v cnk6IDE2MGsgZnJlZWQNCmh1Yi5jOiBwb3J0c3RhdHVzIDEwMSwgY2hhbmdl IDMsIEhpZ2ggU3BlZWQNCmh1Yi5jOiBwb3J0c3RhdHVzIDEwMywgY2hhbmdl IDAsIEhpZ2ggU3BlZWQNCnVzYi5jOiBVU0IgbmV3IGRldmljZSBjb25uZWN0 LCBhc3NpZ25lZCBkZXZpY2UgbnVtYmVyIDINCnVzYi5jOiBrbWFsbG9jIElG IGMzZjk5MTYwLCBudW1pZiAxDQp1c2IuYzogbmV3IGRldmljZSBzdHJpbmdz OiBNZnI9MCwgUHJvZHVjdD0wLCBTZXJpYWxOdW1iZXI9MA0KdXNiLmM6IHVu aGFuZGxlZCBpbnRlcmZhY2VzIG9uIGRldmljZQ0KdXNiLmM6IFRoaXMgZGV2 aWNlIGlzIG5vdCByZWNvZ25pemVkIGJ5IGFueSBpbnN0YWxsZWQgVVNCIGRy aXZlci4NCiAgTGVuZ3RoICAgICAgICAgICAgICA9IDE4DQogIERlc2NyaXB0 b3JUeXBlICAgICAgPSAwMQ0KICBVU0IgdmVyc2lvbiAgICAgICAgID0gMS4w MA0KICBWZW5kb3I6UHJvZHVjdCAgICAgID0gMDU1MzowMDAyDQogIE1heFBh Y2tldFNpemUwICAgICAgPSA4DQogIE51bUNvbmZpZ3VyYXRpb25zICAgPSAx DQogIERldmljZSB2ZXJzaW9uICAgICAgPSAxLjAwDQogIERldmljZSBDbGFz czpTdWJDbGFzczpQcm90b2NvbCA9IDAwOjAwOjAwDQogICAgUGVyLWludGVy ZmFjZSBjbGFzc2VzDQpDb25maWd1cmF0aW9uOg0KICBiTGVuZ3RoICAgICAg ICAgICAgID0gICAgOQ0KICBiRGVzY3JpcHRvclR5cGUgICAgID0gICAwMg0K ICB3VG90YWxMZW5ndGggICAgICAgID0gMDA0OQ0KICBiTnVtSW50ZXJmYWNl cyAgICAgID0gICAwMQ0KICBiQ29uZmlndXJhdGlvblZhbHVlID0gICAwMQ0K ICBpQ29uZmlndXJhdGlvbiAgICAgID0gICAwMA0KICBibUF0dHJpYnV0ZXMg ICAgICAgID0gICA4MA0KICBNYXhQb3dlciAgICAgICAgICAgID0gIDQwMG1B DQoNCiAgSW50ZXJmYWNlOiAwDQogIEFsdGVybmF0ZSBTZXR0aW5nOiAgMA0K ICAgIGJMZW5ndGggICAgICAgICAgICAgPSAgICA5DQogICAgYkRlc2NyaXB0 b3JUeXBlICAgICA9ICAgMDQNCiAgICBiSW50ZXJmYWNlTnVtYmVyICAgID0g ICAwMQ0KICAgIGJBbHRlcm5hdGVTZXR0aW5nICAgPSAgIDAwDQogICAgYk51 bUVuZHBvaW50cyAgICAgICA9ICAgMDENCiAgICBiSW50ZXJmYWNlIENsYXNz OlN1YkNsYXNzOlByb3RvY29sID0gICBmZjowMDpmZg0KICAgIGlJbnRlcmZh Y2UgICAgICAgICAgPSAgIDAwDQogICAgRW5kcG9pbnQ6DQogICAgICBiTGVu Z3RoICAgICAgICAgICAgID0gICAgNw0KICAgICAgYkRlc2NyaXB0b3JUeXBl ICAgICA9ICAgMDUNCiAgICAgIGJFbmRwb2ludEFkZHJlc3MgICAgPSAgIDgx IChpbikNCiAgICAgIGJtQXR0cmlidXRlcyAgICAgICAgPSAgIDAxIChJc29j aHJvbm91cykNCiAgICAgIHdNYXhQYWNrZXRTaXplICAgICAgPSAwMDAwDQog ICAgICBiSW50ZXJ2YWwgICAgICAgICAgID0gICAwMQ0KICBBbHRlcm5hdGUg U2V0dGluZzogIDENCiAgICBiTGVuZ3RoICAgICAgICAgICAgID0gICAgOQ0K ICAgIGJEZXNjcmlwdG9yVHlwZSAgICAgPSAgIDA0DQogICAgYkludGVyZmFj ZU51bWJlciAgICA9ICAgMDENCiAgICBiQWx0ZXJuYXRlU2V0dGluZyAgID0g ICAwMQ0KICAgIGJOdW1FbmRwb2ludHMgICAgICAgPSAgIDAxDQogICAgYklu dGVyZmFjZSBDbGFzczpTdWJDbGFzczpQcm90b2NvbCA9ICAgZmY6MDA6ZmYN CiAgICBpSW50ZXJmYWNlICAgICAgICAgID0gICAwMA0KICAgIEVuZHBvaW50 Og0KICAgICAgYkxlbmd0aCAgICAgICAgICAgICA9ICAgIDcNCiAgICAgIGJE ZXNjcmlwdG9yVHlwZSAgICAgPSAgIDA1DQogICAgICBiRW5kcG9pbnRBZGRy ZXNzICAgID0gICA4MSAoaW4pDQogICAgICBibUF0dHJpYnV0ZXMgICAgICAg ID0gICAwMSAoSXNvY2hyb25vdXMpDQogICAgICB3TWF4UGFja2V0U2l6ZSAg ICAgID0gMDFjMA0KICAgICAgYkludGVydmFsICAgICAgICAgICA9ICAgMDEN CiAgQWx0ZXJuYXRlIFNldHRpbmc6ICAyDQogICAgYkxlbmd0aCAgICAgICAg ICAgICA9ICAgIDkNCiAgICBiRGVzY3JpcHRvclR5cGUgICAgID0gICAwNA0K ICAgIGJJbnRlcmZhY2VOdW1iZXIgICAgPSAgIDAxDQogICAgYkFsdGVybmF0 ZVNldHRpbmcgICA9ICAgMDINCiAgICBiTnVtRW5kcG9pbnRzICAgICAgID0g ICAwMQ0KICAgIGJJbnRlcmZhY2UgQ2xhc3M6U3ViQ2xhc3M6UHJvdG9jb2wg PSAgIGZmOjAwOmZmDQogICAgaUludGVyZmFjZSAgICAgICAgICA9ICAgMDAN CiAgICBFbmRwb2ludDoNCiAgICAgIGJMZW5ndGggICAgICAgICAgICAgPSAg ICA3DQogICAgICBiRGVzY3JpcHRvclR5cGUgICAgID0gICAwNQ0KICAgICAg YkVuZHBvaW50QWRkcmVzcyAgICA9ICAgODEgKGluKQ0KICAgICAgYm1BdHRy aWJ1dGVzICAgICAgICA9ICAgMDEgKElzb2Nocm9ub3VzKQ0KICAgICAgd01h eFBhY2tldFNpemUgICAgICA9IDAyYzANCiAgICAgIGJJbnRlcnZhbCAgICAg ICAgICAgPSAgIDAxDQogIEFsdGVybmF0ZSBTZXR0aW5nOiAgMw0KICAgIGJM ZW5ndGggICAgICAgICAgICAgPSAgICA5DQogICAgYkRlc2NyaXB0b3JUeXBl ICAgICA9ICAgMDQNCiAgICBiSW50ZXJmYWNlTnVtYmVyICAgID0gICAwMQ0K ICAgIGJBbHRlcm5hdGVTZXR0aW5nICAgPSAgIDAzDQogICAgYk51bUVuZHBv aW50cyAgICAgICA9ICAgMDENCiAgICBiSW50ZXJmYWNlIENsYXNzOlN1YkNs YXNzOlByb3RvY29sID0gICBmZjowMDpmZg0KICAgIGlJbnRlcmZhY2UgICAg ICAgICAgPSAgIDAwDQogICAgRW5kcG9pbnQ6DQogICAgICBiTGVuZ3RoICAg ICAgICAgICAgID0gICAgNw0KICAgICAgYkRlc2NyaXB0b3JUeXBlICAgICA9 ICAgMDUNCiAgICAgIGJFbmRwb2ludEFkZHJlc3MgICAgPSAgIDgxIChpbikN CiAgICAgIGJtQXR0cmlidXRlcyAgICAgICAgPSAgIDAxIChJc29jaHJvbm91 cykNCiAgICAgIHdNYXhQYWNrZXRTaXplICAgICAgPSAwM2MwDQogICAgICBi SW50ZXJ2YWwgICAgICAgICAgID0gICAwMQ0KaHViLmM6IHBvcnQgMiBlbmFi bGUgY2hhbmdlLCBzdGF0dXMgMTAxDQpodWIuYzogYWxyZWFkeSBydW5uaW5n IHBvcnQgMiBkaXNhYmxlZCBieSBodWIgKEVNST8pLCByZS1lbmFibGluZy4u Lg0KaHViLmM6IHBvcnRzdGF0dXMgMTAzLCBjaGFuZ2UgMCwgSGlnaCBTcGVl ZA0KdXNiLmM6IFVTQiBkaXNjb25uZWN0IG9uIGRldmljZSAyDQpodWIuYzog cG9ydHN0YXR1cyAxMDMsIGNoYW5nZSAwLCBIaWdoIFNwZWVkDQp1c2IuYzog VVNCIG5ldyBkZXZpY2UgY29ubmVjdCwgYXNzaWduZWQgZGV2aWNlIG51bWJl ciAyDQp1c2IuYzoga21hbGxvYyBJRiBjM2Y5OTFhMCwgbnVtaWYgMQ0KdXNi LmM6IG5ldyBkZXZpY2Ugc3RyaW5nczogTWZyPTAsIFByb2R1Y3Q9MCwgU2Vy aWFsTnVtYmVyPTANCnVzYi5jOiB1bmhhbmRsZWQgaW50ZXJmYWNlcyBvbiBk ZXZpY2UNCnVzYi5jOiBUaGlzIGRldmljZSBpcyBub3QgcmVjb2duaXplZCBi eSBhbnkgaW5zdGFsbGVkIFVTQiBkcml2ZXIuDQogIExlbmd0aCAgICAgICAg ICAgICAgPSAxOA0KICBEZXNjcmlwdG9yVHlwZSAgICAgID0gMDENCiAgVVNC IHZlcnNpb24gICAgICAgICA9IDEuMDANCiAgVmVuZG9yOlByb2R1Y3QgICAg ICA9IDA1NTM6MDAwMg0KICBNYXhQYWNrZXRTaXplMCAgICAgID0gOA0KICBO dW1Db25maWd1cmF0aW9ucyAgID0gMQ0KICBEZXZpY2UgdmVyc2lvbiAgICAg ID0gMS4wMA0KICBEZXZpY2UgQ2xhc3M6U3ViQ2xhc3M6UHJvdG9jb2wgPSAw MDowMDowMA0KICAgIFBlci1pbnRlcmZhY2UgY2xhc3Nlcw0KQ29uZmlndXJh dGlvbjoNCiAgYkxlbmd0aCAgICAgICAgICAgICA9ICAgIDkNCiAgYkRlc2Ny aXB0b3JUeXBlICAgICA9ICAgMDINCiAgd1RvdGFsTGVuZ3RoICAgICAgICA9 IDAwNDkNCiAgYk51bUludGVyZmFjZXMgICAgICA9ICAgMDENCiAgYkNvbmZp Z3VyYXRpb25WYWx1ZSA9ICAgMDENCiAgaUNvbmZpZ3VyYXRpb24gICAgICA9 ICAgMDANCiAgYm1BdHRyaWJ1dGVzICAgICAgICA9ICAgODANCiAgTWF4UG93 ZXIgICAgICAgICAgICA9ICA0MDBtQQ0KDQogIEludGVyZmFjZTogMA0KICBB bHRlcm5hdGUgU2V0dGluZzogIDANCiAgICBiTGVuZ3RoICAgICAgICAgICAg ID0gICAgOQ0KICAgIGJEZXNjcmlwdG9yVHlwZSAgICAgPSAgIDA0DQogICAg YkludGVyZmFjZU51bWJlciAgICA9ICAgMDENCiAgICBiQWx0ZXJuYXRlU2V0 dGluZyAgID0gICAwMA0KICAgIGJOdW1FbmRwb2ludHMgICAgICAgPSAgIDAx DQogICAgYkludGVyZmFjZSBDbGFzczpTdWJDbGFzczpQcm90b2NvbCA9ICAg ZmY6MDA6ZmYNCiAgICBpSW50ZXJmYWNlICAgICAgICAgID0gICAwMA0KICAg IEVuZHBvaW50Og0KICAgICAgYkxlbmd0aCAgICAgICAgICAgICA9ICAgIDcN CiAgICAgIGJEZXNjcmlwdG9yVHlwZSAgICAgPSAgIDA1DQogICAgICBiRW5k cG9pbnRBZGRyZXNzICAgID0gICA4MSAoaW4pDQogICAgICBibUF0dHJpYnV0 ZXMgICAgICAgID0gICAwMSAoSXNvY2hyb25vdXMpDQogICAgICB3TWF4UGFj a2V0U2l6ZSAgICAgID0gMDAwMA0KICAgICAgYkludGVydmFsICAgICAgICAg ICA9ICAgMDENCiAgQWx0ZXJuYXRlIFNldHRpbmc6ICAxDQogICAgYkxlbmd0 aCAgICAgICAgICAgICA9ICAgIDkNCiAgICBiRGVzY3JpcHRvclR5cGUgICAg ID0gICAwNA0KICAgIGJJbnRlcmZhY2VOdW1iZXIgICAgPSAgIDAxDQogICAg YkFsdGVybmF0ZVNldHRpbmcgICA9ICAgMDENCiAgICBiTnVtRW5kcG9pbnRz ICAgICAgID0gICAwMQ0KICAgIGJJbnRlcmZhY2UgQ2xhc3M6U3ViQ2xhc3M6 UHJvdG9jb2wgPSAgIGZmOjAwOmZmDQogICAgaUludGVyZmFjZSAgICAgICAg ICA9ICAgMDANCiAgICBFbmRwb2ludDoNCiAgICAgIGJMZW5ndGggICAgICAg ICAgICAgPSAgICA3DQogICAgICBiRGVzY3JpcHRvclR5cGUgICAgID0gICAw NQ0KICAgICAgYkVuZHBvaW50QWRkcmVzcyAgICA9ICAgODEgKGluKQ0KICAg ICAgYm1BdHRyaWJ1dGVzICAgICAgICA9ICAgMDEgKElzb2Nocm9ub3VzKQ0K ICAgICAgd01heFBhY2tldFNpemUgICAgICA9IDAxYzANCiAgICAgIGJJbnRl cnZhbCAgICAgICAgICAgPSAgIDAxDQogIEFsdGVybmF0ZSBTZXR0aW5nOiAg Mg0KICAgIGJMZW5ndGggICAgICAgICAgICAgPSAgICA5DQogICAgYkRlc2Ny aXB0b3JUeXBlICAgICA9ICAgMDQNCiAgICBiSW50ZXJmYWNlTnVtYmVyICAg ID0gICAwMQ0KICAgIGJBbHRlcm5hdGVTZXR0aW5nICAgPSAgIDAyDQogICAg Yk51bUVuZHBvaW50cyAgICAgICA9ICAgMDENCiAgICBiSW50ZXJmYWNlIENs YXNzOlN1YkNsYXNzOlByb3RvY29sID0gICBmZjowMDpmZg0KICAgIGlJbnRl cmZhY2UgICAgICAgICAgPSAgIDAwDQogICAgRW5kcG9pbnQ6DQogICAgICBi TGVuZ3RoICAgICAgICAgICAgID0gICAgNw0KICAgICAgYkRlc2NyaXB0b3JU eXBlICAgICA9ICAgMDUNCiAgICAgIGJFbmRwb2ludEFkZHJlc3MgICAgPSAg IDgxIChpbikNCiAgICAgIGJtQXR0cmlidXRlcyAgICAgICAgPSAgIDAxIChJ c29jaHJvbm91cykNCiAgICAgIHdNYXhQYWNrZXRTaXplICAgICAgPSAwMmMw DQogICAgICBiSW50ZXJ2YWwgICAgICAgICAgID0gICAwMQ0KICBBbHRlcm5h dGUgU2V0dGluZzogIDMNCiAgICBiTGVuZ3RoICAgICAgICAgICAgID0gICAg OQ0KICAgIGJEZXNjcmlwdG9yVHlwZSAgICAgPSAgIDA0DQogICAgYkludGVy ZmFjZU51bWJlciAgICA9ICAgMDENCiAgICBiQWx0ZXJuYXRlU2V0dGluZyAg ID0gICAwMw0KICAgIGJOdW1FbmRwb2ludHMgICAgICAgPSAgIDAxDQogICAg YkludGVyZmFjZSBDbGFzczpTdWJDbGFzczpQcm90b2NvbCA9ICAgZmY6MDA6 ZmYNCiAgICBpSW50ZXJmYWNlICAgICAgICAgID0gICAwMA0KICAgIEVuZHBv aW50Og0KICAgICAgYkxlbmd0aCAgICAgICAgICAgICA9ICAgIDcNCiAgICAg IGJEZXNjcmlwdG9yVHlwZSAgICAgPSAgIDA1DQogICAgICBiRW5kcG9pbnRB ZGRyZXNzICAgID0gICA4MSAoaW4pDQogICAgICBibUF0dHJpYnV0ZXMgICAg ICAgID0gICAwMSAoSXNvY2hyb25vdXMpDQogICAgICB3TWF4UGFja2V0U2l6 ZSAgICAgID0gMDNjMA0KICAgICAgYkludGVydmFsICAgICAgICAgICA9ICAg MDENCkFkZGluZyBTd2FwOiA3MjI4OGsgc3dhcC1zcGFjZSAocHJpb3JpdHkg LTEpDQpFWFQyLWZzIHdhcm5pbmc6IG1vdW50aW5nIHVuY2hlY2tlZCBmcywg cnVubmluZyBlMmZzY2sgaXMgcmVjb21tZW5kZWQNCm5lMmstcGNpLmM6dnBy ZS0xLjAwZSA1LzI3Lzk5IEQuIEJlY2tlci9QLiBHb3J0bWFrZXIgaHR0cDov L2Nlc2Rpcy5nc2ZjLm5hc2EuZ292L2xpbnV4L2RyaXZlcnMvbmUyay1wY2ku aHRtbA0KbmUyay1wY2kuYzp2cHJlLTEuMDBlIDUvMjcvOTkgRC4gQmVja2Vy L1AuIEdvcnRtYWtlciBodHRwOi8vY2VzZGlzLmdzZmMubmFzYS5nb3YvbGlu dXgvZHJpdmVycy9uZTJrLXBjaS5odG1sDQpuZTJrLXBjaS5jOiBQQ0kgTkUy MDAwIGNsb25lICdSZWFsVGVrIFJUTC04MDI5JyBhdCBJL08gMHhkMDAwLCBJ UlEgMTAuDQpldGgwOiBSZWFsVGVrIFJUTC04MDI5IGZvdW5kIGF0IDB4ZDAw MCwgSVJRIDEwLCAwMDo0MDowNTo2ODozOTpFMy4NCg== --0-1877363535-952982338=:18479-- From sTYLe@WtAl.De Mon, 13 Mar 2000 22:49:06 +0100 Date: Mon, 13 Mar 2000 22:49:06 +0100 From: Bastian sTYLe@WtAl.De Subject: [cpia] still hoping anybody made some new experiences concerning the "10-10-..." problem ? -Bastian From sTYLe@WtAl.De Mon, 13 Mar 2000 22:51:41 +0100 Date: Mon, 13 Mar 2000 22:51:41 +0100 From: Bastian sTYLe@WtAl.De Subject: [cpia] usage under the 2.3.51 kernel At 22:19 13.3.2000 +0100, vincent wrote: >I try to use the CPIA driver and I ve got the following error: > >[root@jukebox module]# /sbin/insmod cpia.o >cpia.o: unresolved symbol video_register_device >cpia.o: unresolved symbol video_unregister_device > >I give you my "dmesg" on attach > >also I don't know how the /dev/video is created >/dev/video: No such device > >in the doc >it s talk about "video 4 linux" >but I don't see that in the kernel config .. have a look in Character Devices -> Video For Linux -> >Hope somene can help me .. > Bastian From claudio@helllabs.org Mon, 13 Mar 2000 19:14:15 -0300 (BRT) Date: Mon, 13 Mar 2000 19:14:15 -0300 (BRT) From: Claudio Matsuoka claudio@helllabs.org Subject: [cpia] usage under the 2.3.51 kernel On Mon, 13 Mar 2000, vincent wrote: > I try to use the CPIA driver and I ve got the following error: > [root@jukebox module]# /sbin/insmod cpia.o > cpia.o: unresolved symbol video_register_device > cpia.o: unresolved symbol video_unregister_device I've been using the module with many 2.3.4x and 2.3.50 kernels with no major problems. I'm still at 2.3.50 but I belive it should work on 2.3.51 as well. Make sure the video4linux support is enabled in the kernel configuration. > also I don't know how the /dev/video is created > /dev/video: No such device It's a character device with major 81 and minor 0, create it using mknod. > in the doc > it s talk about "video 4 linux" > but I don't see that in the kernel config .. Character devices ---> Video For Linux ---> Video For Linux claudio From Peter.Pregler@risc.uni-linz.ac.at Tue, 14 Mar 2000 08:42:03 +0100 (CET) Date: Tue, 14 Mar 2000 08:42:03 +0100 (CET) From: Peter Pregler Peter.Pregler@risc.uni-linz.ac.at Subject: [cpia] gqcam with Creative WebCam II On 14-Mar-2000 Sang Y. Yum wrote: > V4L-Driver for Vision CPiA based cameras v0.7.3 > Parallel port driver for Vision CPiA based cameras > v0.7.3 > using PIO mode > cpia.c(10063826):goto_low_power(2314):camera now in > LOW power state > cpia.c(10063833):goto_high_power(2300):camera now in > HIGH power state > cpia.c(10063833):reset_camera(2448):fatal_error: > 0x20 > cpia.c(10063833):reset_camera(2450):vp_status: > 0x09 > 1 camera(s) found > > What's that "fatal_error" doing there? That should be the source of your problem. Apparently the read of the firmware version et al. fails. I check that out. -Peter ------------------------------- Email: Peter.Pregler@risc.uni-linz.ac.at WWW: http://www.risc.uni-linz.ac.at/people/ppregler From Peter.Pregler@risc.uni-linz.ac.at Tue, 14 Mar 2000 08:52:47 +0100 (CET) Date: Tue, 14 Mar 2000 08:52:47 +0100 (CET) From: Peter Pregler Peter.Pregler@risc.uni-linz.ac.at Subject: [cpia] still hoping On 13-Mar-2000 Bastian wrote: > anybody made some new experiences concerning the "10-10-..." problem ? Not directly. I try to get some updated documentation for the 1.30 firmware and some hints about the correct camera-initialisation from VLSI. In the meantime you can try out the following: - did you try to run the camera under windows and a soft-boot (i.e. no power down) to linux? -Peter ------------------------------- Email: Peter.Pregler@risc.uni-linz.ac.at WWW: http://www.risc.uni-linz.ac.at/people/ppregler From schertha@uni-landau.de Tue, 14 Mar 2000 15:25:37 +0100 Date: Tue, 14 Mar 2000 15:25:37 +0100 From: Frank Scherthan schertha@uni-landau.de Subject: [cpia] Terratec Webcam works too :) Hi, I just wanted to let you know that the Terratec Webcam (USB) is working fine with the cpia_usb-driver :) -- So long and thanx for all the fish, Frank Scherthan _________________ __________ _________________________ |snail-mail: |Tel. |email: | | Frank Scherthan | 06341/ | schertha@uni-landau.de| | Marktstr. 105 | 60606 |_________________________| | 76829 Landau |__________| |_________________| From vincent@linuxbe.org Tue, 14 Mar 2000 18:06:49 +0100 Date: Tue, 14 Mar 2000 18:06:49 +0100 From: vincent vincent@linuxbe.org Subject: [cpia] "usb.h" is missing ? was: usage under the 2.3.51 kernel" apparently, the file "usb.h" is missing ? why ? another file can replace this ? [root@jukebox module]# make dep rm -f .depend make .depend make[1]: Entering directory `/tmp/cpia-0.7.4/module' echo '# Program dependencies' >.depend gcc -M -D_CPIA_DEBUG_ -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -pipe -fno-strength-reduce -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=686 -fomit-frame-pointer -fno-strength-reduce -I. -I/usr/src/linux/include -D__KERNEL__ -DMODULE -DCONFIG_VIDEO_CPIA_MODULE -DCONFIG_VIDEO_CPIA_PP_MODULE -DCONFIG_VIDEO_CPIA_PP_DMA *.c >>.depend cpia_usb.c:34: /usr/src/linux/drivers/usb/usb.h: No such file or directory make[1]: *** [.depend] Error 1 make[1]: Leaving directory `/tmp/cpia-0.7.4/module' make: *** [dep] Error 2 ]# ls /usr/src/linux/drivers/usb/usb*h /usr/src/linux/drivers/usb/usb-ohci.h /usr/src/linux/drivers/usb/usb-storage-debug.h /usr/src/linux/drivers/usb/usb-storage.h /usr/src/linux/drivers/usb/usb-uhci-debug.h /usr/src/linux/drivers/usb/usb-uhci.h /usr/src/linux/drivers/usb/usbdevice_fs.h Bastian wrote: > > At 22:19 13.3.2000 +0100, vincent wrote: > > >I try to use the CPIA driver and I ve got the following error: > > > >[root@jukebox module]# /sbin/insmod cpia.o > >cpia.o: unresolved symbol video_register_device > >cpia.o: unresolved symbol video_unregister_device > > > >I give you my "dmesg" on attach > > > >also I don't know how the /dev/video is created > >/dev/video: No such device > > > >in the doc > >it s talk about "video 4 linux" > >but I don't see that in the kernel config .. > > have a look in Character Devices -> Video For Linux -> > > >Hope somene can help me .. > > > > Bastian > > _______________________________________________ > cpia mailing list - cpia@risc.uni-linz.ac.at > http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia From sTYLe@WtAl.De Tue, 14 Mar 2000 18:11:03 +0100 Date: Tue, 14 Mar 2000 18:11:03 +0100 From: Bastian sTYLe@WtAl.De Subject: [cpia] still hoping At 08:52 14.3.2000 +0100, Peter Pregler wrote: >On 13-Mar-2000 Bastian wrote: > > anybody made some new experiences concerning the "10-10-..." problem ? > >Not directly. I try to get some updated documentation for the 1.30 my camera seems to have firmware version 1.00 >firmware and some hints about the correct camera-initialisation from VLSI. >In the meantime you can try out the following: > >- did you try to run the camera under windows and a soft-boot (i.e. no >power down) to linux? under windows it works. >-Peter > > >------------------------------- >Email: Peter.Pregler@risc.uni-linz.ac.at >WWW: http://www.risc.uni-linz.ac.at/people/ppregler regards, Bastian From tadavis@lbl.gov Tue, 14 Mar 2000 09:29:18 -0800 Date: Tue, 14 Mar 2000 09:29:18 -0800 From: Thomas Davis tadavis@lbl.gov Subject: [cpia] "usb.h" is missing ? was: usage under the 2.3.51 kernel" vincent wrote: > > apparently, the file "usb.h" is missing ? > why ? > > another file can replace this ? > replace "/usr/src/linux/usb/usb.h" with It was finally moved to the proper place in 2.3.51. -- ------------------------+-------------------------------------------------- Thomas Davis | PDSF Project Leader tadavis@lbl.gov | (510) 486-4524 | "Only a petabyte of data this year?" From Peter.Pregler@risc.uni-linz.ac.at Tue, 14 Mar 2000 18:37:43 +0100 (CET) Date: Tue, 14 Mar 2000 18:37:43 +0100 (CET) From: Peter Pregler Peter.Pregler@risc.uni-linz.ac.at Subject: [cpia] still hoping On 14-Mar-2000 Bastian wrote: > At 08:52 14.3.2000 +0100, Peter Pregler wrote: > >>On 13-Mar-2000 Bastian wrote: >> > anybody made some new experiences concerning the "10-10-..." problem >> > ? >> >>Not directly. I try to get some updated documentation for the 1.30 > > my camera seems to have firmware version 1.00 Actually it has version 1.02 (1.0) according to your postings. >>firmware and some hints about the correct camera-initialisation from >>VLSI. >>In the meantime you can try out the following: >> >>- did you try to run the camera under windows and a soft-boot (i.e. no >>power down) to linux? > > under windows it works. I guessed that. What I wanted to know is if windows does any initialisation that our driver does not. I checked out the mailing list archive and I cannot think of any good point to start debugging on my side anymore. Can you try out the following: - try out the driver version 0.4.4, that is the first one which should work reliable with 1.02 firmware, so we can see if any bug was introduced after that (http://download.sourceforge.net/webcam/cpia-0.4.4.tgz), do not activate dma please - can you boot your box fresh in emergency mode, load the parport-modules, v4l and the driver and _no_ other fency stuff, especially not the ppp/isdn stuff you got in the ooops, use vidcat or the like to grab a single frame to disk (or /dev/null ;), if it fails send me the syslog from boot to end, and also the output of the relevant proc-file (interrupt, parport, cpia). Sorry for not being of more help. But something in your setup is very special and I have no idea what it is. -Peter ------------------------------- Email: Peter.Pregler@risc.uni-linz.ac.at WWW: http://www.risc.uni-linz.ac.at/people/ppregler From sTYLe@WtAl.De Tue, 14 Mar 2000 18:48:26 +0100 Date: Tue, 14 Mar 2000 18:48:26 +0100 From: Bastian sTYLe@WtAl.De Subject: [cpia] still hoping At 08:52 14.3.2000 +0100, Peter Pregler wrote: >On 13-Mar-2000 Bastian wrote: > > anybody made some new experiences concerning the "10-10-..." problem ? > >Not directly. I try to get some updated documentation for the 1.30 >firmware and some hints about the correct camera-initialisation from VLSI. >In the meantime you can try out the following: > >- did you try to run the camera under windows and a soft-boot (i.e. no >power down) to linux? windows and linux are on several computers. >-Peter > > >------------------------------- >Email: Peter.Pregler@risc.uni-linz.ac.at >WWW: http://www.risc.uni-linz.ac.at/people/ppregler Bastian From vincent@linuxbe.org Tue, 14 Mar 2000 19:07:54 +0100 Date: Tue, 14 Mar 2000 19:07:54 +0100 From: vincent vincent@linuxbe.org Subject: [cpia] cpia.o: unresolved symbol(s) was: "usb.h" is missing ? was: usage under the 2.3.51 kernel" ok gor the usb.h (thx you ;) but i have always the "unresolved symbol(s)" message ? why ? [root@jukebox module]# make echo '# Program dependencies' >.depend gcc -M -D_CPIA_DEBUG_ -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -pipe -fno-strength-reduce -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=686 -fomit-frame-pointer -fno-strength-reduce -I. -I/usr/src/linux/include -D__KERNEL__ -DMODULE -DCONFIG_VIDEO_CPIA_MODULE -DCONFIG_VIDEO_CPIA_PP_MODULE -DCONFIG_VIDEO_CPIA_PP_DMA *.c >>.depend gcc -c -D_CPIA_DEBUG_ -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -pipe -fno-strength-reduce -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=686 -fomit-frame-pointer -fno-strength-reduce -I. -I/usr/src/linux/include -D__KERNEL__ -DMODULE -DCONFIG_VIDEO_CPIA_MODULE -DCONFIG_VIDEO_CPIA_PP_MODULE -DCONFIG_VIDEO_CPIA_PP_DMA cpia.c gcc -c -D_CPIA_DEBUG_ -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -pipe -fno-strength-reduce -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=686 -fomit-frame-pointer -fno-strength-reduce -I. -I/usr/src/linux/include -D__KERNEL__ -DMODULE -DCONFIG_VIDEO_CPIA_MODULE -DCONFIG_VIDEO_CPIA_PP_MODULE -DCONFIG_VIDEO_CPIA_PP_DMA cpia_pp.c [root@jukebox module]# make install install -m 644 -o root -g root cpia.o cpia_pp.o /lib/modules/`uname -r`/misc /sbin/depmod -a /lib/modules/2.3.51/misc/cpia_pp.o: unresolved symbol(s) /lib/modules/2.3.51/misc/cpia.o: unresolved symbol(s) Thomas Davis wrote: > > vincent wrote: > > > > apparently, the file "usb.h" is missing ? > > why ? > > > > another file can replace this ? > > > > replace "/usr/src/linux/usb/usb.h" with > > It was finally moved to the proper place in 2.3.51. > > -- > ------------------------+-------------------------------------------------- > Thomas Davis | PDSF Project Leader > tadavis@lbl.gov | > (510) 486-4524 | "Only a petabyte of data this year?" > > _______________________________________________ > cpia mailing list - cpia@risc.uni-linz.ac.at > http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia From tadavis@lbl.gov Tue, 14 Mar 2000 10:10:33 -0800 Date: Tue, 14 Mar 2000 10:10:33 -0800 From: Thomas Davis tadavis@lbl.gov Subject: [cpia] Re: cpia.o: unresolved symbol(s) was: "usb.h" is missing ? was: usage under the 2.3.51 kernel" vincent wrote: > > ok gor the usb.h (thx you ;) > > but i have always the "unresolved symbol(s)" message ? > why ? > do a 'depmod -ae', and it will tell you what the missing symbols are. -- ------------------------+-------------------------------------------------- Thomas Davis | PDSF Project Leader tadavis@lbl.gov | (510) 486-4524 | "Only a petabyte of data this year?" From jerdfelt@sventech.com Tue, 14 Mar 2000 13:20:29 -0500 Date: Tue, 14 Mar 2000 13:20:29 -0500 From: Johannes Erdfelt jerdfelt@sventech.com Subject: [cpia] "usb.h" is missing ? was: usage under the 2.3.51 kernel" I think it was moved to /usr/src/linux/include/linux/usb.h You'll have to modify the path in cpia_usb.c JE On Tue, Mar 14, 2000, vincent wrote: > apparently, the file "usb.h" is missing ? > why ? > > another file can replace this ? > > > [root@jukebox module]# make dep > rm -f .depend > make .depend > make[1]: Entering directory `/tmp/cpia-0.7.4/module' > echo '# Program dependencies' >.depend > gcc -M -D_CPIA_DEBUG_ -Wall -Wstrict-prototypes -O2 > -fomit-frame-pointer -pipe -fno-strength-reduce -m486 -malign-loops=2 > -malign-jumps=2 -malign-functions=2 -DCPU=686 -fomit-frame-pointer > -fno-strength-reduce -I. -I/usr/src/linux/include -D__KERNEL__ -DMODULE > -DCONFIG_VIDEO_CPIA_MODULE -DCONFIG_VIDEO_CPIA_PP_MODULE > -DCONFIG_VIDEO_CPIA_PP_DMA *.c >>.depend > cpia_usb.c:34: /usr/src/linux/drivers/usb/usb.h: No such file or > directory > make[1]: *** [.depend] Error 1 > make[1]: Leaving directory `/tmp/cpia-0.7.4/module' > make: *** [dep] Error 2 > > > ]# ls /usr/src/linux/drivers/usb/usb*h > /usr/src/linux/drivers/usb/usb-ohci.h > /usr/src/linux/drivers/usb/usb-storage-debug.h > /usr/src/linux/drivers/usb/usb-storage.h > /usr/src/linux/drivers/usb/usb-uhci-debug.h > /usr/src/linux/drivers/usb/usb-uhci.h > /usr/src/linux/drivers/usb/usbdevice_fs.h > > > Bastian wrote: > > > > At 22:19 13.3.2000 +0100, vincent wrote: > > > > >I try to use the CPIA driver and I ve got the following error: > > > > > >[root@jukebox module]# /sbin/insmod cpia.o > > >cpia.o: unresolved symbol video_register_device > > >cpia.o: unresolved symbol video_unregister_device > > > > > >I give you my "dmesg" on attach > > > > > >also I don't know how the /dev/video is created > > >/dev/video: No such device > > > > > >in the doc > > >it s talk about "video 4 linux" > > >but I don't see that in the kernel config .. > > > > have a look in Character Devices -> Video For Linux -> > > > > >Hope somene can help me .. > > > > > > > Bastian > > > > _______________________________________________ > > 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 vincent@linuxbe.org Tue, 14 Mar 2000 19:23:54 +0100 Date: Tue, 14 Mar 2000 19:23:54 +0100 From: vincent vincent@linuxbe.org Subject: [cpia] Re: cpia.o: unresolved symbol(s) was: "usb.h" is missing ? was: usageunder the 2.3.51 kernel" I have change the following line in the Makefile because it s USB camera that I want install I don't know why it will installed the cpia_pp ? OBJS = cpia.o cpia_usb.o #cpia_pp.o #cpia_usb.o I have also try to load cpia manually but I have some other error... [root@jukebox module]# make clean rm -f *.o *~ core .depend [root@jukebox module]# make install gcc -c -D_CPIA_DEBUG_ -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -pipe -fno-strength-reduce -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=686 -fomit-frame-pointer -fno-strength-reduce -I. -I/usr/src/linux/include -D__KERNEL__ -DMODULE -DCONFIG_VIDEO_CPIA_MODULE -DCONFIG_VIDEO_CPIA_PP_MODULE -DCONFIG_VIDEO_CPIA_PP_DMA cpia.c gcc -c -D_CPIA_DEBUG_ -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -pipe -fno-strength-reduce -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=686 -fomit-frame-pointer -fno-strength-reduce -I. -I/usr/src/linux/include -D__KERNEL__ -DMODULE -DCONFIG_VIDEO_CPIA_MODULE -DCONFIG_VIDEO_CPIA_PP_MODULE -DCONFIG_VIDEO_CPIA_PP_DMA cpia_usb.c install -m 644 -o root -g root cpia.o cpia_usb.o /lib/modules/`uname -r`/misc /sbin/depmod -a /lib/modules/2.3.51/misc/cpia_pp.o: unresolved symbol(s) [root@jukebox module]# /sbin/depmod -ae /lib/modules/2.3.51/misc/cpia_pp.o: unresolved symbol(s) parport_read parport_unregister_device parport_write parport_unregister_driver parport_register_driver parport_negotiate parport_register_device parport_claim parport_release [root@jukebox module]# [root@jukebox module]# /sbin/insmod cpia_usb ./cpia_usb.o: unresolved symbol cpia_unregister_camera ./cpia_usb.o: unresolved symbol cpia_register_camera [root@jukebox module]# /sbin/insmod cpia ./cpia.o: unresolved symbol video_register_device ./cpia.o: unresolved symbol video_unregister_device [root@jukebox module]# Thomas Davis wrote: > > vincent wrote: > > > > ok gor the usb.h (thx you ;) > > > > but i have always the "unresolved symbol(s)" message ? > > why ? > > > > do a 'depmod -ae', and it will tell you what the missing symbols are. > > -- > ------------------------+-------------------------------------------------- > Thomas Davis | PDSF Project Leader > tadavis@lbl.gov | > (510) 486-4524 | "Only a petabyte of data this year?" > > _______________________________________________ > 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 Tue, 14 Mar 2000 13:29:09 -0500 Date: Tue, 14 Mar 2000 13:29:09 -0500 From: Johannes Erdfelt jerdfelt@sventech.com Subject: [cpia] Re: cpia.o: unresolved symbol(s) was: "usb.h" is missing ? was: usageunder the 2.3.51 kernel" You need video4linux as well. It's called videodev.o. Try doing a modprobe cpia_usb and it should resolve all of the dependancies and load all of the modules needed. If that doesn't work you need to compile video4linux support. It's in the main kernel. JE On Tue, Mar 14, 2000, vincent wrote: > I have change the following line in the Makefile because it s USB camera > that I want install > I don't know why it will installed the cpia_pp ? > > OBJS = cpia.o cpia_usb.o #cpia_pp.o #cpia_usb.o > > I have also try to load cpia manually but I have some other error... > > [root@jukebox module]# make clean > rm -f *.o *~ core .depend > [root@jukebox module]# make install > gcc -c -D_CPIA_DEBUG_ -Wall -Wstrict-prototypes -O2 > -fomit-frame-pointer -pipe -fno-strength-reduce -m486 -malign-loops=2 > -malign-jumps=2 -malign-functions=2 -DCPU=686 -fomit-frame-pointer > -fno-strength-reduce -I. -I/usr/src/linux/include -D__KERNEL__ -DMODULE > -DCONFIG_VIDEO_CPIA_MODULE -DCONFIG_VIDEO_CPIA_PP_MODULE > -DCONFIG_VIDEO_CPIA_PP_DMA cpia.c > gcc -c -D_CPIA_DEBUG_ -Wall -Wstrict-prototypes -O2 > -fomit-frame-pointer -pipe -fno-strength-reduce -m486 -malign-loops=2 > -malign-jumps=2 -malign-functions=2 -DCPU=686 -fomit-frame-pointer > -fno-strength-reduce -I. -I/usr/src/linux/include -D__KERNEL__ -DMODULE > -DCONFIG_VIDEO_CPIA_MODULE -DCONFIG_VIDEO_CPIA_PP_MODULE > -DCONFIG_VIDEO_CPIA_PP_DMA cpia_usb.c > install -m 644 -o root -g root cpia.o cpia_usb.o /lib/modules/`uname > -r`/misc > /sbin/depmod -a > /lib/modules/2.3.51/misc/cpia_pp.o: unresolved symbol(s) > > [root@jukebox module]# /sbin/depmod -ae > /lib/modules/2.3.51/misc/cpia_pp.o: unresolved symbol(s) > parport_read > parport_unregister_device > parport_write > parport_unregister_driver > parport_register_driver > parport_negotiate > parport_register_device > parport_claim > parport_release > [root@jukebox module]# > > [root@jukebox module]# /sbin/insmod cpia_usb > ./cpia_usb.o: unresolved symbol cpia_unregister_camera > ./cpia_usb.o: unresolved symbol cpia_register_camera > [root@jukebox module]# /sbin/insmod cpia > ./cpia.o: unresolved symbol video_register_device > ./cpia.o: unresolved symbol video_unregister_device > [root@jukebox module]# > > Thomas Davis wrote: > > > > vincent wrote: > > > > > > ok gor the usb.h (thx you ;) > > > > > > but i have always the "unresolved symbol(s)" message ? > > > why ? > > > > > > > do a 'depmod -ae', and it will tell you what the missing symbols are. > > > > -- > > ------------------------+-------------------------------------------------- > > Thomas Davis | PDSF Project Leader > > tadavis@lbl.gov | > > (510) 486-4524 | "Only a petabyte of data this year?" > > > > _______________________________________________ > > 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 tadavis@lbl.gov Tue, 14 Mar 2000 10:32:18 -0800 Date: Tue, 14 Mar 2000 10:32:18 -0800 From: Thomas Davis tadavis@lbl.gov Subject: [cpia] Re: cpia.o: unresolved symbol(s) was: "usb.h" is missing ? was: usageunder the 2.3.51 kernel" vincent wrote: > [root@jukebox module]# /sbin/depmod -ae > /lib/modules/2.3.51/misc/cpia_pp.o: unresolved symbol(s) > parport_read > parport_unregister_device > parport_write > parport_unregister_driver > parport_register_driver > parport_negotiate > parport_register_device > parport_claim > parport_release > [root@jukebox module]# > do a 'rm /lib/modules/2.3.51/misc/cpia_pp.o'. Problem fixed. (or, enable Parport support in the kernel) > [root@jukebox module]# /sbin/insmod cpia_usb > ./cpia_usb.o: unresolved symbol cpia_unregister_camera > ./cpia_usb.o: unresolved symbol cpia_register_camera > [root@jukebox module]# /sbin/insmod cpia > ./cpia.o: unresolved symbol video_register_device > ./cpia.o: unresolved symbol video_unregister_device > [root@jukebox module]# > Try '/sbin/modprobe cpia_usb'. That will load all the needed modules (if they have been compiled). If it still bombs, make sure video4linux has been configured. Go into menuconfig, select character devices, select video4linux, type 'm'. Nothing else in video4linux needs to be to selected. -- ------------------------+-------------------------------------------------- Thomas Davis | PDSF Project Leader tadavis@lbl.gov | (510) 486-4524 | "Only a petabyte of data this year?" From vincent@linuxbe.org Tue, 14 Mar 2000 19:48:23 +0100 Date: Tue, 14 Mar 2000 19:48:23 +0100 From: vincent vincent@linuxbe.org Subject: [cpia] Re: cpia.o: unresolved symbol(s) was: "usb.h" is missing ? was: usageunder the 2.3.51 kernel" This is a multi-part message in MIME format. --------------497CB90193B395711364A9B4 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit ok its running right now thanks to all I give you a picture of me for your help thanks Thomas Davis wrote: > > vincent wrote: > > [root@jukebox module]# /sbin/depmod -ae > > /lib/modules/2.3.51/misc/cpia_pp.o: unresolved symbol(s) > > parport_read > > parport_unregister_device > > parport_write > > parport_unregister_driver > > parport_register_driver > > parport_negotiate > > parport_register_device > > parport_claim > > parport_release > > [root@jukebox module]# > > > > do a 'rm /lib/modules/2.3.51/misc/cpia_pp.o'. Problem fixed. (or, > enable Parport support in the kernel) > > > [root@jukebox module]# /sbin/insmod cpia_usb > > ./cpia_usb.o: unresolved symbol cpia_unregister_camera > > ./cpia_usb.o: unresolved symbol cpia_register_camera > > [root@jukebox module]# /sbin/insmod cpia > > ./cpia.o: unresolved symbol video_register_device > > ./cpia.o: unresolved symbol video_unregister_device > > [root@jukebox module]# > > > > Try '/sbin/modprobe cpia_usb'. That will load all the needed modules > (if they have been compiled). If it still bombs, make sure video4linux > has been configured. Go into menuconfig, select character devices, > select video4linux, type 'm'. Nothing else in video4linux needs to be > to selected. > > -- > ------------------------+-------------------------------------------------- > Thomas Davis | PDSF Project Leader > tadavis@lbl.gov | > (510) 486-4524 | "Only a petabyte of data this year?" > > _______________________________________________ > cpia mailing list - cpia@risc.uni-linz.ac.at > http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia --------------497CB90193B395711364A9B4 Content-Type: image/jpeg; name="moa.jpg" Content-Disposition: inline; filename="moa.jpg" Content-Transfer-Encoding: base64 /9j/4AAQSkZJRgABAQAAAQABAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHRof Hh0aHBwgJC4nICIsIxwcKDcpLDAxNDQ0Hyc5PTgyPC4zNDL/2wBDAQkJCQwLDBgNDRgyIRwh MjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjL/wAAR CACQALADASIAAhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAA AgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkK FhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWG h4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl 5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREA AgECBAQDBAcFBAQAAQJ3AAECAxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYk NOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOE hYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk 5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwDlfDs0sumxySEs/Qkn9DW9fi4Jjjuikivu YKPbn+RrktC1K2+yERRmOJFLk56Yro4b9NVlULKjBY2AAGDnH/1q8GunzPSxslqilKsXkSBU AX5gVH171WjEAihO08McjpngVPKTBC4cZGS2OelQm7H2a2X7OSwlOSvbj/EVlq2dVFpRdyc+ SNW0srHj5G4x1+b/APV+Va1mtvLq2o7ocD7aD0rLe7Q6lprCIqyq/GOvJ7fSup8PyC78SXit bE771SVx2PWrim7L1KqSSd7dS14ato/PjVYC228fIx23GrFvarLruryCA5a5XqvA4H/6q9Xt NOsrBNtvbRp8xbIXnJqZbeBGZ1gjDMcsQoyT6mutZfKVpXOd4qC0seU3qK3jTUGW3wRFGqjF YWf+Ki1QG3+b7RnAX2Ne4mztXnac2kBlYANIUG4gdATjNeeeN9I/sTULLUtNjbyry5KXaM25 Q20lWXPI5B6ce1c9bAzpQ5r3SuaUcTCUkrbs4C9lf/hL79vs5AEq8f8AARS+I5ZP+EvsmW2K Ztxg4xwP/wBdO1S5uh4u1CQxYPnLgdhlRR4kutQn8UacZYAAbfHHGen/ANeuWG8f66G8n7r0 6noF/l/BKmM7pPIOM9+1eS6tPfJ4YuYpIUKb1Zs8jI6frXq9w3meBiUPIhIOfXFeX+IILhPC 8h3ZVpkUgD3H+fwrNP8Af/NGGHgnGdzLluHbQb9Bbq/yfMeeBmsm0uFOi3Ktb5wVzgdK3ZEu P+Ecv8J/yy5X+n/1qyrPzRodyViLAlSfb/6/Wu6LtF37m8ofkV4JkMbl4m5hVQCenHWs/wAy 3eC1UxkLtznHU/5IrTs5Du5iPNuCFI6DHWqKhjBZoI9oIwM9Bzjr+Vbx3f8AXciEXcz7cx4w +eByRk8/T8qsTmBdV3YJQFCQR1GB6fT9ahhUM0m9Dk4Bz269KnnEcmpBhEx+VcrjGTitn8Xy LSdijGI8zl2Iba359P60/T14cj+6c9aSFIf32eoUkfr/AEqbSyE5AOG4OM1c37rMal+U1dFb ZatGw3ObZl47/eA/pW34MAa8cn+KN8EdPu9sVH4dtFeGNQoGS0ecY4JHH61Z8IR/Y9VitXU7 lUr/AL3A6evUVzVJptmS2L10CF6Hdt9ff/69VJS4jsj5Ix5p/i9jmrdwJJU8yFC4eMPwOeet U7iS4WCxzHjMpwwHPfrXDBapG9J2i9C/KZRqelN5D5w4GR7123gyKV/F1+XjHy3gySOc9f8A P0rjJbi6a600lNjAsBng5JNd54IluX8VagHAJ+1Hdx0OK0pfGvmVXk7PQ9WPLc9KTryaD3x3 pGPOB0r6FHjS7gSTXM+OYpZNAiaIAmK7iY56AFtp/wDQq6XGa4H4qeK7bRdB/suBxJqt26GO JTzGiuCZG9AMcep/GsMUlKjKPdFUpOM1I8812R7bxHqUk0gUidSQxGcBR/SsbX/FllPrVncx zl0t4PLbC98AVgXsd9rN1LPcySSSSsWd29cfpUJ0F1Q+blOMc85rw6VGEUueWx7blJ36HpSf EHQJ/C76Y9zLFdGIhSUyoJ9/rXLaxFLJ4YWSC8WWBpUIw2TjdyfyzXD3mlvATgk8fmRiqqPc wBcPIFXqu446+ldMcJBtTgzCNOUb9bnfXEd2ugajhxsWHJ56/wCTWTYyXa6DdMPukLuHXn3q 1ZahHqnhzUIpJ9lz5R2xk43nP+HNNs7eYeHLyRCuFC9s5/z71nyuCafc1tFrfoVLF7kyglFL fZsdAMcHsPwqiJJ3tIPlCvnHC98//r5rZsUuGnAjRTmBs/Tn/P4VnrDcNBbcL8zkj0OTx196 tS1bIjHbUyYJiLm4Hlbvl646Yzj8KtPKWv4yYcAqOF+gqvEkiXtx+7GQOvTj1/z61dIn/tS3 HlrkJuwPYVvK1/kWo6bmZBcBGnDwqdysACAO5qbTXDKcLg7c89/xpsJcyzFYuqtnjOOv+fwq XTsjywSpUpkY6mrnblZnUWh0+gTQWbwxtKXfeCfkx3FaOnXdhLq9tcRoxlQ+UzZ4Hzfy6VlN a+Te2wQgZX05yOaZp7/ZdclgUNgTlWzg8cHH61x25/fTMlF9DotM15rW3nt7RI2VlAJYZ46c VU1COdf7OAOVdz0HQ881i6SGV54lyAHZAB2GSB/KtjUll8zSzHJjdgAZ6nn/AArJwUZo3inG 5climafTC/BDtt9+tdX4evJ9M8VahJK2R9qBbnP8IrkZobkPpp8znzCMc+hrVWG5XXL9DNz5 0bZHfKD+lQnbVeZrNSlpY9xi1vTJpJVS9i3w8SKTgrxn+tFlrGm6kqNZ30MyvnaVP3seleZW 9tcQHWpDdFSAzZz14H+FdT8Oba1Tw7aMzq90qdzyOOeK68Pjq9SfK3H7n/mebWwvJqyPxp8R NO0HS5otMuYrnVnYwxRL8wjbIBZ/QDPTucD1x5LpGiX3iO+muLqV7m8nJaaZ+S/XHXoAMADo Kb4qtjH8Qdas4phcW8M4Mbqfus4EjKevQvjj+letfDuxjgsXl2Deccnr3onUnUfLUav5bF0Y Rpx9o9WcrZeAb13ZfKCqevpn/P8AOnX/AMPtVMJOxJcLggEjv2r2HI9Kjc1hVoKMbuRp9abf wnzn/wAIneTSOjW0gKnncMVNL4AeWJhLHgnj5TXtd8IxIcIuT2A61i3jYjPTAGCfxriWIlFW R3U2pLmsfPWueGZ9MhaSPeI42PzdKsafEZ/Cd5Ks6nBCsM+36V6DrkUM8bowVlcEEE9q87gg Fimo2THbG670GehHb8q7KNd1YOM90Z1Et0S6fDN5wVZju8g4BbrwaoRRXBhtFJ24bH4g81sa dbIXXE2P9Fyee4B4qhaWoMenK0wbecMCe2f8QfzrVS1f9dzKKjoYUP2hL+4VCCATy31/+vWh /pJ1i0AILCIlR+VU4omGrXIUjaCRnPXmtFrd/wC1bT9/ncvXuK6JtXXp+hVlbcyrZ5hNcqGY cNjJ9zn8+al0tGKx7mbJTCjGMVHDE7S3Kq6g4YEE9etWLFdpjO7JKZ4Oc5zVTfuszqJJfI6i 5j/0m1ZeSFPB+tVbaEPr9xKOd827p7D+ua07owkwMrKCnzHJ6/hUdtq1sNU+zQQqZWJ3N2Bw P8a4aUnayJUkkX7LwvdNfXU2AsRlcg+g3H8+tRatFGz6W8b+YmXAb19/1r0PR7FjqSNJIX+1 JIQD0A2k/wBK5aXwrdXOnafsXD2jPlR6Mc1HP765ilV3Kj2iH+zX83J84gj04Nb501V1q8Yz ZDGEhs4I/dis6Tw/cxC2WRSpictnJORyK9AsfC1jcQrc3EkiyuiE4PogAP6iobNHiUndsyLu ytY9I195LggqGUHfySQQKs6PZR6dDZTo4byYC5Df7pP+Fbt94a0qbT57dpJI1lk8xmXGcrls foaxPEFvaaXpWovE8nyWk207T8u2KY/+0j+YrBRlytdyPrMZS1ehxS2Sy69dXG0OrzswYDhv m4Net+G41gtDGBggDI/CvB9BvriG2t/OuFmcuW3r068f1r3LQC5tYp3OWnXcB+FbcsqcbXvY l3cbM6HPPrTHOFPPaq15qdlpyZurmOMnnDHBrGn8W6bIGSK5ib1+aoqVotWT1MIwbZNekFmz kNwCKxdTJ8ot7ZPNQ3usJIWdHVmHXB4xXNav4lhtIgHkGQOAPr6VhGmz0IyUVYp3y4kZuDjP IPeuB1NRcXkqurbWjYjaOeQa3bzxRLKSsUCurc1DoeohruWcxormEqNy57jp+VdVKMovmsZS mmUdO04tNgBwgtwAcEgnBwKpWekyB7CN45AF+8u0ggZrslv5DGQWwDgbccY5psV8kUqO8mDn jNV9Yd35mfOlrY83i0W/Go3LC3mChm24H3hk1fk02b+0rUBJMBWBOwkCvQpJGjk88EZQZOO9 ZdxIxm3gjryfWrljJyewcytsefR6ZcgXJMcoPzYypHc/4U+ytnicM4YYT+JSBXZSlSeeGHVi egqlPcRyMIQQTg9K1WKlNWsTKV1sVbzSbqzMsjzNIsbBVyeSOaLJIoddY7R5p2nPsVA4/LpW 1q9xBLZj98GMiKRj1Kp/iaqRaVcSahBdRJuVlHzDsQT/AI1d9WjOnK8T2Tw1GJtQ09x/yyU7 ifeP/wCvV+1twk0yf9NCMD03EA/pXMxeIbfRUsbaNSbu5UA+igcZ/Suns1cajJk/eT88Hj+Z rz6ibldbGc2ldFq9so/srFUGQD1HSrdpHixj5ZV8hfmx0+Uj+gp0sZ+ws56qucmqrzFdOixw BaggY/6Zyf4UU0pSakYOWhdu9hVl4bG7HscPWZrunDVdJvrTODLDNHkDn5kmT/2arR3SPIM9 35P1lFJrIlj0O9ltz5cqo5BPoN+f0zW9SpywbjoZK8pXZ5jf+HdHfQPM0WJ47rTYwTLklZ48 bs+5xXbmaaPwpZzWzMJDbLhseo5/nT/E2mfZLa9lsEIe5jAZEH3QOOB9DTPDOLjRkspvvW7G BgenBNcs5SmpU5PU96PK4Rmtjze+nW9ke4v9RkZ1H3ZGIPH8q5j7RazXpFtIz4bbuBwM+/5V 7Lr3g+0dDJHbBZADtbrXKWngdIrvEcagufmwP8+prSgopWeg+RSV4vQn8JaVNqXmRAtnZuyT xXnmui4XXr20dMNA20Y7g55x2/8ArV9C+HNKj08nbgnZjI715R4ytYm8Y3RKhWbC7scnBP8A 9b860c4qUWvP9CYWbcOx5y9zfJOY/IO0AjjvgcZ/UV6H8NtKjvtbC3cSuogcshGR93H9azhp aNsYrwBgcV1/w4SKDWr2YAlI7YjdjuWHH861nUXToZVFaOhR8U+C73Tg91pI3xKOYScn3Irz 6Vpppo2f9yhJ3h8gg/T8q+hLrV4/LJHK+4rzvxrollrVg7LEI50+dHTg5FcFCur2kvmTCpbo YNrcmayjIIIkjHIrGutUaOTYYsKp6tVnS5RFapC4CeWoXnnHFZuq6XFc3Bka6aNWBOxRxn+n rXSoQ9prsTF9Cje6uqN5ROS2D8nJ5zVCKe5W8UPGVjB4Lfwj/Oa0pZ9Ot7eM28QMij5mPUms m6v3lu0xtAcEDiu2lFbRj95c4vluy1piTXMcY3MQFGSQe3f9K6qXV2trZrKGRRJskdZOeCO1 Ug7XNs00RCDcqnA6+v8AKs6+t2inWMPws0in6EZ7/hUtuo/e0MNFpE7C4lP2XSLot8yvt3dz 8xP9a9W0e4huL6Fz8u6MnJPrzXltvbw3Oh25lJBilL5HAHA4rpNH1ZYdQhuYmYYXaAeVPFc0 2r8qInCy5mel6pf21npM0krAJsI/SuPXxxaRQeTJaI+0EZDDGPnx19sfmapXFy167vK4+Y5C joOelVxaW2dxRe2DgdOf8/jWHLNy5m7GNrrU6GHx3BLxBp6MSTgeZjOS3t/nJov/ABLLqNhc 239nCPzInRWMo/iUjn/voViw21suNsa4GT6EU97qLT83IgWYLk7Dxnjv+lEr2s5Maj5m7L4x hEsJmtI1j3KGcSBiAxI6fgKg0+RF1nUPs7oYpWWdCp45GD19wfzrkriyV7B3MO2Xyi3ynABA zW5pSm0FrL5ZXcFDgnsR1/lS5W3eT1OqjPk06HWtdu8IjYDjv1NV2VYleVhgkflVgIuflYCo 5YvNwqtgdCoxUO6O2PKtEXtKkiWHDuvmuNxBPOK808eJaHUWuVYLPuGaseJdNvbPUVv4b2RF RCFiVsAD6elef3t1dXl1FNcSsylsHn+lVFSq2j2Jt7ObkuprzyMLbcuASDzW34Llkh0/VpVP JVcnPTrXO3cqeSm1sjtzXQ+HY/K8NX0h/wCWkioCR1AFa1NFLyRlN3si1FetPFEncgE49aSa RXmukU52IAOe/eoNGIMW7B4OMntVeGUSXV2ckBWz+NcnLZIyOXm0WWXUGm8xUifBG3k9O9Jc 6ZBHCMyNnPQ+lanmH7Q8K/fUZwOM/wCeaklszcxYdCAeCP8APStlOXKge5zN3oOnPCAW6kH5 eBVB9A0wvlpCf6dK6CTRsQ7GmYjGOOoqtc6WoBJkbG3nit41pL7QnexDZp/xJ5SQeORx0PWt RPD7X2ruHfCjZMfXaVGfxrDsLl5LW5t9uf3RIIPeuhhvZvkeOQC4khVG56KDj+pNdE276Ex0 uLci3uHeCyctbxyKH5+8f8P8a07UFQPw6Vd1bSodPns444ljbyMyBOAWyDmo1Tam4etYx0uj OcuZliJyqnn61YRiTgdzisXRL1Lq+vIZpHB2MIlz/EGH9K2xFtfgcrz/ADqd9SLWJFby1wee DjFZt9fncscltM8J4Yr1YGtBQcgDqOvPWiULtzJkFCCCRxis5IpOw6G8trnT40CXAmKFCJF6 /wCRUl7exQaFp80bvumktoCDjADuqE5/HNZd3r8UDBINrSbsKQMc9ap2zvfWF7GWDrbJE8Qz 0ZJAw/UCqj7z12Hqdzb6k0Rkglb95E2xh9Bx+lU9a8QnTwTyCT0HNUddJkK6rZZcsoZ1HAcd fzFYkOow38qMpBKgBVPbms3TUtDu57IdeeIzcjc1vcNwSQUPArlb/UUMJW0siqrnJIyc8/0r r7uW7jRmSA4xj5RjjrXKXNzNOTHJD5YJ6dSea2hFLRI0Tgo63M9J5GgWSdNh54B/IV0EGuxD w5b2dlcpv3MZEPXOe34CuRu5nacRREBFBJyen+cVgC4kjmlVWwQxwuevX9f8a39h7RNbHHKW uh6bpGsyWMBWRRMHIB4yefSpdLmSeKdw2JC250xyMnArhLLUp4kGyTAUg7SfbitGy1Qxybgu xj3HryaxnQaJ5jrYlRdQ88nACkYI/Wr03K5Vup7Vg/boZoAY3G8jnJ5GB/n8qsx3oVlTH+e9 cslZcrKv1JZlYSA5BA7Cqr7ejZA55UVc85ZR8pAAPp9aqTfLnIz6e9JIlswPD2mPcqFCnfIN o4/w/wA81tXugf2LdRp9taSWbdlQPuAdDVHwvrENo4jYrnbuU9h/nArsoZdLvblpZpY2lJ5J PQcV6dWRlKo1LyKYupJyjzSl3WMKCfanTXccVo25toHJBP5f1rcj0/SZYmdG3bOW2nFeQeMN fZdUutPt96xxkIexz71kqbqS5Ykx956F3T9b+y6o1ygVgspPX/aP616X9slEXlsyqpAyCOnX vXiOksJ2hRVbcZFLDHbdzXpV7q5LsqkYHHNXXgoKxpOOptSapBCSRlpBk47Hise81Z5S7Svh VGdvoayPtbSPkdPm6fSqd5cFm2rlsknk+1cyg+okrE32k+cXySeSP8/nW94XuALi5jZhuaM9 O+CK5NZV8tTghxznuOv/ANapobxrW8EqnBHX9a3irDlseiabdiK6l025IKMC8J7c9RWRrOli O+e6sXEM/Rv7rYPf3680n2ganp4mtmP2mFcg/wB04pYtUF3CyyZWVeHXrz/WpcLaIunU0szP fxDdQMRcwMvAyF5BPWue1HXIxFJx874xkHPWtPVZ/lZflx6Y5rk542mkM8qgR5yAw6/4VdOm m9R3sRhmt7ffK4d5CWOeO/ArHgZnbMjc8YPTJzg/1pb2/NzNhQBGOgHGaIOFJZuRghhj1P8A 9avRjDlV31JXdlpG8uEN14AI5z0q7HcEMOSvcZ68f/r/AErOQKqBcYBOAD34qxu+fDAHJOSf XNZTimDRfSfywNp2qPU9a07bVmKKspLEDAJ7Vg+YyhSx4APHTFNEjbQQ3c4/KsXSTWpJ2Ed6 AocNuXPABq2t6kkeGb5h3J71xMN+8T/KTjJ6/iK04bwSpg43YOR3PvXNPDtA2cimqT26gKRy O4z3+tWovElzG3y+vr2rFfJwMU3oe1e26FOW6Cb97Y7q01u5/wCEdv7pZ2WSERkKr9QWC/1r mJp7jVNQmuJSzS3MrSN6Ek1FaTN9iurdTjzI8n32sp/oa3vD9ji3Nw3PYAjH+f8A69YuEKCc kioWi3I1dGsUsbdTwZX5JB/T+daDTeZzznPr61T88llzjAGPbrSlyWII4B5/nXnTfNLmYm7l tHHRuCBkcde9UrqaNf4s/SkE287VfA6nB59Kp3LKB90ZzjPXkUoxdwLqSrIuAhPA56d6WTcI 23fwHoO3WoIH/c8c4OSemKlZskjfwTzn8arlSET2Opy2ExkTHqc9CMd6rPrcv9qXJlbYjvvi ZR90ccH2BqOZG2kgAMTgnHT6/nVGdAWckEbl5Geg6VcEupPW5rXd7E9q91PhYAMZXPzH0A/G uZ1DUpbi1ETFgrENg/wjsKfeTGTKufl44Hqfb1qgMNgxkhSOjDpXTRpqPvMta7jI9xCLu3EZ x3A9ePpViNsbPlyvUnFRqDtAIIzwe3Hp+lW4o41jAU5HGOP1rWb0KbFBAUBo/vEcjn61KsiE ZYEc54Hv0qLeyDfwOPmOM5oLAkMVyVJJGORg+9ZNXIGJMGYBGXJGf8/59aeXwVBUqR1ANUtp Rd49Bk5xnk8/mKmFx+7G5gSOcrVuHYZFI5ikygGV4GRnj+tL/aEttjByf5VSdiWcnrupjsfl yPz5zWypp7jdrH//2Q== --------------497CB90193B395711364A9B4-- From tadavis@lbl.gov Tue, 14 Mar 2000 11:09:22 -0800 Date: Tue, 14 Mar 2000 11:09:22 -0800 From: Thomas Davis tadavis@lbl.gov Subject: [cpia] patch to fix debug/usb.h problems.. This is a multi-part message in MIME format. --------------9F04D76AF2AE76E9CAB72B23 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I've attached a patch to fix two problems; 1) removing -DDEBUG from the makefile, causes the compile to die. (two lines are goofy) 2) Fixes the usb.h based on kernel version. -- ------------------------+-------------------------------------------------- Thomas Davis | PDSF Project Leader tadavis@lbl.gov | (510) 486-4524 | "Only a petabyte of data this year?" --------------9F04D76AF2AE76E9CAB72B23 Content-Type: text/plain; charset=us-ascii; name="cpia-0.7.4.diff" Content-Disposition: inline; filename="cpia-0.7.4.diff" Content-Transfer-Encoding: 7bit diff -ruN cpia-0.7.4/module/cpia.c cpia-0.7.4-fixed/module/cpia.c --- cpia-0.7.4/module/cpia.c Sat Mar 11 13:44:01 2000 +++ cpia-0.7.4-fixed/module/cpia.c Mon Mar 13 19:27:46 2000 @@ -1647,9 +1647,9 @@ cmd[7] = 0; retval = cam->ops->transferCmd(cam->lowlevel_data, cmd, data); - if (retval) + if (retval) { DBG("%x - failed, retval=%d\n", command, retval); - else { + } else { switch(command) { case CPIA_COMMAND_GetCPIAVersion: cam->params.version.firmwareVersion = data[0]; @@ -2251,9 +2251,9 @@ schedule(); cam->image_size = parse_picture(cam, image_size); - if (cam->image_size <= 0) + if (cam->image_size <= 0) { DBG("parse_picture failed %d\n", cam->image_size); - else + } else break; } diff -ruN cpia-0.7.4/module/cpia_usb.c cpia-0.7.4-fixed/module/cpia_usb.c --- cpia-0.7.4/module/cpia_usb.c Sat Mar 11 13:44:01 2000 +++ cpia-0.7.4-fixed/module/cpia_usb.c Tue Mar 14 11:11:40 2000 @@ -31,7 +31,11 @@ #include #include "cpia.h" +#if (LINUX_VERSION_CODE >= KERNEL_VERSION(2,3,51)) +#include +#else #include "/usr/src/linux/drivers/usb/usb.h" +#endif #define USB_REQ_CPIA_GRAB_FRAME 0xC1 #define USB_REQ_CPIA_UPLOAD_FRAME 0xC2 --------------9F04D76AF2AE76E9CAB72B23-- From sTYLe@WtAl.De Tue, 14 Mar 2000 21:50:58 +0100 Date: Tue, 14 Mar 2000 21:50:58 +0100 From: Bastian sTYLe@WtAl.De Subject: [cpia] still hoping At 18:37 14.3.2000 +0100, Peter Pregler wrote: >On 14-Mar-2000 Bastian wrote: > > At 08:52 14.3.2000 +0100, Peter Pregler wrote: > > > >>On 13-Mar-2000 Bastian wrote: > >> > anybody made some new experiences concerning the "10-10-..." problem > >> > ? > >> > >>Not directly. I try to get some updated documentation for the 1.30 > > > > my camera seems to have firmware version 1.00 > >Actually it has version 1.02 (1.0) according to your postings. > > >>firmware and some hints about the correct camera-initialisation from > >>VLSI. > >>In the meantime you can try out the following: > >> > >>- did you try to run the camera under windows and a soft-boot (i.e. no > >>power down) to linux? > > > > under windows it works. > >I guessed that. What I wanted to know is if windows does any >initialisation that our driver does not. > >I checked out the mailing list archive and I cannot think of any good point >to start debugging on my side anymore. Can you try out the following: > >- try out the driver version 0.4.4, that is the first one which >should work reliable with 1.02 firmware, so we can see if any bug was >introduced after that >(http://download.sourceforge.net/webcam/cpia-0.4.4.tgz), do not activate >dma please > >- can you boot your box fresh in emergency mode, load the parport-modules, >v4l and the driver and _no_ other fency stuff, especially not the ppp/isdn >stuff you got in the ooops, use vidcat or the like to grab a single frame >to disk (or /dev/null ;), if it fails send me the syslog from boot to end, >and also the output of the relevant proc-file (interrupt, parport, cpia). compiling cpia_pp without dma brings up the following warning : gcc -c -Wall -Wstrict-prototypes -O2 -pipe -fomit-frame-pointer -fno-strength-reduce -I. -I/usr/src/linux/include -D__KERNEL__ -DMODULE -D_DEBUG_ -DCONFIG_VIDEO_CPIA_MODULE -DCONFIG_VIDEO_CPIA_PP_MODULE -DCONFIG_VIDEO_CPIA_USB_MODULE cpia_pp.c cpia_pp.c: In function `cpia_parport_enable_irq': cpia_pp.c:259: warning: implicit declaration of function `mdelay' and both insmod'ing cpia_pp and depmod -a bring up : /lib/modules/2.2.14/misc/cpia_pp.o: unresolved symbol mdelay >Sorry for not being of more help. But something in your setup is very >special and I have no idea what it is. > >-Peter > > >------------------------------- >Email: Peter.Pregler@risc.uni-linz.ac.at >WWW: http://www.risc.uni-linz.ac.at/people/ppregler > >_______________________________________________ >cpia mailing list - cpia@risc.uni-linz.ac.at >http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia -Bastian From sbertin@mindspring.com Tue, 14 Mar 2000 17:14:01 -0500 (EST) Date: Tue, 14 Mar 2000 17:14:01 -0500 (EST) From: sbertin@mindspring.com sbertin@mindspring.com Subject: [cpia] "usb.h" is missing ? was: usage under the 2.3.51 kernel " On 14 Mar, vincent wrote: > apparently, the file "usb.h" is missing ? > why ? This file was moved in kernel 2.3.51. The CVS archive has a fix to this already committed, there just hasn't been a new release yet. Scott J. Bertin sbertin@mindspring.com From sbertin@mindspring.com Tue, 14 Mar 2000 17:19:54 -0500 (EST) Date: Tue, 14 Mar 2000 17:19:54 -0500 (EST) From: sbertin@mindspring.com sbertin@mindspring.com Subject: [cpia] still hoping On 14 Mar, Bastian wrote: > compiling cpia_pp without dma brings up the following warning : > > gcc -c -Wall -Wstrict-prototypes -O2 -pipe -fomit-frame-pointer > -fno-strength-reduce -I. -I/usr/src/linux/include -D__KERNEL__ -DMODULE > -D_DEBUG_ -DCONFIG_VIDEO_CPIA_MODULE -DCONFIG_VIDEO_CPIA_PP_MODULE > -DCONFIG_VIDEO_CPIA_USB_MODULE cpia_pp.c > cpia_pp.c: In function `cpia_parport_enable_irq': > cpia_pp.c:259: warning: implicit declaration of function `mdelay' > > and both insmod'ing cpia_pp and depmod -a bring up : > > /lib/modules/2.2.14/misc/cpia_pp.o: unresolved symbol mdelay Try adding #include just after the #include Scott J. Bertin sbertin@mindspring.com From sbertin@mindspring.com Tue, 14 Mar 2000 17:24:19 -0500 (EST) Date: Tue, 14 Mar 2000 17:24:19 -0500 (EST) From: sbertin@mindspring.com sbertin@mindspring.com Subject: [cpia] patch to fix debug/usb.h problems.. On 14 Mar, Thomas Davis wrote: > I've attached a patch to fix two problems; > > 1) removing -DDEBUG from the makefile, causes the compile to die. (two > lines are goofy) > > 2) Fixes the usb.h based on kernel version. > Both of these have already been fixed in CVS. Scott J. Bertin sbertin@mindspring.com From tdat@yahoo.com Tue, 14 Mar 2000 18:21:43 -0800 (PST) Date: Tue, 14 Mar 2000 18:21:43 -0800 (PST) From: Sang Y. Yum tdat@yahoo.com Subject: [cpia] gqcam with Creative WebCam II --- Peter Pregler wrote: > > > > What's that "fatal_error" doing there? > > That should be the source of your problem. > Apparently the read of the > firmware version et al. fails. I check that out. > Peter, My bad. I bought a OEM version of this camera, which came with no documentation. I did not realize that the extra dangling connection were to be plugged into the keyboard connector, which, I guess, is a power source. Anyway, I am getting close but no dough. gqcam displays a couple of frames, the picture freezes and gqcam spits out "Error reading image..." repeatedly and I see these messages repeated in dmesg: cpia.c:parse_picture(1901):header not found cpia.c(3629046):fetch_frame(2231):parse_picture failed -1 cpia.c(3629046):fetch_frame(2159):retry=1 What do THESE mean? Please tell me there is a very easy solution for this. Thanks a million. Sang ===== Sang Y. Yum http://www.yumnet.dyndns.org/~sang San Diego, CA mailto:tdat@yahoo.com __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com From sTYLe@WtAl.De Wed, 15 Mar 2000 14:20:06 +0100 Date: Wed, 15 Mar 2000 14:20:06 +0100 From: Bastian sTYLe@WtAl.De Subject: [cpia] still hoping At 18:37 14.3.2000 +0100, Peter Pregler wrote: >- try out the driver version 0.4.4, that is the first one which >should work reliable with 1.02 firmware, so we can see if any bug was >introduced after that >(http://download.sourceforge.net/webcam/cpia-0.4.4.tgz), do not activate >dma please > >- can you boot your box fresh in emergency mode, load the parport-modules, >v4l and the driver and _no_ other fency stuff, especially not the ppp/isdn >stuff you got in the ooops, use vidcat or the like to grab a single frame >to disk (or /dev/null ;), if it fails send me the syslog from boot to end, >and also the output of the relevant proc-file (interrupt, parport, cpia). ok, i've done the following : - disabled the isdn/hisax drivers - compiled the 0.4.4 cpia module (disabled DMA in makefile and added the include line) - loaded the parport, videodev and cpia modules using the script loadpp here are the results AFTER starting gqcam : --- dmesg --- Linux version 2.2.14 (root@Little) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 SMP Wed Mar 1 17:53:36 CET 2000 mapped APIC to ffffe000 (00233000) Detected 132874322 Hz processor. Console: colour VGA+ 80x60 Calibrating delay loop... 52.84 BogoMIPS Memory: 79472k/81920k available (880k kernel code, 416k reserved, 1092k data, 60k init) Dentry hash table entries: 16384 (order 5, 128k) Buffer cache hash table entries: 131072 (order 7, 512k) Page cache hash table entries: 32768 (order 5, 128k) Checking 386/387 coupling... OK, FPU using exception 16 error reporting. Checking 'hlt' instruction... OK. Intel Pentium with F0 0F bug - workaround enabled. POSIX conformance testing by UNIFIX per-CPU timeslice cutoff: 1.56 usecs. CPU0: Intel Pentium 75 - 200 stepping 0c SMP motherboard not detected. Using dummy APIC emulation. PCI: PCI BIOS revision 2.10 entry at 0xfb740 PCI: Using configuration type 1 PCI: Probing PCI hardware PCI: 00:38 [1106/0586]: Work around ISA DMA hangs (00) Activating ISA DMA hang workarounds. Linux NET4.0 for Linux 2.2 Based upon Swansea University Computer Society NET3.039 NET4: Unix domain sockets 1.0 for Linux NET4.0. NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP TCP: Hash tables configured (ehash 131072 bhash 65536) Initializing RT netlink socket Starting kswapd v 1.5 Serial driver version 4.27 with no serial options enabled ttyS00 at 0x03f8 (irq = 4) is a 16550A pty: 256 Unix98 ptys configured VP_IDE: IDE controller on PCI bus 00 dev 39 VP_IDE: not 100% native mode: will probe irqs later ide0: BM-DMA at 0x6000-0x6007, BIOS settings: hda:pio, hdb:pio ide1: BM-DMA at 0x6008-0x600f, BIOS settings: hdc:pio, hdd:pio Keyboard timeout[2] Keyboard timeout[2] hda: ST32531A, ATA DISK drive hdb: FX810T, ATAPI CDROM drive hdc: IOMEGA ZIP 100 ATAPI, ATAPI FLOPPY drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide1 at 0x170-0x177,0x376 on irq 15 hda: ST32531A, 2439MB w/0kB Cache, CHS=619/128/63 hdb: ATAPI 8X CD-ROM drive, 256kB Cache Uniform CDROM driver Revision: 2.56 FDC 0 is a post-1991 82077 Partition check: hda: hda2 hda3 VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel memory: 60k freed Adding Swap: 60476k swap-space (priority -1) ne.c:v1.10 9/23/94 Donald Becker (becker@cesdis.gsfc.nasa.gov) NE*000 ethercard probe at 0x300: 08 00 00 18 20 07 eth0: NE2000 found at 0x300, using IRQ 5. parport0: PC-style at 0x378 (0x778) [SPP,ECP,ECPPS2] Linux video capture interface: v1.00 V4L-Driver for Vision CPiA based cameras v0.4.4 parport0: read2 timeout. parport0: Multimedia device, VLSI Vision Ltd DUAL Camera Parallel port driver for Vision CPiA based cameras v0.4.4 1 cameras found cpia.c(19607):cpia_open(2466):cpia_open Unable to handle kernel NULL pointer dereference at virtual address 0000000c current->tss.cr3 = 03841000, %cr3 = 03841000 *pde = 00000000 Oops: 0000 CPU: 0 EIP: 0010:[] EFLAGS: 00010212 eax: 00000000 ebx: 00032000 ecx: c3882000 edx: 00000316 esi: c5832000 edi: c5832000 ebp: 0000001f esp: c3883f2c ds: 0018 es: 0018 ss: 0018 Process gqcam (pid: 276, process nr: 40, stackpage=c3883000) Stack: c581b540 c3476640 c58258f0 00031ba5 c3d946ac 00000000 c581b17f c3d946ac 00000000 00000000 c384a480 c375e220 00000051 00000000 000000ff c01c0d9c c01e8b20 c01273eb c375e220 c384a480 c384a480 00000000 c375e220 c01261b8 Call Trace: [] [] [] [] [] [] [] [] Code: 8b 40 0c 8b 14 90 85 d2 74 43 81 e2 00 f0 ff ff 89 f8 c1 e8 --- /var/log/message (since last boot) --- Mar 15 13:59:21 Little syslogd 1.3-3: restart. Mar 15 13:59:24 Little kernel: klogd 1.3-3, log source = /proc/kmsg started. Mar 15 13:59:24 Little kernel: Inspecting /boot/System.map Mar 15 13:59:25 Little kernel: Loaded 6463 symbols from /boot/System.map. Mar 15 13:59:25 Little kernel: Symbols match kernel version 2.2.14. Mar 15 13:59:25 Little kernel: Loaded 6 symbols from 2 modules. Mar 15 13:59:25 Little kernel: ne.c:v1.10 9/23/94 Donald Becker (becker@cesdis.gsfc.nasa.gov) Mar 15 13:59:25 Little kernel: NE*000 ethercard probe at 0x300: 08 00 00 18 20 07 Mar 15 13:59:25 Little kernel: eth0: NE2000 found at 0x300, using IRQ 5. Mar 15 13:59:31 Little /usr/sbin/cron[185]: (CRON) STARTUP (fork ok) Mar 15 13:59:32 Little in.identd[186]: started Mar 15 14:00:03 Little in.telnetd[236]: connect from 192.168.0.1 Mar 15 14:00:04 Little login: pam_unix session started for user root, service login Mar 15 14:00:28 Little kernel: parport0: PC-style at 0x378 (0x778) [SPP,ECP,ECPPS2] Mar 15 14:00:28 Little kernel: Linux video capture interface: v1.00 Mar 15 14:00:28 Little kernel: V4L-Driver for Vision CPiA based cameras v0.4.4 Mar 15 14:00:29 Little modprobe: modprobe: Can't locate module cpia_pp Mar 15 14:00:29 Little kernel: parport0: read2 timeout. Mar 15 14:00:29 Little kernel: parport0: Multimedia device, VLSI Vision Ltd DUAL Camera Mar 15 14:00:29 Little kernel: Parallel port driver for Vision CPiA based cameras v0.4.4 Mar 15 14:00:29 Little kernel: 1 cameras found Mar 15 14:01:59 Little kernel: cpia.c(19607):cpia_open(2466):cpia_open Mar 15 14:01:59 Little kernel: Unable to handle kernel NULL pointer dereference at virtual address 0000000c Mar 15 14:01:59 Little kernel: current->tss.cr3 = 03841000, %cr3 = 03841000 Mar 15 14:01:59 Little kernel: *pde = 00000000 Mar 15 14:01:59 Little kernel: Oops: 0000 Mar 15 14:01:59 Little kernel: CPU: 0 Mar 15 14:01:59 Little kernel: EIP: 0010:[] Mar 15 14:01:59 Little kernel: EFLAGS: 00010212 Mar 15 14:01:59 Little kernel: eax: 00000000 ebx: 00032000 ecx: c3882000 edx: 00000316 Mar 15 14:01:59 Little kernel: esi: c5832000 edi: c5832000 ebp: 0000001f esp: c3883f2c Mar 15 14:01:59 Little kernel: ds: 0018 es: 0018 ss: 0018 Mar 15 14:01:59 Little kernel: Process gqcam (pid: 276, process nr: 40, stackpage=c3883000) Mar 15 14:01:59 Little kernel: Stack: c581b540 c3476640 c58258f0 00031ba5 c3d946ac 00000000 c581b17f c3d946ac Mar 15 14:01:59 Little kernel: 00000000 00000000 c384a480 c375e220 00000051 00000000 000000ff c01c0d9c Mar 15 14:01:59 Little kernel: c01e8b20 c01273eb c375e220 c384a480 c384a480 00000000 c375e220 c01261b8 Mar 15 14:01:59 Little kernel: Call Trace: [] [] [] [tvecs+10012/13216] [chrdev_open+63/76] [filp_open+172/240] [sys_open+82/172] Mar 15 14:01:59 Little kernel: [system_call+52/56] Mar 15 14:01:59 Little kernel: Code: 8b 40 0c 8b 14 90 85 d2 74 43 81 e2 00 f0 ff ff 89 f8 c1 e8 --- cat /proc/interrupts --- CPU0 0: 46211 XT-PIC timer 1: 2 XT-PIC keyboard 2: 0 XT-PIC cascade 5: 2565 XT-PIC NE2000 13: 1 XT-PIC fpu 14: 48176 XT-PIC ide0 15: 2 XT-PIC ide1 NMI: 0 ERR: 0 --- cat /proc/cpia/video0 --- read-only CPIA Version: 0.00 (0.0) CPIA PnP-ID: 0000:0000:0000 VP-Version: 0.0 0000 system_state: 0x00 grab_state: 0x00 stream_state: 0x00 fatal_error: 0x00 cmd_error: 0x00 debug_flags: 0x00 vp_status: 0x00 error_code: 0x00 video_size: CIF sub_sample: 422 yuv_order: YUYV roi: ( 0, 0) to (352, 288) actual_fps: 0 transfer_rate: 500kB/s read-write current min max default comment brightness: 50 0 100 50 contrast: 48 0 96 48 steps of 8 saturation: 50 0 100 50 sensor_fps: 15.000 3 30 15 stream_start_line: 240 0 288 240 ecp_timing: normal slow normal normal color_balance_mode: auto manual auto auto red_gain: 32 0 212 32 green_gain: 6 0 212 6 blue_gain: 92 0 212 92 max_gain: 2 1,2,4,8 2 exposure_mode: auto manual auto auto centre_weight: on off on on gain: 1 1 max_gain 1 1,2,4,8 possible fine_exp: 0 0 511 0 coarse_exp: 185 0 65535 185 red_comp: 220 220 255 220 green1_comp: 214 214 255 214 green2_comp: 214 214 255 214 blue_comp: 230 230 255 230 apcor_gain1: 0x1c 0x0 0xff 0x1c apcor_gain2: 0x1a 0x0 0xff 0x1a apcor_gain4: 0x2d 0x0 0xff 0x2d apcor_gain8: 0x2a 0x0 0xff 0x2a vl_offset_gain1: 24 0 255 24 vl_offset_gain2: 28 0 255 28 vl_offset_gain4: 30 0 255 30 vl_offset_gain8: 30 0 255 30 flicker_control: off off on off mains_frequency: 50 50 60 50 only 50/60 allowable_overexposure: 0 0 255 0 compression_mode: none none,auto,manual auto decimation: off off off off compression_target: quality framerate quality quality target_framerate: 7 0 30 7 target_quality: 10 0 255 10 y_threshold: 15 0 31 15 uv_threshold: 15 0 31 15 hysteresis: 3 0 255 3 threshold_max: 11 0 255 11 small_step: 1 0 255 1 large_step: 3 0 255 3 decimation_hysteresis: 2 0 255 2 fr_diff_step_thresh: 5 0 255 5 q_diff_step_thresh: 3 0 255 3 decimation_thresh_mod: 2 0 255 2 --- cat /proc/parport/0/hardware --- base: 0x378 irq: none dma: none modes: SPP,ECP,ECPPS2 --- cat /proc/parport/0/autoprobe --- CLASS:MEDIA; MODEL:DUAL Camera; MANUFACTURER:VLSI Vision Ltd; DESCRIPTION:Parallel Port Camera; COMMAND SET:CPIA_1-00; --- lsmod --- Module Size Used by parport_probe 2980 0 (autoclean) cpia_pp 16036 0 (unused) cpia 50780 0 [cpia_pp] videodev 2368 1 [cpia] parport_pc 7232 1 [cpia_pp] parport 7272 1 [parport_probe cpia_pp parport_pc] ne 6560 1 (autoclean) 8390 6628 0 (autoclean) [ne] a bit long but i hope it helps. >-Peter > > >------------------------------- >Email: Peter.Pregler@risc.uni-linz.ac.at >WWW: http://www.risc.uni-linz.ac.at/people/ppregler > >_______________________________________________ >cpia mailing list - cpia@risc.uni-linz.ac.at >http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia Regards, Bastian From vincent@linuxbe.org Wed, 15 Mar 2000 18:43:56 +0100 Date: Wed, 15 Mar 2000 18:43:56 +0100 From: vincent vincent@linuxbe.org Subject: [cpia] applications? which applications is available for the quick cam? I can only use "gqcam" I have try "w3cam" but I have a strange picture at some resolution like 80x60 but at 320x240 it s ok. why ? From Peter.Pregler@risc.uni-linz.ac.at Thu, 16 Mar 2000 10:33:26 +0100 (CET) Date: Thu, 16 Mar 2000 10:33:26 +0100 (CET) From: Peter Pregler Peter.Pregler@risc.uni-linz.ac.at Subject: [cpia] cpia-control-0.2.1 now available at sourceforge Hi all, I have released a first version of the cpia-control program at sourceforge. There are no functional changes to version 0.2. I just rewrote the framework, added documentation and created it also as a debian-package (patches for rpms are welcome). See http://sourceforge.net/project/?group_id=3159 for the download. I will add the save/load camera state next. There is already code there but it turned out to need a rewrite of the state-handling module to work reliable. So stay tuned. -Peter ------------------------------- Email: Peter.Pregler@risc.uni-linz.ac.at WWW: http://www.risc.uni-linz.ac.at/people/ppregler From lunarbard@moonman.com Thu, 16 Mar 2000 08:27:14 CST Date: Thu, 16 Mar 2000 08:27:14 CST From: David Cougle lunarbard@moonman.com Subject: [cpia] autoconf.h I cannot compile latest cpia .7.4 cuz 2.2.14 doesn't seem to have an autoconf.h, but i could compile .7.3 and stuff. where might i acquire autoconf.h? -- http://www.slidellweb.com/dcougle ICQ #3795561 Lunarbard on AOL(Instant Messenger) Proverbs 15:3 Linux, operating system of the future "We will not be the alternative, we will set the trend" From Peter.Pregler@risc.uni-linz.ac.at Thu, 16 Mar 2000 18:22:44 +0100 (CET) Date: Thu, 16 Mar 2000 18:22:44 +0100 (CET) From: Peter Pregler Peter.Pregler@risc.uni-linz.ac.at Subject: [cpia] webpage update - developers documentation addendum Hi all, I have added some documention addendum to the developers guide that was sent to me by Henry Bruce to the resources available at the web-page (webcam.sourceforge.net). It is about - anti-flicker control - the meaning of compression quality - ApCor settings - overexposure calculation Could anyone with spare time read it and send me patches? :) The things described should not be that hard to implement. I was also told that VLSI Vision is now called the Imaging Division of STMicroelectronics. Whatever the company is called, thanx again to Henry Bruce for his support. -Peter ------------------------------- Email: Peter.Pregler@risc.uni-linz.ac.at WWW: http://www.risc.uni-linz.ac.at/people/ppregler From Peter.Pregler@risc.uni-linz.ac.at Thu, 16 Mar 2000 18:25:30 +0100 (CET) Date: Thu, 16 Mar 2000 18:25:30 +0100 (CET) From: Peter Pregler Peter.Pregler@risc.uni-linz.ac.at Subject: [cpia] autoconf.h On 16-Mar-2000 David Cougle wrote: > > I cannot compile latest cpia .7.4 cuz 2.2.14 doesn't seem to have an > autoconf.h, but i could compile .7.3 and stuff. > where might i acquire autoconf.h? A 'make config; make depend' in the kernel tree? -Peter ------------------------------- Email: Peter.Pregler@risc.uni-linz.ac.at WWW: http://www.risc.uni-linz.ac.at/people/ppregler From Peter.Pregler@risc.uni-linz.ac.at Thu, 16 Mar 2000 18:28:40 +0100 (CET) Date: Thu, 16 Mar 2000 18:28:40 +0100 (CET) From: Peter Pregler Peter.Pregler@risc.uni-linz.ac.at Subject: [cpia] applications? On 15-Mar-2000 vincent wrote: > which applications is available for the quick cam? > > I can only use "gqcam" > > I have try "w3cam" but I have a strange picture at some resolution like > 80x60 > but at 320x240 it s ok. why ? Any application for v4l should do. See the references at webcam.sourceforge.net. About the resolution issue: this is a problem with the application not the driver. Basically it requests an unsupported resolution and the drivers gives the next closest one. Now the problem is that the applications are written for frame-grabber cards and usually ignore what the driver says it can do since frame-grabber cards can deliver any resolution. -Peter ------------------------------- Email: Peter.Pregler@risc.uni-linz.ac.at WWW: http://www.risc.uni-linz.ac.at/people/ppregler From Peter.Pregler@risc.uni-linz.ac.at Thu, 16 Mar 2000 18:42:39 +0100 (CET) Date: Thu, 16 Mar 2000 18:42:39 +0100 (CET) From: Peter Pregler Peter.Pregler@risc.uni-linz.ac.at Subject: [cpia] still hoping On 15-Mar-2000 Bastian wrote: > ok, i've done the following : > - disabled the isdn/hisax drivers > - compiled the 0.4.4 cpia module (disabled DMA in makefile and added the > include line) > - loaded the parport, videodev and cpia modules using the script loadpp > > here are the results AFTER starting gqcam : Okay, is it possible that some syslog-output is missing? There should be some lines with the string 'goto_high/low_power' and 'save_camera_state'. Anyway, the empty version-fields in the /proc/cpia/videoN indicate that the first power up of the camera failed. I have some suggestion that might help with this. Stay tuned. Apparently there is also a bug in the module load that allows an open even if the initial query of the camera failed. I check that out. It is the source of the ooops but it is not the source of your problem. I try to make a short test patch this evening. Greetings, Peter ------------------------------- Email: Peter.Pregler@risc.uni-linz.ac.at WWW: http://www.risc.uni-linz.ac.at/people/ppregler From Peter.Pregler@risc.uni-linz.ac.at Thu, 16 Mar 2000 18:43:56 +0100 (CET) Date: Thu, 16 Mar 2000 18:43:56 +0100 (CET) From: Peter Pregler Peter.Pregler@risc.uni-linz.ac.at Subject: [cpia] gqcam with Creative WebCam II On 15-Mar-2000 Sang Y. Yum wrote: > My bad. I bought a OEM version of this camera, which > came with no documentation. I did not realize that the > extra dangling connection were to be plugged into the > keyboard connector, which, I guess, is a power source. That is good to know. I will check the driver with respect to that 'sillyness'. Maybe we can give a more reasonable error-message. > Anyway, I am getting close but no dough. gqcam > displays a couple of frames, the picture freezes and > gqcam spits out "Error reading image..." repeatedly > and I see these messages repeated in dmesg: > > cpia.c:parse_picture(1901):header not found > cpia.c(3629046):fetch_frame(2231):parse_picture failed > -1 The driver read some garbage from the camera. I have not seen that message for quite some time in the parport case. Can you check the syslog-file /var/log/kernel.log or whatever for more info. We need the complete output. See the list-archive, I have given the list of what is needed in numerous mails before. -Peter ------------------------------- Email: Peter.Pregler@risc.uni-linz.ac.at WWW: http://www.risc.uni-linz.ac.at/people/ppregler From tdat@yahoo.com Fri, 17 Mar 2000 09:58:22 -0800 (PST) Date: Fri, 17 Mar 2000 09:58:22 -0800 (PST) From: Sang Y. Yum tdat@yahoo.com Subject: [cpia] gqcam with Creative WebCam II --- Peter Pregler wrote: > > The driver read some garbage from the camera. I have > not seen that message > for quite some time in the parport case. Can you > check the syslog-file > /var/log/kernel.log or whatever for more info. We > need the complete > output. See the list-archive, I have given the list > of what is needed in > numerous mails before. Peter, thanks for staying with me here. I documented all the outputs and placed them at http://www.yumnet.dyndns.org/~sang/linux/webcam.html I browsed thru list-archive but didn't find anything that seemed relevant to my problem. I will look at it again. Thanks. Sang ===== Sang Y. Yum http://www.yumnet.dyndns.org/~sang San Diego, CA mailto:tdat@yahoo.com __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com From tdat@yahoo.com Fri, 17 Mar 2000 11:48:38 -0800 (PST) Date: Fri, 17 Mar 2000 11:48:38 -0800 (PST) From: Sang Y. Yum tdat@yahoo.com Subject: [cpia] gqcam with Creative WebCam II Peter, I found a reference to "parse_header" routine and some comments around it. It gave me an idea that my problem might have something to do with compression. I went back to cpia source code to see if there is a way to turn off the compression. Ahah, in README, there was a line that shows how to control the camera setting from command line. So, I executed: [root@pikatsu cpia-0.7.3]# echo "compression_mode:none" >> /proc/cpia/video1 Bam, gqcam displays a beautiful video of my empty room. (I've been doing this from work. Really should get back to work... :). Thanks. Sang ===== Sang Y. Yum http://www.yumnet.dyndns.org/~sang San Diego, CA mailto:tdat@yahoo.com __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com From Peter.Pregler@risc.uni-linz.ac.at Sat, 18 Mar 2000 15:05:31 +0100 (CET) Date: Sat, 18 Mar 2000 15:05:31 +0100 (CET) From: Peter Pregler Peter.Pregler@risc.uni-linz.ac.at Subject: [cpia] Webcam II & bi-directional port On 05-Feb-1999 tom@eufemio.free-online.co.uk wrote: > > According to creative their webcam II > can work with a birdirectional llel > port. > > Is there any reason why yht linux > driver docs say you need an ECP. > > Is it a difficult job to add > bidirectional support? The camera can talk a nibble-mode variant. But none has cared to implement that yet. It is in the todo-list for ages. I can point you to the relevant documentation if you want to give it a try. -Peter ------------------------------- Even the thought that a ship was waiting to take him back to Earth did not wipe out the sense of loss he felt at that moment. ------------------------------- Email: Peter.Pregler@risc.uni-linz.ac.at Peter Pregler / RISC, University of Linz, Austria From sbertin@mindspring.com Sat, 18 Mar 2000 10:58:01 -0500 (EST) Date: Sat, 18 Mar 2000 10:58:01 -0500 (EST) From: sbertin@mindspring.com sbertin@mindspring.com Subject: [cpia] Webcam II & bi-directional port On 18 Mar, Peter Pregler wrote: > > On 05-Feb-1999 tom@eufemio.free-online.co.uk wrote: >> Is it a difficult job to add >> bidirectional support? > > The camera can talk a nibble-mode variant. But none has cared to implement > that yet. It is in the todo-list for ages. I can point you to the relevant > documentation if you want to give it a try. Using a 2.3 kernel, any parallel port that supports TRISTATE mode can use software emulation of ECP to talk to the camera. This probably covers most bidirectional ports. Scott J. Bertin sbertin@mindsprring.com From tumati@students.uiuc.edu Sun, 19 Mar 2000 22:28:54 -0600 (CST) Date: Sun, 19 Mar 2000 22:28:54 -0600 (CST) From: Pavan tumati@students.uiuc.edu Subject: [cpia] CU SeeMe Cam Kit Problems, & Cpia driver 0.7.4 I have been attempting to get my CU-SeeMe CamKit Camera to work under linux. I compiled the modules successfully, and got the modules to load. On one machine, the system loaded the drivers, but when I attempted to grab pictures, it was garbled. On the system I am currently trying it on, the client programs insist the device does not exist. The driver says 1 camera was found, but spits out all sorts of strange information that, at this point, does not make sense to me. I would appreciate it if someone on this list could assist me. I apologize if the contents of this message were contained elsewhere in the mail archives. In the initial computer setup, I have the parallel port set at ECCEPP1.9, and I have tried ECCEPP1.7, and I have tried both ECP and EPP. ECCEPP1.9 seems to be the only one that gives me any good results. Also -- *** I compiled without the DMA option when compiling the modules to avoid problems. In either case, the setup is not working. *** This is what I get out of 'dmesg': Linux video capture interface: v1.00 V4L-Driver for Vision CPiA based cameras v0.7.4 parport0: PC-style at 0x378 [SPP,ECP,ECPEPP,ECPPS2] parport0: detected irq 7; use procfs to enable interrupt-driven operation. parport0: read2 timeout. parport0: Multimedia device, VLSI Vision Ltd PPC2 Camera Parallel port driver for Vision CPiA based cameras v0.7.4 cpia_pp.c(19332):my_wait_peripheral(325):failed 0x0 should be 0x38 waited 33 jiffies cpia_pp.c(19332):Negotiate2SetupPhase(373):B failed cpia_pp.c(19332):ForwardSetup(833):could not negotiate for setup phase cpia_pp.c(19334):WritePacket(1094):Write failed in setup cpia_pp.c(19334):cpia_pp_transferCmd(1314):Error writing command cpia.c(19334):do_command(1651):4005 - failed, retval=-5 1 camera(s) found ... As for the parport information: [tumati@undergrad1 0]$ ls autoprobe devices hardware irq [tumati@undergrad1 0]$ cat autoprobe CLASS:MEDIA; MODEL:PPC2 Camera; MANUFACTURER:VLSI Vision Ltd; DESCRIPTION:Parallel Port Camera; COMMAND SET:CPIA_1-20; And... [tumati@undergrad1 0]$ cat devices cpia_pp [tumati@undergrad1 0]$ [tumati@undergrad1 0]$ cat hardware base: 0x378 irq: none dma: none modes: SPP,ECP,ECPEPP,ECPPS2 [tumati@undergrad1 0]$ [tumati@undergrad1 0]$ cat irq none [tumati@undergrad1 0]$ Any and all help would be appreciated... Again, I apologize for repeat of information already posted. -Pavan Tumati From tumati@students.uiuc.edu Mon, 20 Mar 2000 15:49:57 -0600 (CST) Date: Mon, 20 Mar 2000 15:49:57 -0600 (CST) From: Pavan tumati@students.uiuc.edu Subject: [cpia] CU SeeMe Cam Kit Problems, & Cpia driver 0.7.4 Nevermind. These drivers and the camera are working fine. I just made a silly mistake on my single board computer. Thanks for the quality drivers. :) On Sun, 19 Mar 2000, Pavan wrote: > > I have been attempting to get my CU-SeeMe CamKit Camera to work under > linux. I compiled the modules successfully, and got the modules to load. > On one machine, the system loaded the drivers, but when I attempted to > grab pictures, it was garbled. On the system I am currently trying it on, > the client programs insist the device does not exist. The driver says 1 > camera was found, but spits out all sorts of strange information that, at > this point, does not make sense to me. I would appreciate it if someone > on this list could assist me. I apologize if the contents of this message > were contained elsewhere in the mail archives. From jto@bdc.no Tue, 21 Mar 2000 07:39:27 +0100 Date: Tue, 21 Mar 2000 07:39:27 +0100 From: Jarl Totland jto@bdc.no Subject: [cpia] Are the CPiA parport webcams still available? I have received several queries on this the last few months. It seems today one has to put some effort into finding any CPiA cams at all. Could all of you who have bought CPiA cams lately, even if it's USB, send me a note on where it's available? I'll compile the information and put it online. Thanks. Vyrdsamt, -Jarl From Peter.Pregler@risc.uni-linz.ac.at Tue, 21 Mar 2000 17:29:32 +0100 (CET) Date: Tue, 21 Mar 2000 17:29:32 +0100 (CET) From: Peter Pregler Peter.Pregler@risc.uni-linz.ac.at Subject: [cpia] at what time should we goto_high_power Dear all, I got the information below about how the camera does handle setting changes. This has quite some impact on the basic layout of the linux driver. I have written it under the implicit assumption that the first frame I read from the camera can read with the settings (exposure, gain, color balance, ...) I want. Now in the worst case it seems that it takes up to 8 frames until I get what I really want. Why does this affect the current driver operation? With the current driver the camera power is switched on only _after_ the first device is opened. So unless you have a device open the camera is in power-save mode (i.e. the video processor is not running). I thought this is a reasonable model since linux-boxes tend to run all day (contrary to M$-stuff which is rebooted on demand ;), but the camera does not. Now the new information is that it can take 8 frames until the picture looks like the way you want it after you have switched power on, i.e. in the current driver afer you opened the device. Rigth now the driver throws away the first one or two images which works moderatly well with most settings. Note that this problem will not affect video-conferencing stuff, but webcam-software that does a open/read/close to get a single frame is heavily affected by this. Also for grabbing videos the first few frames will be 'bad'. My question is: should we switch on power as soon as the driver is loaded. So the video-processor will run all the time? Is this bad for camera lifetime? I certainly do not want to throw away the first 8 frames if the user changed any setting. Adding a special load-time option will blow up the code a bit but looks reasonable. Any other suggestions? I do not want to force a special power-on model. -Peter -----FW: <200003201517.PAA20497@matthau.vvl.co.uk>----- Date: Mon, 20 Mar 2000 15:17:32 GMT From: Henry Bruce To: Peter.Pregler@risc.uni-linz.ac.at Subject: Re: Fw: RE: [cpia] VIDIOCSWIN/reset_camera_struct and weird colors Cc: Henry.BRUCE@matthau.vvl.co.uk Here's a simplification of what happens: If a grab is taking place then the camera takes the new settings and applies them to the next frame to be uploaded. Exposure sensor gain and compensation gain settings take effect up to 1 frame later. If a combination of settings are changed during 1 frame period then it make take several frames for all settings to take effect. When the camera switched to high power mode, the firmware spends approximately 8 frames downloading default settings. The first frame will always be uncompressed. To avoid recieving frames in the wrong format, disable grabbing before applying the new settings, wait a few frames and start grabbing again. --------------End of forwarded message------------------------- ------------------------------- Email: Peter.Pregler@risc.uni-linz.ac.at WWW: http://www.risc.uni-linz.ac.at/people/ppregler From jackdied@yahoo.com Thu, 23 Mar 2000 10:41:50 -0800 (PST) Date: Thu, 23 Mar 2000 10:41:50 -0800 (PST) From: john smallberries jackdied@yahoo.com Subject: [cpia] cpia.c yuvconvert hack --0-861021530-953836910=:3728 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Just for kicks here is some modifications I made to the yuvconvert routine. Basically I just expanded all the rgb calculations, combined like terms and did all that other 8th grade algebra. The end result doesn't appear any faster, and isn't even actually correct. I include some funky shift ops that are about 5% off the correct color, but should be a little bit faster than multiplying and getting the correct result. This affects 1/2 of the pixels. I can't tell the difference when looking at the picture, however. This only covers the RGB24 and RGB 32 calculations, all the others are unchanged. The attached diff is against 0.7.4 -smallberries __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com --0-861021530-953836910=:3728 Content-Type: application/x-unknown; name="cpia.c.diff" Content-Description: cpia.c.diff Content-Disposition: attachment; filename="cpia.c.diff" Content-Transfer-Encoding: base64 KioqIGNwaWEuYwlTYXQgTWFyIDExIDE2OjQ0OjAxIDIwMDAKLS0tIC4uLy4u L2NwaWEtamFjay9tb2R1bGUvY3BpYS5jCVRodSBNYXIgMTYgMDc6NTI6MzAg MjAwMAoqKioqKioqKioqKioqKioKKioqIDE3NzAsMTg4MyAqKioqCiAgICog Q29sb3JzcGFjZSBjb252ZXJzaW9uCiAgICoKICAgKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKi8KISAjZGVmaW5lIExJTUlUKHgpICgoKCh4KT4weGZmZmZm Zik/MHhmZjAwMDA6KCgoeCk8PTB4ZmZmZik/MDooeCkmMHhmZjAwMDApKT4+ MTYpCiAgCiAgc3RhdGljIGludCB5dXZjb252ZXJ0KHVuc2lnbmVkIGNoYXIg Knl1diwgdW5zaWduZWQgY2hhciAqcmdiLCBpbnQgb3V0X2ZtdCwKICAgICAg ICAgICAgICAgICAgICAgICAgaW50IGluX3V5dnksIGludCBtbWFwX2tsdWRn ZSkKICB7CiEgCWludCB5LCB1LCB2LCByLCBnLCBiLCB5MTsKISAKISAJc3dp dGNoKG91dF9mbXQpIHsKISAJY2FzZSBWSURFT19QQUxFVFRFX1JHQjU1NToK ISAJY2FzZSBWSURFT19QQUxFVFRFX1JHQjU2NToKISAJY2FzZSBWSURFT19Q QUxFVFRFX1JHQjI0OgohIAljYXNlIFZJREVPX1BBTEVUVEVfUkdCMzI6CiEg CQlpZiAoaW5fdXl2eSkgewohIAkJCXUgPSAqeXV2KysgLSAxMjg7CiEgCQkJ eSA9ICgqeXV2KysgLSAxNikgKiA3NjMxMDsKISAJCQl2ID0gKnl1disrIC0g MTI4OwohIAkJCXkxID0gKCp5dXYgLSAxNikgKiA3NjMxMDsKISAJCX0gZWxz ZSB7CiEgCQkJeSA9ICgqeXV2KysgLSAxNikgKiA3NjMxMDsKISAJCQl1ID0g Knl1disrIC0gMTI4OwohIAkJCXkxID0gKCp5dXYrKyAtIDE2KSAqIDc2MzEw OwohIAkJCXYgPSAqeXV2IC0gMTI4OwohIAkJfQohIAkJciA9IDEwNDYzNSAq IHY7CiEgCQlnID0gLTI1NjkwICogdSArIC01MzI5NCAqIHY7CiEgCQliID0g MTMyMjc4ICogdTsKISAJCWJyZWFrOwohIAlkZWZhdWx0OgohIAkJeSA9ICp5 dXYrKzsKISAJCXUgPSAqeXV2Kys7CiEgCQl5MSA9ICp5dXYrKzsKISAJCXYg PSAqeXV2OwohIAkJLyogSnVzdCB0byBhdm9pZCBjb21waWxlciB3YXJuaW5n cyAqLwohIAkJciA9IDA7CiEgCQlnID0gMDsKISAJCWIgPSAwOwohIAkJYnJl YWs7CiEgCX0KISAJc3dpdGNoKG91dF9mbXQpIHsKISAJY2FzZSBWSURFT19Q QUxFVFRFX1JHQjU1NToKISAJCSpyZ2IrKyA9ICgoTElNSVQoZyt5KSAmIDB4 ZjgpIDw8IDIpIHwgKExJTUlUKGIreSkgPj4gMyk7CiEgCQkqcmdiKysgPSAo KExJTUlUKHIreSkgJiAweGY4KSA+PiAxKSB8IChMSU1JVChnK3kpID4+IDYp OwohIAkJKnJnYisrID0gKChMSU1JVChnK3kxKSAmIDB4ZjgpIDw8IDIpIHwg KExJTUlUKGIreTEpID4+IDMpOwohIAkJKnJnYiA9ICgoTElNSVQocit5MSkg JiAweGY4KSA+PiAxKSB8IChMSU1JVChnK3kxKSA+PiA2KTsKISAJCXJldHVy biA0OwohIAljYXNlIFZJREVPX1BBTEVUVEVfUkdCNTY1OgohIAkJKnJnYisr ID0gKChMSU1JVChnK3kpICYgMHhmYykgPDwgMykgfCAoTElNSVQoYit5KSA+ PiAzKTsKISAJCSpyZ2IrKyA9IChMSU1JVChyK3kpICYgMHhmOCkgfCAoTElN SVQoZyt5KSA+PiA1KTsKISAJCSpyZ2IrKyA9ICgoTElNSVQoZyt5MSkgJiAw eGZjKSA8PCAzKSB8IChMSU1JVChiK3kxKSA+PiAzKTsKISAJCSpyZ2IgPSAo TElNSVQocit5MSkgJiAweGY4KSB8IChMSU1JVChnK3kxKSA+PiA1KTsKISAJ CXJldHVybiA0OwohIAljYXNlIFZJREVPX1BBTEVUVEVfUkdCMjQ6CiEgCQlp ZiAobW1hcF9rbHVkZ2UpIHsKISAJCQkqcmdiKysgPSBMSU1JVChiK3kpOwoh IAkJCSpyZ2IrKyA9IExJTUlUKGcreSk7CiEgCQkJKnJnYisrID0gTElNSVQo cit5KTsKISAJCQkqcmdiKysgPSBMSU1JVChiK3kxKTsKISAJCQkqcmdiKysg PSBMSU1JVChnK3kxKTsKISAJCQkqcmdiID0gTElNSVQocit5MSk7CiEgCQl9 IGVsc2UgewohIAkJCSpyZ2IrKyA9IExJTUlUKHIreSk7CiEgCQkJKnJnYisr ID0gTElNSVQoZyt5KTsKISAJCQkqcmdiKysgPSBMSU1JVChiK3kpOwohIAkJ CSpyZ2IrKyA9IExJTUlUKHIreTEpOwohIAkJCSpyZ2IrKyA9IExJTUlUKGcr eTEpOwohIAkJCSpyZ2IgPSBMSU1JVChiK3kxKTsKISAJCX0KISAJCXJldHVy biA2OwohIAljYXNlIFZJREVPX1BBTEVUVEVfUkdCMzI6CiEgCQlpZiAobW1h cF9rbHVkZ2UpIHsKISAJCQkqcmdiKysgPSBMSU1JVChiK3kpOwohIAkJCSpy Z2IrKyA9IExJTUlUKGcreSk7CiEgCQkJKnJnYisrID0gTElNSVQocit5KTsK ISAJCQlyZ2IrKzsKISAJCQkqcmdiKysgPSBMSU1JVChiK3kxKTsKISAJCQkq cmdiKysgPSBMSU1JVChnK3kxKTsKISAJCQkqcmdiID0gTElNSVQocit5MSk7 CiEgCQl9IGVsc2UgewohIAkJCSpyZ2IrKyA9IExJTUlUKHIreSk7CiEgCQkJ KnJnYisrID0gTElNSVQoZyt5KTsKISAJCQkqcmdiKysgPSBMSU1JVChiK3kp OwohIAkJCXJnYisrOwohIAkJCSpyZ2IrKyA9IExJTUlUKHIreTEpOwohIAkJ CSpyZ2IrKyA9IExJTUlUKGcreTEpOwohIAkJCSpyZ2IgPSBMSU1JVChiK3kx KTsKISAJCX0KISAJCXJldHVybiA4OwohIAljYXNlIFZJREVPX1BBTEVUVEVf R1JFWToKISAJCSpyZ2IrKyA9IHk7CiEgCQkqcmdiID0geTE7CiEgCQlyZXR1 cm4gMjsKISAJY2FzZSBWSURFT19QQUxFVFRFX1lVVjQyMjoKISAJY2FzZSBW SURFT19QQUxFVFRFX1lVWVY6CiEgCQkqcmdiKysgPSB5OwohIAkJKnJnYisr ID0gdTsKISAJCSpyZ2IrKyA9IHkxOwohIAkJKnJnYiA9IHY7CiEgCQlyZXR1 cm4gNDsKISAJY2FzZSBWSURFT19QQUxFVFRFX1VZVlk6CiEgCQkqcmdiKysg PSB1OwohIAkJKnJnYisrID0geTsKISAJCSpyZ2IrKyA9IHY7CiEgCQkqcmdi ID0geTE7CiEgCQlyZXR1cm4gNDsKISAJZGVmYXVsdDoKISAJCURCRygiRW1w dHk6ICVkXG4iLCBvdXRfZm10KTsKISAJCXJldHVybiAwOwogIAl9CiAgfQog IAogIHN0YXRpYyBpbnQgc2tpcGNvdW50KGludCBjb3VudCwgaW50IGZtdCkK LS0tIDE3NzAsMTkyMCAtLS0tCiAgICogQ29sb3JzcGFjZSBjb252ZXJzaW9u CiAgICoKICAgKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKi8KISAvKiAjZGVm aW5lIExJTUlUKHgpICgoKCh4KT4weGZmZmZmZik/MHhmZjAwMDA6KCgoeCk8 PTB4ZmZmZik/MDooeCkmMHhmZjAwMDApKT4+MTYpICovCiEgaW5saW5lIAoh IHN0YXRpYyBpbnQgTElNSVQoIGludCBpbnZhbCApIHsKISAgIGludCByZXR2 YWw7CiEgICBpZiggaW52YWwgPiAweGZmZmZmZiApCiEgICAgIHJldHZhbCA9 IDB4ZmY7CiEgICBlbHNlIGlmKCBpbnZhbCA8PSAweDAwZmZmZiApIAohICAg ICByZXR2YWwgPSAwOwohICAgZWxzZQohICAgICByZXR2YWwgPSBpbnZhbCA+ PiAxNjsKISAgIHJldHVybiByZXR2YWw7CiEgfQogIAorIC8qIENvbnN0YW50 cyB0aGF0IGFwcGVhciBpbiB5dXZjb252ZXJzaW9uICovCisgc3RhdGljIGNv bnN0IGludCBteV9BID0gMTI4OworIHN0YXRpYyBjb25zdCBpbnQgbXlfQiA9 IDE2OworIHN0YXRpYyBjb25zdCBpbnQgbXlfQyA9IDc2MzEwOworIHN0YXRp YyBjb25zdCBpbnQgbXlfRCA9IDEwNDYzNTsKKyBzdGF0aWMgY29uc3QgaW50 IG15X0FBID0gMjU2OTA7Cisgc3RhdGljIGNvbnN0IGludCBteV9CQiA9IDUz Mjk0OworIHN0YXRpYyBjb25zdCBpbnQgbXlfQ0MgPSAxMzIyNzg7CisgLyog Q29tb3VuZCBjb25zdGFudHMsIGVuZCByZXN1bHQgb2YgbXVsdHMgYW5kIGFk ZHMgKi8KKyBzdGF0aWMgY29uc3QgaW50IHJSID0gLTE0NjE0MjQwOyAvKiAo LSAoIG15X0EgKiBteV9EICsgbXlfQiAqIG15X0MgKSk7ICovCisgc3RhdGlj IGNvbnN0IGludCBnUiA9IDIzMTIzNTI7IC8qICggbXlfQSAqIG15X0JCIC0g bXlfQSAqIG15X0FBIC0gbXlfQiAqIG15X0MgKTsgKi8KKyBzdGF0aWMgY29u c3QgaW50IGJSID0gLTE4MTUyNTQ0OyAvKiAoLTEgKiAoIG15X0IgKiBteV9D ICsgbXlfQSAqIG15X0NDICkpOyAqLworIAorIGlubGluZQogIHN0YXRpYyBp bnQgeXV2Y29udmVydCh1bnNpZ25lZCBjaGFyICp5dXYsIHVuc2lnbmVkIGNo YXIgKnJnYiwgaW50IG91dF9mbXQsCiAgICAgICAgICAgICAgICAgICAgICAg IGludCBpbl91eXZ5LCBpbnQgbW1hcF9rbHVkZ2UpCiAgewohICAgc3dpdGNo KG91dF9mbXQpIHsKISAgIGNhc2UgVklERU9fUEFMRVRURV9SR0IyNDoKISAg IGNhc2UgVklERU9fUEFMRVRURV9SR0IzMjoKISAgICAgewohICAgICAgIGlu dCB4MCwgeDEsIHgyLCB4MzsKISAgICAgICBpbnQgdDBhLCB0MGIsIHQxLCB0 MmEsIHQyYiwgdDM7CiEgICAgICAgaWYgKGluX3V5dnkpIHsKISAJeDIgPSAq eXV2Kys7CiEgCXgxID0gKnl1disrOwohIAl4MCA9ICp5dXYrKzsKISAJeDMg PSAqeXV2OwohICAgICAgIH0gZWxzZSB7CiEgCXgxID0gKnl1disrOwohIAl4 MiA9ICp5dXYrKzsKISAJeDMgPSAqeXV2Kys7CiEgCXgwID0gKnl1djsKISAg ICAgICB9CiEgICAgICAgdDEgID0gbXlfQyAqIHgxOwohICAgICAgIHQzICA9 IG15X0MgKiB4MzsKISAgICAgICB0MGEgPSBteV9EICogeDA7ICAKISAgICAg ICB0MGIgPSB0MGEgPj4gMTsgLyogdDBiID0gbXlfQkIgKiB4MDsgKi8KISAg ICAgICB0MmEgPSBteV9BQSAqIHgyOyAKISAgICAgICB0MmIgPSAoIHQyYSA8 PCAyICkgKyB0MmE7IC8qIHQyYiA9IG15X0NDICogeDI7ICovCiEgICAgICAg CiEgICAgICAgaWYgKG1tYXBfa2x1ZGdlKSB7CiEgCSpyZ2IrKyA9IExJTUlU KCB0MSArIHQyYiArIGJSICk7CiEgCSpyZ2IrKyA9IExJTUlUKCB0MmEgLSB0 MGIgKyB0MSArIGdSICk7CiEgCSpyZ2IrKyA9IExJTUlUKCB0MGEgKyB0MSAr IHJSICk7CiEgCSpyZ2IrKyA9IExJTUlUKCB0MyArIHQyYiArIGJSICk7CiEg CSpyZ2IrKyA9IExJTUlUKCB0MmEgLSB0MGIgKyB0MyArIGdSICk7CiEgCSpy Z2IgPSBMSU1JVCggdDBhICsgdDMgKyByUiApOwohICAgICAgIH0gZWxzZSB7 CiEgCSpyZ2IrKyA9IExJTUlUKCB0MGEgKyB0MSArIHJSICk7CiEgCSpyZ2Ir KyA9IExJTUlUKCB0MmEgLSB0MGIgKyB0MSArIGdSICk7CiEgCSpyZ2IrKyA9 IExJTUlUKCB0MSArIHQyYiArIGJSICk7CiEgCSpyZ2IrKyA9IExJTUlUKCB0 MGEgKyB0MyArIHJSICk7CiEgCSpyZ2IrKyA9IExJTUlUKCB0MmEgLSB0MGIg KyB0MyArIGdSICk7CiEgCSpyZ2IgPSBMSU1JVCggdDMgKyB0MmIgKyBiUiAp OwohICAgICAgIH0KISAgICAgICBpZiggb3V0X2ZtdCA9PSBWSURFT19QQUxF VFRFX1JHQjI0ICkKISAJcmV0dXJuIDY7CiEgICAgICAgZWxzZQohIAlyZXR1 cm4gODsKISAgICAgfQohICAgICBicmVhazsKISAgIGRlZmF1bHQ6CiEgICAg IHsKISAgICAgICBpbnQgeSwgdSwgdiwgciwgZywgYiwgeTE7CiEgICAgICAg c3dpdGNoKG91dF9mbXQpIHsKISAgICAgICBjYXNlIFZJREVPX1BBTEVUVEVf UkdCNTU1OgohICAgICAgIGNhc2UgVklERU9fUEFMRVRURV9SR0I1NjU6CiEg CWlmIChpbl91eXZ5KSB7CiEgCSAgdSA9ICp5dXYrKyAtIDEyODsKISAJICB5 ID0gKCp5dXYrKyAtIDE2KSAqIDc2MzEwOwohIAkgIHYgPSAqeXV2KysgLSAx Mjg7CiEgCSAgeTEgPSAoKnl1diAtIDE2KSAqIDc2MzEwOwohIAl9IGVsc2Ug ewohIAkgIHkgPSAoKnl1disrIC0gMTYpICogNzYzMTA7CiEgCSAgdSA9ICp5 dXYrKyAtIDEyODsKISAJICB5MSA9ICgqeXV2KysgLSAxNikgKiA3NjMxMDsK ISAJICB2ID0gKnl1diAtIDEyODsKICAJfQorIAlyID0gMTA0NjM1ICogdjsK KyAJZyA9IC0yNTY5MCAqIHUgKyAtNTMyOTQgKiB2OworIAliID0gMTMyMjc4 ICogdTsKKyAJYnJlYWs7CisgICAgICAgZGVmYXVsdDoKKyAJeSA9ICp5dXYr KzsKKyAJdSA9ICp5dXYrKzsKKyAJeTEgPSAqeXV2Kys7CisgCXYgPSAqeXV2 OworIAkvKiBKdXN0IHRvIGF2b2lkIGNvbXBpbGVyIHdhcm5pbmdzICovCisg CXIgPSAwOworIAlnID0gMDsKKyAJYiA9IDA7CisgCWJyZWFrOworICAgICAg IH0gCisgICAgICAgc3dpdGNoKG91dF9mbXQpIHsKKyAgICAgICBjYXNlIFZJ REVPX1BBTEVUVEVfUkdCNTU1OgorIAkqcmdiKysgPSAoKExJTUlUKGcreSkg JiAweGY4KSA8PCAyKSB8IChMSU1JVChiK3kpID4+IDMpOworIAkqcmdiKysg PSAoKExJTUlUKHIreSkgJiAweGY4KSA+PiAxKSB8IChMSU1JVChnK3kpID4+ IDYpOworIAkqcmdiKysgPSAoKExJTUlUKGcreTEpICYgMHhmOCkgPDwgMikg fCAoTElNSVQoYit5MSkgPj4gMyk7CisgCSpyZ2IgPSAoKExJTUlUKHIreTEp ICYgMHhmOCkgPj4gMSkgfCAoTElNSVQoZyt5MSkgPj4gNik7CisgCXJldHVy biA0OworICAgICAgIGNhc2UgVklERU9fUEFMRVRURV9SR0I1NjU6CisgCSpy Z2IrKyA9ICgoTElNSVQoZyt5KSAmIDB4ZmMpIDw8IDMpIHwgKExJTUlUKGIr eSkgPj4gMyk7CisgCSpyZ2IrKyA9IChMSU1JVChyK3kpICYgMHhmOCkgfCAo TElNSVQoZyt5KSA+PiA1KTsKKyAJKnJnYisrID0gKChMSU1JVChnK3kxKSAm IDB4ZmMpIDw8IDMpIHwgKExJTUlUKGIreTEpID4+IDMpOworIAkqcmdiID0g KExJTUlUKHIreTEpICYgMHhmOCkgfCAoTElNSVQoZyt5MSkgPj4gNSk7Cisg CXJldHVybiA0OyAKKyAgICAgICBjYXNlIFZJREVPX1BBTEVUVEVfR1JFWToK KyAJKnJnYisrID0geTsKKyAJKnJnYiA9IHkxOworIAlyZXR1cm4gMjsKKyAg ICAgICBjYXNlIFZJREVPX1BBTEVUVEVfWVVWNDIyOgorICAgICAgIGNhc2Ug VklERU9fUEFMRVRURV9ZVVlWOgorIAkqcmdiKysgPSB5OworIAkqcmdiKysg PSB1OworIAkqcmdiKysgPSB5MTsKKyAJKnJnYiA9IHY7CisgCXJldHVybiA0 OworICAgICAgIGNhc2UgVklERU9fUEFMRVRURV9VWVZZOgorIAkqcmdiKysg PSB1OworIAkqcmdiKysgPSB5OworIAkqcmdiKysgPSB2OworIAkqcmdiID0g eTE7CisgCXJldHVybiA0OworICAgICAgIGRlZmF1bHQ6CisgCURCRygiRW1w dHk6ICVkXG4iLCBvdXRfZm10KTsKKyAJcmV0dXJuIDA7CisgICAgICAgfSAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIAor ICAgICB9CisgICAgIGJyZWFrOworICAgfQorICAgcmV0dXJuIDA7IC8qIHVu cmVhY2hhYmxlICovCiAgfQogIAogIHN0YXRpYyBpbnQgc2tpcGNvdW50KGlu dCBjb3VudCwgaW50IGZtdCkK --0-861021530-953836910=:3728-- From Peter.Pregler@risc.uni-linz.ac.at Fri, 24 Mar 2000 00:09:10 +0100 (CET) Date: Fri, 24 Mar 2000 00:09:10 +0100 (CET) From: Peter Pregler Peter.Pregler@risc.uni-linz.ac.at Subject: [cpia] new version of cpia-control Hi all, I have released a new version of the control client. New features are: - added support for saving/loading the camera state - the GUI now tracks the camera state - various bug fixes It is available at: http://sourceforge.net/project/?group_id=3159 This is close to the final version from my side. If you want some additional features step forward now or implement it yourself. There are a lot of things in the todo. Do not take that too serious. I am bored with it. :) Have fun, Peter ------------------------------- Even the thought that a ship was waiting to take him back to Earth did not wipe out the sense of loss he felt at that moment. ------------------------------- Email: Peter.Pregler@risc.uni-linz.ac.at Peter Pregler / RISC, University of Linz, Austria From root@mail.velenje.cx Fri, 24 Mar 2000 00:53:28 +0100 (CET) Date: Fri, 24 Mar 2000 00:53:28 +0100 (CET) From: Samo Gabrovec root@mail.velenje.cx Subject: [cpia] Debug .. Hello. i used cpia 0.7.1 and in the Makefile i have commented the line # DEBUG = -D_CPIA_DEBUG_ compiled and i`ve gor a module which is NOT loud and it works. today i have dl-ed the 0.7.4 and at first forgot to coment it out, loaded the modules and i saw that every pic that it takes there`s one line in my logs. ok i coment out the debug line and tried to re-compile but it wont. i get an error +++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++ mail:/download/cpia-0.7.4/module # make gcc -c -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -pipe -fno-strength-reduce -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=686 -fomit-frame-pointer -fno-strength-reduce -I. -I/usr/src/linux/include -D__KERNEL__ -DMODULE -DCONFIG_VIDEO_CPIA_MODULE -DCONFIG_VIDEO_CPIA_PP_MODULE -DCONFIG_VIDEO_CPIA_PP_DMA cpia.c cpia.c: In function `do_command': cpia.c:1652: parse error before `else' cpia.c:1659: break statement not within loop or switch cpia.c:1660: case label not within a switch statement cpia.c:1665: break statement not within loop or switch cpia.c:1666: case label not within a switch statement cpia.c:1675: break statement not within loop or switch cpia.c:1676: case label not within a switch statement cpia.c:1681: break statement not within loop or switch cpia.c:1682: case label not within a switch statement cpia.c:1687: break statement not within loop or switch cpia.c:1688: case label not within a switch statement cpia.c:1693: break statement not within loop or switch cpia.c:1694: case label not within a switch statement cpia.c:1727: break statement not within loop or switch cpia.c:1728: default label not within a switch statement cpia.c:1729: break statement not within loop or switch cpia.c:1730: warning: control reaches end of non-void function cpia.c: At top level: cpia.c:1731: parse error before `}' cpia.c: In function `fetch_frame': cpia.c:2256: parse error before `else' make: *** [cpia.o] Error 1 ++++++++++++++++++++++++++++++++++++++++++++= ++++++++++++++++++++++++++++++++++++++++++== How do i make the newest driver less noisy ? thanks. Samo Gabrovec ---------------------------------------------------------------- Depart in pieces.... i.e., Split. ---------------------------------------------------------------- Visit http://www.velenje.cx ---------------------------------------------------------------- From tdat@yahoo.com Thu, 23 Mar 2000 15:53:27 -0800 (PST) Date: Thu, 23 Mar 2000 15:53:27 -0800 (PST) From: Sang Y. Yum tdat@yahoo.com Subject: [cpia] new version of cpia-control Peter, I am not a Python programmer. :) cpia-control failed on my machine: [sang@pikatsu cpia-control]$ rpm -q python pygtk python-1.5.2-11ac pygtk-0.6.3-8ac [sang@pikatsu cpia-control]$ ./cpia-control Traceback (innermost last): File "./cpia-control", line 70, in ? camera=libcpia.status() File "./libcpia.py", line 80, in __init__ self.__update() File "./libcpia.py", line 140, in __update self.camera_status_min[key]=m.group(3) File "/usr/lib/python1.5/re.py", line 347, in group raise IndexError, 'group %s is undefined' % `g` IndexError: group 3 is undefined --- Peter Pregler wrote: > Hi all, > > I have released a new version of the control client. > New features are: > > - added support for saving/loading the > camera state > - the GUI now tracks the camera state > - various bug fixes > > It is available at: > http://sourceforge.net/project/?group_id=3159 > > This is close to the final version from my side. If > you want some additional > features step forward now or implement it yourself. > There are a lot of things > in the todo. Do not take that too serious. I am > bored with it. :) > > Have fun, Peter > > ------------------------------- > Even the thought that a ship was waiting to take him > back to Earth > did not wipe out the sense of loss he felt at that > moment. > ------------------------------- > Email: Peter.Pregler@risc.uni-linz.ac.at > Peter Pregler / RISC, University of Linz, Austria > > _______________________________________________ > cpia mailing list - cpia@risc.uni-linz.ac.at > http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia > ===== Sang Y. Yum http://www.yumnet.dyndns.org/~sang San Diego, CA mailto:tdat@yahoo.com __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com From sbertin@mindspring.com Thu, 23 Mar 2000 23:10:03 -0500 (EST) Date: Thu, 23 Mar 2000 23:10:03 -0500 (EST) From: sbertin@mindspring.com sbertin@mindspring.com Subject: [cpia] Debug .. On 24 Mar, Samo Gabrovec wrote: > i used cpia 0.7.1 and in the Makefile i have commented the line > # DEBUG = -D_CPIA_DEBUG_ > compiled and i`ve gor a module which is NOT loud and it works. > today i have dl-ed the 0.7.4 and at first forgot to coment it out, loaded > the modules and i saw that every pic that it takes there`s one line in my > logs. ok i coment out the debug line and tried to re-compile but it wont. > i get an error [errors snipped] > How do i make the newest driver less noisy ? > thanks. Apply this patch, courtesy of George Talusan. Scott J. Bertin sbertin@mindspring.com =================================================================== RCS file: /cvsroot/webcam/cpia/module/cpia.h,v retrieving revision 0.10 retrieving revision 0.11 diff -u -r0.10 -r0.11 --- cpia/module/cpia.h 2000/03/11 21:51:44 0.10 +++ cpia/module/cpia.h 2000/03/12 15:41:29 0.11 @@ -385,7 +385,7 @@ #define ADBG(lineno,fmt,args...) printk(fmt, jiffies, lineno, ##args) #define DBG(fmt,args...) ADBG((__LINE__),KERN_DEBUG __FILE__"(%ld):"__FUNCTION__"(%d):"fmt,##args) #else -#define DBG(fmn,args...) {} +#define DBG(fmn,args...) do {} while(0) #endif #define DEB_BYTE(p)\ From Peter.Pregler@risc.uni-linz.ac.at Fri, 24 Mar 2000 08:31:38 +0100 (CET) Date: Fri, 24 Mar 2000 08:31:38 +0100 (CET) From: Peter Pregler Peter.Pregler@risc.uni-linz.ac.at Subject: [cpia] new version of cpia-control This message is in MIME format --_=XFMail.1.4.4.Linux:20000324083138:650=_ Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Ooops, never ever believe that some program will work. Alyways test it with the actual versions the user will use. I use the cvs-version of the driver for which I changed the proc-output slightly. :( Okay, I have attached a small patch that will fix it for now, just uncomment the offending lines. I will release something better in the evening. Sorry for the fuss, Peter On 23-Mar-2000 Sang Y. Yum wrote: > Peter, >=20 > I am not a Python programmer. :) cpia-control failed > on my machine: >=20 > [sang@pikatsu cpia-control]$ rpm -q python pygtk > python-1.5.2-11ac > pygtk-0.6.3-8ac > [sang@pikatsu cpia-control]$ ./cpia-control > Traceback (innermost last): > File "./cpia-control", line 70, in ? > camera=3Dlibcpia.status() > File "./libcpia.py", line 80, in __init__ > self.__update() > File "./libcpia.py", line 140, in __update > self.camera_status_min[key]=3Dm.group(3) > File "/usr/lib/python1.5/re.py", line 347, in group > raise IndexError, 'group %s is undefined' % `g` > IndexError: group 3 is undefined > >=20 > --- Peter Pregler > wrote: >> Hi all, >>=20 >> I have released a new version of the control client. >> New features are: >>=20 >> - added support for saving/loading the >> camera state >> - the GUI now tracks the camera state >> - various bug fixes >>=20 >> It is available at: >> http://sourceforge.net/project/?group_id=3D3159 >>=20 >> This is close to the final version from my side. If >> you want some additional >> features step forward now or implement it yourself. >> There are a lot of things >> in the todo. Do not take that too serious. I am >> bored with it. :) >>=20 >> Have fun, Peter >>=20 >> ------------------------------- >> Even the thought that a ship was waiting to take him >> back to Earth >> did not wipe out the sense of loss he felt at that >> moment. >> ------------------------------- >> Email: Peter.Pregler@risc.uni-linz.ac.at >> Peter Pregler / RISC, University of Linz, Austria >>=20 >> _______________________________________________ >> cpia mailing list - cpia@risc.uni-linz.ac.at >> > http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia >>=20 >=20 > =3D=3D=3D=3D=3D > Sang Y. Yum http://www.yumnet.dyndns.org/~sang > San Diego, CA mailto:tdat@yahoo.com >=20 > __________________________________________________ > Do You Yahoo!? > Talk to your friends online with Yahoo! Messenger. > http://im.yahoo.com ------------------------------- Email: Peter.Pregler@risc.uni-linz.ac.at WWW: http://www.risc.uni-linz.ac.at/people/ppregler --_=XFMail.1.4.4.Linux:20000324083138:650=_ Content-Disposition: attachment; filename="cpia-control.0.3.patch" Content-Description: cpia-control.0.3.patch Content-Type: text/plain; charset=iso-8859-1; name=cpia-control.0.3.patch; SizeOnDisk=770 Content-Transfer-Encoding: 7bit --- libcpia.py Fri Mar 24 08:23:59 2000 +++ libcpia.py.bad Fri Mar 24 08:25:12 2000 @@ -137,9 +137,9 @@ except KeyError: self.camera_status_changed[key]=0 self.camera_status[key]=m.group(2) - #self.camera_status_min[key]=m.group(3) - #self.camera_status_max[key]=m.group(4) - #self.camera_status_default[key]=m.group(5) + self.camera_status_min[key]=m.group(3) + self.camera_status_max[key]=m.group(4) + self.camera_status_default[key]=m.group(5) else: if key=='V4L Driver version': match_string=\ --_=XFMail.1.4.4.Linux:20000324083138:650=_-- End of MIME message From jerdfelt@sventech.com Fri, 24 Mar 2000 14:05:11 -0500 Date: Fri, 24 Mar 2000 14:05:11 -0500 From: Johannes Erdfelt jerdfelt@sventech.com Subject: [cpia] Merging new cpia driver into 2.3? I think everyone wants it to be done, but it has occured yet. Does anyone have any objections to me making the patch and submitting it to Linus (or the appropriate parties) to get it merged into 2.3 before 2.4 is released? I'm working on a patch now. JE From Peter.Pregler@risc.uni-linz.ac.at Fri, 24 Mar 2000 20:48:21 +0100 (CET) Date: Fri, 24 Mar 2000 20:48:21 +0100 (CET) From: Peter Pregler Peter.Pregler@risc.uni-linz.ac.at Subject: [cpia] Merging new cpia driver into 2.3? On 24-Mar-2000 Johannes Erdfelt wrote: > I think everyone wants it to be done, but it has occured yet. Does > anyone have any objections to me making the patch and submitting it to > Linus (or the appropriate parties) to get it merged into 2.3 before 2.4 > is released? You get a big thanx for the work from my side. :) But please use the CVS at sourceforge (there are some minor but important fixes). I have also written a short Documentation-file for the 2.2.x patch I sent to Alan. It might be a good idea to include it. I will update the parport stuff in it and send it to you. -Peter ------------------------------- Even the thought that a ship was waiting to take him back to Earth did not wipe out the sense of loss he felt at that moment. ------------------------------- Email: Peter.Pregler@risc.uni-linz.ac.at Peter Pregler / RISC, University of Linz, Austria From jerdfelt@sventech.com Fri, 24 Mar 2000 15:20:42 -0500 Date: Fri, 24 Mar 2000 15:20:42 -0500 From: Johannes Erdfelt jerdfelt@sventech.com Subject: [cpia] Merging new cpia driver into 2.3? On Fri, Mar 24, 2000, Peter Pregler wrote: > > On 24-Mar-2000 Johannes Erdfelt wrote: > > I think everyone wants it to be done, but it has occured yet. Does > > anyone have any objections to me making the patch and submitting it to > > Linus (or the appropriate parties) to get it merged into 2.3 before 2.4 > > is released? > > You get a big thanx for the work from my side. :) But please use the CVS at > sourceforge (there are some minor but important fixes). I have also written a > short Documentation-file for the 2.2.x patch I sent to Alan. It might be a good > idea to include it. I will update the parport stuff in it and send it to you. Already done. I have a patch whipped up that I was about to send off, but I can wait until you send the documentation. JE From jerdfelt@valinux.com Sat, 25 Mar 2000 08:41:56 -0800 Date: Sat, 25 Mar 2000 08:41:56 -0800 From: Johannes Erdfelt jerdfelt@valinux.com Subject: [cpia] Re: new cpia driver and camstream (fwd) Just when you thought you were safe. BTW - I submitted a 2.3 patch, Alan took it and submitted it to Linus. JE ----- Forwarded message from Alan Cox ----- Subject: Re: new cpia driver and camstream To: nemosoft@smcc.demon.nl (Nemosoft Unv.) Date: Sat, 25 Mar 2000 14:15:05 +0000 (GMT) Cc: randy.dunlap@intel.com (Dunlap Randy), jerdfelt@valinux.com (Johannes Erdfelt), alan@lxorguk.ukuu.org.uk (Alan Cox), linux-usb@suse.com (linux-usb@suse.com) X-Mailer: ELM [version 2.5 PL1] From: Alan Cox > What's the case? The new CPiA driver takes into account whether the image is > being requested through read() or mmap(). With read() it now returns a RGB > palette, and with mmap() BGR. However, the ibmcam, ov511 and my Philips > drivers always return BGR (my drivers don't have mmap() yet, but that shall > use BGR too). The read case is broken. > c-qcam | RGB (5)| - | - | - | This one is wrong. As is the pms. > "standard", which is mainly "broken" because the grabber cards seem to prefer > BGR format (fortunately, they all use the same format!). And some drivers > changed from RGB to BGR at some point in their development. Its actually basically endianness accident I think. > My suggestion is to stick to BGR format, ditch RGB, and try to get "illegal" > formats out (like the Zoran 36120 which always returns BGR format with read, > even if you had set VIDEO_PALETTE_RGB32). An invalid format request should error I guess. We never quite decided if it should error or offer you the next nearest. Error probably. We should stick with BGR. This hasnt really come up before because TV overlay doesn't care and hardcore capture and process freaks all use YUVspace Alan ----- End forwarded message ----- From nicolas.roussel@gmd.de Sun, 26 Mar 2000 13:38:44 +0200 (CEST) Date: Sun, 26 Mar 2000 13:38:44 +0200 (CEST) From: Nicolas Roussel nicolas.roussel@gmd.de Subject: [cpia] Re: new cpia driver and camstream (fwd) Talking about the RGB/BGR issue, Alan suggested: > We should stick with BGR. This hasnt really come up before because > TV overlay doesn't care and hardcore capture and process freaks all > use YUVspace Many video hardware can't produce RGB or BGR data directly, so drivers usually have to convert from the "native" format (YUV or something else). By supporting only BGR, you force anyone who wants or needs RGB to convert once more between different formats. > Its actually basically endianness accident I think. Well, I think something described as RGB24 in the API should really be seen by the application as three bytes R-G-B, no matter the endianness of the underlying system. I think we should just add a few constants to videodev.h to fix this once for all. Simply adding VIDEO_PALETTE_BGR24 to the existing VIDEO_PALETTE_RGB24 would make a clear difference between the two formats and all existing applications and drivers would still work, provided that they now choose the right format name. User-space code should be used to convert from what the driver can produce to what the application wants. But this can work efficiently only if the drivers are not already performing some conversion. Ideally, they should be able to send "native" data to the application in order to minimize the number of conversions. Maybe we could have a VIDEO_PALETTE_NATIVE format that could be used with VID_HARDWARE_* to allow fast user-space coding conversions? Nicolas P.S.: I also think an invalid format request should error. TV-like applications can display RGB data even if it is BGR encoded because we are the final destination of the images and we can understand them even if people look like martians. Image processing applications are usually not that smart. Chromakeying on the wrong format will never work, so the next nearest format is not an option. -- ________________________________________________________________________ Nicolas Roussel mailto:nicolas.roussel@gmd.de GMD - FIT.HCI, Schloss Birlinghoven http://www-ihm.lri.fr/~roussel/ 53754 St. Augustin, Germany phone: +49 2241 14-2154 / fax: 14-2065 ________________________________________________________________________ From alan@redhat.com Sun, 26 Mar 2000 09:37:48 -0500 (EST) Date: Sun, 26 Mar 2000 09:37:48 -0500 (EST) From: Alan Cox alan@redhat.com Subject: [cpia] Re: new cpia driver and camstream (fwd) > Many video hardware can't produce RGB or BGR data directly, so drivers > usually have to convert from the "native" format (YUV or something > else). By supporting only BGR, you force anyone who wants or needs RGB > to convert once more between different formats. Drivers should never be converting formats. All the known YUV format are defined. When given an unsupported format a driver should error it. > usually not that smart. Chromakeying on the wrong format will never > work, so the next nearest format is not an option. Indeed From jmbuena@isys.dia.fi.upm.es Wed, 29 Mar 2000 17:56:50 +0200 Date: Wed, 29 Mar 2000 17:56:50 +0200 From: Jose Miguel Buenaposada Biencinto jmbuena@isys.dia.fi.upm.es Subject: [cpia] 2.2.14 & USB 2.3.50 Backport Hi , Does anybody got working propertly the USB cpia driver with kernel 2.2.14 and the USB 2.3.50 patch backport ? I have applied this patch and the Linux1394 patch to 2.2.14 kernel. [root@hal jmbuena]# cat /proc/version Linux version 2.2.14 (root@hal) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #4 SMP Wed Mar 29 15:19:52 CEST 2000 [root@hal jmbuena]# /sbin/lsmod Module Size Used by cpia 11748 0 (unused) usb-uhci 17736 0 (unused) usbcore 26468 0 [cpia usb-uhci] es1371 27904 0 soundcore 3012 4 [es1371] I got this with the cpia_usb module: [root@hal log]# /sbin/modprobe cpia_usb /lib/modules/2.2.14/misc/cpia_usb.o: unresolved symbol cpia_unregister_camera /lib/modules/2.2.14/misc/cpia_usb.o: unresolved symbol cpia_register_camera /lib/modules/2.2.14/misc/cpia_usb.o: insmod /lib/modules/2.2.14/misc/cpia_usb.o failed /lib/modules/2.2.14/misc/cpia_usb.o: insmod cpia_usb failed Any idea ? I can work with the driver with kernel 2.3.51 but I can't get network interface working good enougth. -- ------------------------------------------------------------------- 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 tadavis@lbl.gov Wed, 29 Mar 2000 09:22:17 -0800 Date: Wed, 29 Mar 2000 09:22:17 -0800 From: Thomas Davis tadavis@lbl.gov Subject: [cpia] 2.2.14 & USB 2.3.50 Backport Jose Miguel Buenaposada Biencinto wrote: > > Hi , > > Does anybody got working propertly the USB cpia driver with > kernel 2.2.14 and the USB 2.3.50 patch backport ? I have applied this > patch and the Linux1394 patch to 2.2.14 kernel. > It works fine here. > I got this with the cpia_usb module: > > [root@hal log]# /sbin/modprobe cpia_usb > /lib/modules/2.2.14/misc/cpia_usb.o: unresolved symbol > cpia_unregister_camera > /lib/modules/2.2.14/misc/cpia_usb.o: unresolved symbol > cpia_register_camera > /lib/modules/2.2.14/misc/cpia_usb.o: insmod > /lib/modules/2.2.14/misc/cpia_usb.o failed > /lib/modules/2.2.14/misc/cpia_usb.o: insmod cpia_usb failed > > Any idea ? > did you do a '/sbin/depmod -a' first? Also, make sure you don't install the usb's backport cpia.. it will muck you up! (ie, go to where you got the source for cpia, and do another install) -- ------------------------+-------------------------------------------------- Thomas Davis | PDSF Project Leader tadavis@lbl.gov | (510) 486-4524 | "Only a petabyte of data this year?" From jmbuena@isys.dia.fi.upm.es Thu, 30 Mar 2000 12:58:45 +0200 Date: Thu, 30 Mar 2000 12:58:45 +0200 From: Jose Miguel Buenaposada Biencinto jmbuena@isys.dia.fi.upm.es Subject: [cpia] 2.2.14 & USB 2.3.50 Backport This is a multi-part message in MIME format. --Boundary_(ID_yuE1ENaIXQTSKlbV0ot+xw) Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT Hi ! I hope somebody can help me. I still have problems with the USB 2.3.50 backport to 2.2.14 and cpia 0.7.4. I have installed again a fresh copy of the cpia-0.7.4 and a fresh copy of kernel 2.2.14 without the Linux1394 path. ¿ Can anyone send me a valid /usr/src/linux-2.2.14/.config file with working options ? I'm a bit confused. I can load de modules: [root@hal linux]# /sbin/lsmod Module Size Used by cpia_usb 4772 0 (unused) cpia 49028 0 [cpia_usb] But I get non defined symbols with the depmod command. I attach the result of /sbin/depmod -ae Also I get: [root@hal module]# /home/bin/gqcam /dev/video: No such device [root@hal module]# ls -l /dev/video* lrwxrwxrwx 1 root root 6 Mar 9 14:10 /dev/video -> video0 crw------- 1 jmbuena root 81, 0 Sep 21 1999 /dev/video0 crw------- 1 jmbuena root 81, 1 Sep 21 1999 /dev/video1 crw------- 1 jmbuena root 81, 2 Sep 21 1999 /dev/video2 In /var/log/messages: Mar 30 12:49:07 hal modprobe: modprobe: Can't locate module char-major-81-0 ls Is because the cpia and cpia_usb modules are not installed correctly in the kernel ? Or is because is not the correct version of video4linux (I compile it into the kernel with the usb and usb-uhci support) ? In addition in /var/log/messages when I connect the zoomcam usb appears: Mar 30 12:48:47 hal kernel: usb.c: USB new device connect, assigned device number 2 Mar 30 12:48:50 hal kernel: usb_control/bulk_msg: timeout Mar 30 12:49:02 hal last message repeated 4 times Mar 30 12:49:02 hal kernel: usb.c: USB device not responding, giving up (error=-110) Maybe a usb problem ? Again thanks a lot for your time. -- ------------------------------------------------------------------- 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 ------------------------------------------------------------------- --Boundary_(ID_yuE1ENaIXQTSKlbV0ot+xw) Content-type: text/plain; charset=us-ascii; name=m Content-disposition: inline; filename=m Content-Transfer-Encoding: 7BIT depmod: *** Unresolved symbols in /lib/modules/2.2.14/misc/cpia.o depmod: remap_page_range depmod: schedule_timeout depmod: schedule depmod: kmalloc depmod: _ctype depmod: create_proc_entry depmod: vfree depmod: video_register_device depmod: video_unregister_device depmod: request_module depmod: kfree depmod: vmalloc depmod: remove_proc_entry depmod: mem_map depmod: simple_strtoul depmod: sprintf depmod: jiffies depmod: printk depmod: __generic_copy_to_user depmod: *** Unresolved symbols in /lib/modules/2.2.14/misc/cpia_usb.o depmod: __wake_up depmod: kmalloc depmod: vfree depmod: usb_deregister depmod: usb_free_urb depmod: usb_alloc_urb depmod: usb_register depmod: interruptible_sleep_on depmod: kfree depmod: vmalloc depmod: usb_submit_urb depmod: usb_driver_release_interface depmod: usb_control_msg depmod: printk depmod: usb_set_interface depmod: usb_unlink_urb depmod: *** Unresolved symbols in /lib/modules/default/misc/cpia.o depmod: remap_page_range depmod: schedule_timeout depmod: schedule depmod: kmalloc depmod: _ctype depmod: create_proc_entry depmod: vfree depmod: video_register_device depmod: video_unregister_device depmod: request_module depmod: kfree depmod: vmalloc depmod: remove_proc_entry depmod: mem_map depmod: simple_strtoul depmod: sprintf depmod: jiffies depmod: printk depmod: __generic_copy_to_user depmod: *** Unresolved symbols in /lib/modules/default/misc/cpia_usb.o depmod: __wake_up depmod: kmalloc depmod: vfree depmod: usb_deregister depmod: usb_free_urb depmod: usb_alloc_urb depmod: usb_register depmod: interruptible_sleep_on depmod: kfree depmod: vmalloc depmod: usb_submit_urb depmod: usb_driver_release_interface depmod: usb_control_msg depmod: printk depmod: usb_set_interface depmod: usb_unlink_urb --Boundary_(ID_yuE1ENaIXQTSKlbV0ot+xw)--