From root@velenje.cx 01 Sep 2000 09:48:03 CEST
Date: 01 Sep 2000 09:48:03 CEST
From: Samo Gabrovec root@velenje.cx
Subject: [cpia] 2.4.0.test7 cpia-1.1 compile problem..

Hi.
I was using webcam II pp for a long time, since i got troubles with the cable i
decided to buy a new one.
And peter said that a Trustc@m Lite works so i bought that one. 
Now there`s a liitle change and the change is USB. I have downloaded the
2.4.0.test7 kernel, and i also removed the
# in the make file of cpia so that USB module will be compiled too.
but it doesn`t . as i can see it didn`t came even through the cpia.c . On
2.2.16 it did compile. What should i do?
Which version of cpia is in the 2.4 kernel ? (there were options but in the
cpia readme i read that i shouldn`t include them)
Please help.


Samo Gabrovec
--------
gekko:/download/cpia-1.1/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 -DCONFIG_VIDEO_CPIA_USB_MODULE cpia.c
cpia.c: In function `uvirt_to_kva':
cpia.c:272: invalid operands to binary |
cpia.c: In function `rvmalloc':
cpia.c:313: warning: implicit declaration of function `MAP_NR'
cpia.c:313: invalid type argument of `->'
cpia.c: In function `rvfree':
cpia.c:341: invalid type argument of `->'
make: *** [cpia.o] Error 1
gekko:/download/cpia-1.1/module #	   
------------


-- 
----------------------------------------------------------------
visit http://www.velenje.cx
----------------------------------------------------------------

In /dev/null no one can hear you scream...
----------------------------------------------------------------





From robert@work.vc-graz.ac.at Fri, 1 Sep 2000 11:22:55 +0200 (CEST)
Date: Fri, 1 Sep 2000 11:22:55 +0200 (CEST)
From: Robert Ladstaetter robert@work.vc-graz.ac.at
Subject: [cpia] problems with intel playcam

hi,

i've successfully installed the terracam usb webcam, and after that I wanted
to do the same with the intel playcam (me2cam, which is said to be supported
too by the cpia driver); 

kernel: 2.3.99pre9

everything loads ok, but in

/var/log/messages i get:

Aug 31 11:49:16 dmt kernel: usb.c: USB new device connect, assigned device
number 2
Aug 31 11:49:16 dmt kernel: usb.c: kmalloc IF c5b78ec0, numif 1  
Aug 31 11:49:16 dmt kernel: usb.c: new device strings: Mfr=0, Product=0,
SerialNumber=0
Aug 31 11:49:16 dmt kernel: usb.c: unhandled interfaces on device
Aug 31 11:49:16 dmt kernel: usb.c: This device is not recognized by any
installed USB driver.

<this line doesn't sound all too good, then I get more stuff like:>

Aug 31 11:49:16 dmt kernel:   Length              = 18
Aug 31 11:49:16 dmt kernel:   DescriptorType      = 01
Aug 31 11:49:16 dmt kernel:   USB version         = 1.00
Aug 31 11:49:16 dmt kernel:   Vendor:Product      = 0813:0002
Aug 31 11:49:16 dmt kernel:   MaxPacketSize0      = 8
Aug 31 11:49:16 dmt kernel:   NumConfigurations   = 1 
Aug 31 11:49:16 dmt kernel:   Device version      = 1.00  
Aug 31 11:49:16 dmt kernel:   Device Class:SubClass:Protocol = 00:00:00 
Aug 31 11:49:16 dmt kernel:     Per-interface classes 

[....] (about 100 lines)

if I load usbcore, videodev, cpia and cpia_usb the directory /proc/cpia 
exists, but is empty (?). if I make a 'cat /dev/video' everything I get is an
'Unknown Device/Device doesn't exist'. Unfortunately in the docs the only
thing which relates to this problem is the line: 'everything should be detected
automatically'. Well, that obviously isn't the case. ;-). 

I suspekt that the camera doesn't function, but maybe this is a common problem
with an easy solution. *crosses his fingers*

the terracam worked right out of the box, but on another machine I right now
don't have access to. (very unfortunate ;-)

greetings from austria,

robert

-- 
mfG 
Ladstaetter Robert              mailto:ladi@sbox.tu-graz.ac.at






From tdat@yahoo.com Fri, 1 Sep 2000 10:45:36 -0700 (PDT)
Date: Fri, 1 Sep 2000 10:45:36 -0700 (PDT)
From: Sang Y. Yum tdat@yahoo.com
Subject: [cpia] Creative WebCam II on Debian woody

I was successfully using this camera on my machine
when it was running RedHat 6.1.

Now that I switched to Debian Woody and I'm having difficulties.

Kernel: custom-built 2.2.16
CPiA driver: cpia-1.1
Camera: Creative WebCam II Parallel version

When I load cpia module, the machine freezes solid and has to be reset.
No error message I could retrieve.

Any idea?

Sang


=====
Sang Y. Yum             http://www.yumnet.dyndns.org/~sang
San Diego, CA           mailto:tdat@yahoo.com

__________________________________________________
Do You Yahoo!?
Yahoo! Mail - Free email you can access from anywhere!
http://mail.yahoo.com/




From tobias@ing.ens.uabc.mx Sat, 2 Sep 2000 14:09:57 -0700
Date: Sat, 2 Sep 2000 14:09:57 -0700
From: Tobias Gogolin tobias@ing.ens.uabc.mx
Subject: [cpia] V4L faq ?

Questions:

Is there a tool that any of you developers have
that could shed some light on the status and availability of the V4L
interface ports
such as:
- availability
- size
- update frequency
- PortName : how exactly a client would have to refer to the port
- Are any clients accessing the ports

Are there any possibilities to 'massage' ports into certain shapes to comply
to clients expectations ?
For example I am investigating the possibility to use Real producer as a
client
and it seems justly they focused on v4l produced from Frame Grabbers

Point me to all the resources that are already available to understand these
issues
And or lets compile further tools and info resources to evolve the
technology

My vision is a more communicative methodology to hook components via
interfaces together
and taking out the uncertainty and guesswork with visual status monitors for
components and interfaces

Is this to much to ask ?

cheers

Tobias







From mfreytes@gtwing.efn.uncor.edu Mon, 4 Sep 2000 00:40:47 -0300 (ART)
Date: Mon, 4 Sep 2000 00:40:47 -0300 (ART)
From: Matias Freytes mfreytes@gtwing.efn.uncor.edu
Subject: [cpia] usb webcam

Hello,
	My name is Matias and I´m working on video conferencing (QCIF and
CIF sizes) applications at the Laboratorio de Comunicaciones Digitales,
Universidad Nacional de Cordoba, Argentina. So far, I´ve been working with
bttv848 frame grabbers (using V4L2, www.thedirks.org) with very nice
results, but I need to put a camera to a laptop. My guess is USB should be
the best choice and I´ve read about your CPiA driver. Questions are:

	*. Is Creative´s Webcam II a good option?
	*. Is your driver a V4L2 driver or a V4L driver?
	*. Are there any V4L2 ports of the driver? I got used to V4L2.

Thank you very much
Matias.

PS: please cc, I´m not subscribed to the list.





From mfreytes@gtwing.efn.uncor.edu Mon, 4 Sep 2000 00:50:12 -0300 (ART)
Date: Mon, 4 Sep 2000 00:50:12 -0300 (ART)
From: Matias Freytes mfreytes@gtwing.efn.uncor.edu
Subject: [cpia] more on usb webcam

Hello again,
	I forgot to ask about the frame format. Is it any YUV format,
like YUV420, YUV 411, ...?

--------------
Matias Freytes
Laboratorio de Comunicaciones Digitales
Universidad Nacional de Cordoba
Argentina







From Peter_Pregler@email.com Mon, 4 Sep 2000 11:31:11 +0200
Date: Mon, 4 Sep 2000 11:31:11 +0200
From: Peter Pregler Peter_Pregler@email.com
Subject: [cpia] usb webcam

On Mon, Sep 04, 2000 at 12:40:47AM -0300, Matias Freytes wrote:
> 	My name is Matias and I´m working on video conferencing (QCIF and
> CIF sizes) applications at the Laboratorio de Comunicaciones Digitales,
> Universidad Nacional de Cordoba, Argentina. So far, I´ve been working with
> bttv848 frame grabbers (using V4L2, www.thedirks.org) with very nice
> results, but I need to put a camera to a laptop. My guess is USB should be
> the best choice and I´ve read about your CPiA driver. Questions are:
> 
> 	*. Is Creative´s Webcam II a good option?

I think from the basic electrical specifications all the cpia-based
cameras are the same since almost all the electronics is already on
the cpia-chip. What is different is the optics. I have a Creative WC
II (parport) and a USB SpaceC@m lite. IMHO the picture quality of the
WCII is better. I do not know about the quality of other cameras.

> 	*. Is your driver a V4L2 driver or a V4L driver?

It is v4l only.

> 	*. Are there any V4L2 ports of the driver? I got used to V4L2.

Feel free to write the v4l2 api. It is definitly not very complicated
since you can use the v4l-stuff. And it should not be _that_ much
work. ;) Personally I did not write it because I have no need for it and
it is IMHO pretty boring to write another slightly different api. Also
the future of v4l(2) is not clear to me.

-Peter

-- 
I will not waste chalk. --Bart Simpson at the blackboard
--------------------------------------------------------
Email: Peter_Pregler@email.com
WWW:   http://www.risc.uni-linz.ac.at/people/ppregler
ICQ:   61011460




From Peter_Pregler@email.com Mon, 4 Sep 2000 11:34:04 +0200
Date: Mon, 4 Sep 2000 11:34:04 +0200
From: Peter Pregler Peter_Pregler@email.com
Subject: [cpia] more on usb webcam

On Mon, Sep 04, 2000 at 12:50:12AM -0300, Matias Freytes wrote:
> Hello again,
> 	I forgot to ask about the frame format. Is it any YUV format,
> like YUV420, YUV 411, ...?

See the cpia-developers guide for what the camera can do in
hardware. See the v4l-api (I have no idea anymore if there was a query
or if you have to do trial an error) resp. the driver source (cpia.c)
for what is supported right now.

-Peter

-- 
I will not waste chalk. --Bart Simpson at the blackboard
--------------------------------------------------------
Email: Peter_Pregler@email.com
WWW:   http://www.risc.uni-linz.ac.at/people/ppregler
ICQ:   61011460




From Peter_Pregler@email.com Mon, 4 Sep 2000 11:39:35 +0200
Date: Mon, 4 Sep 2000 11:39:35 +0200
From: Peter Pregler Peter_Pregler@email.com
Subject: [cpia] problems with intel playcam

On Fri, Sep 01, 2000 at 11:22:55AM +0200, Robert Ladstaetter wrote:
> Aug 31 11:49:16 dmt kernel: usb.c: This device is not recognized by any
> installed USB driver.
> 
> <this line doesn't sound all too good, then I get more stuff like:>

Not good but the truth. ;)

> Aug 31 11:49:16 dmt kernel:   Length              = 18
> Aug 31 11:49:16 dmt kernel:   DescriptorType      = 01
> Aug 31 11:49:16 dmt kernel:   USB version         = 1.00
> Aug 31 11:49:16 dmt kernel:   Vendor:Product      = 0813:0002

The 0813:0001 is supported. I have no idea what the 0813:0002 is.
Change the 0x0001 to 0x0002 in the following paragraph in cpia_usb.c
and try out what happens:

        /* Is it a CPiA? */
        if (!((udev->descriptor.idVendor == 0x0553 && 
             udev->descriptor.idProduct == 0x0002) ||
            (udev->descriptor.idVendor == 0x0813 &&
             udev->descriptor.idProduct == 0x0001))) /* GA 04/14/00 */
          return NULL;

> greetings from austria,

Same country here. ;)

-Peter

-- 
I will not waste chalk. --Bart Simpson at the blackboard
--------------------------------------------------------
Email: Peter_Pregler@email.com
WWW:   http://www.risc.uni-linz.ac.at/people/ppregler
ICQ:   61011460




From Peter_Pregler@email.com Mon, 4 Sep 2000 11:47:28 +0200
Date: Mon, 4 Sep 2000 11:47:28 +0200
From: Peter Pregler Peter_Pregler@email.com
Subject: [cpia] V4L faq ?

Hi,

Best ask your questions again on the v4l-linux list. See
http://roadrunner.swansea.uk.linux.org/v4l.shtml for how to subscribe.

-Peter

On Sat, Sep 02, 2000 at 02:09:57PM -0700, Tobias Gogolin wrote:
> Questions:
> 
> Is there a tool that any of you developers have
> that could shed some light on the status and availability of the V4L
> interface ports
> such as:
> - availability
> - size
> - update frequency
> - PortName : how exactly a client would have to refer to the port
> - Are any clients accessing the ports
> 
> Are there any possibilities to 'massage' ports into certain shapes
> to comply to clients expectations ?  For example I am investigating
> the possibility to use Real producer as a client and it seems justly
> they focused on v4l produced from Frame Grabbers
> 
> Point me to all the resources that are already available to
> understand these issues And or lets compile further tools and info
> resources to evolve the technology
> 
> My vision is a more communicative methodology to hook components via
> interfaces together and taking out the uncertainty and guesswork
> with visual status monitors for components and interfaces
> 
> Is this to much to ask ?
> 
> cheers
> 
> Tobias
> 
> 
> 
> 
> _______________________________________________
> cpia mailing list  -  cpia@risc.uni-linz.ac.at
> http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia
> 

-- 
I will not waste chalk. --Bart Simpson at the blackboard
--------------------------------------------------------
Email: Peter_Pregler@email.com
WWW:   http://www.risc.uni-linz.ac.at/people/ppregler
ICQ:   61011460




From kopecjc@att.net Mon, 04 Sep 2000 10:00:28 -0400
Date: Mon, 04 Sep 2000 10:00:28 -0400
From: Joseph C. Kopec kopecjc@att.net
Subject: [cpia] aiptek webcam works -- think its ov511

My experience with the USB Aiptek HyperVcam Fun is that it is an ov511
device.  I am running version 2.4.0-test7 on Intel.  I have compiled
into the kernel both the CPiA (Version 1.20 (2.10)) and the ov511
(Version 1.20) drivers. When I use an Ezonics EZCam USB, the camera is
detected as a USB CPiA camera.  When I use an Aiptek HyperVcam Fun USB
camera, the camera is detected as USB OV511 camera.  Each camera works
using gqcam -- I haven't worked on trying to get them both running at
the same time however.  Additionally, the colors in the Aiptek run very
purplish-blue in indoor light.  I am in the U.S. -- perhaps the Aiptek
distributed here differs somewhat from that distributed in Europe.

For more information on ov511, see http://alpha.dyndns.org/ov511/

Ries van Twisk wrote:
> 
> I Folks,
> 
> I just wanted top tell you that the 'webcam HyperVcam Fun' is supported
> using the Cpia driver (0553:0002).
> You can find more information on this webcam on www.aiptek.de
> 
> This is tested in a 2.2.16 kernel with the USB patch.
> 
> Only one minor thing is that i sometimes get a VIDIOCGFBUF ioctl error.
> It looks like this has something to do with the 'v4lctl/v4l-conf'
> programs. I'm currently digging into this.... I'm using Debian Potato distro.
> 
> Since I'm not on this list you should repy me to rvt@dds.nl
> 
> Regards,
> Ries van Twisk
> rvt@dds.nl
> 
> _______________________________________________
> cpia mailing list  -  cpia@risc.uni-linz.ac.at
> http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia




From mwm@i.am Tue, 05 Sep 2000 02:36:11 -0700
Date: Tue, 05 Sep 2000 02:36:11 -0700
From: Mark W. McClelland mwm@i.am
Subject: [cpia] aiptek webcam works -- think its ov511

It is possible that there are two revisions of the camera, one a CPiA
and one an OV511. I have seen this with other cameras. 

The ov511 driver's data rate can be decreased by increasing the "cams"
parameter. This should allow simultaneous use of another camera, as long
as its driver has a similar data-rate reduction feature. I'm not sure if
cpia does.

The color balance of ov511 cameras can vary between models, and the type
of lighting (flourescent, daylight, etc...) makes a huge difference. If
you want, you can send me a frame grab so I can see if there is a
problem with support for that particular camera.

"Joseph C. Kopec" wrote:
> 
> My experience with the USB Aiptek HyperVcam Fun is that it is an ov511
> device.  I am running version 2.4.0-test7 on Intel.  I have compiled
> into the kernel both the CPiA (Version 1.20 (2.10)) and the ov511
> (Version 1.20) drivers. When I use an Ezonics EZCam USB, the camera is
> detected as a USB CPiA camera.  When I use an Aiptek HyperVcam Fun USB
> camera, the camera is detected as USB OV511 camera.  Each camera works
> using gqcam -- I haven't worked on trying to get them both running at
> the same time however.  Additionally, the colors in the Aiptek run very
> purplish-blue in indoor light.  I am in the U.S. -- perhaps the Aiptek
> distributed here differs somewhat from that distributed in Europe.
> 
> For more information on ov511, see http://alpha.dyndns.org/ov511/

-- 
Mark McClelland
http://alpha.dyndns.org/ov511/
mwm@i.am




From vlothuizen@fel.tno.nl Tue, 05 Sep 2000 12:45:09 +0200
Date: Tue, 05 Sep 2000 12:45:09 +0200
From: WJ Vlothuizen vlothuizen@fel.tno.nl
Subject: [cpia] Re: 2 cameras streaming at once?

I (try to) use 2 USB CPiA cameras at once. My current setup is:
- kernel 2.3.49
- cpia-1.1 using usb (ohci), with a patch to parse_picture() that speeds
up processing (at the cost of readability :-)
- client using mmap/VIDIOCMCAPTURE/VIDIOCSYNC at about 5 pictures/s

I can basically use 2 camera's, but occasionally commands fail with
retval -110 (timed out) or -32 (USB_ST_STALL), which does not seem to
harm the capturing. After several minutes I get a message:

  hub.c: already running port 1 disabled by hub (EMI?), re-enabling
  usb.c: USB disconnect on device 2

after which things fail (Expectedly, because the camera will be reset).
Things seem to get somewhat better when I remove the non-essential
do_commands() from fetch_frame(), so the problem seems to be
traffic-related.

While looking through the source of cpia.c I got the impression that the
driver will not really perform double buffering in the sense that one
buffer is filled in the background while the other is 'used' by the
client. Am I right, and would such behaviour be required/wanted by
video4linux?

Regards,
Wouter Vlothuizen




From Peter_Pregler@email.com Sat, 9 Sep 2000 12:18:51 +0200
Date: Sat, 9 Sep 2000 12:18:51 +0200
From: Peter Pregler Peter_Pregler@email.com
Subject: [cpia] Re: 2 cameras streaming at once?

On Tue, Sep 05, 2000 at 12:45:09PM +0200, WJ Vlothuizen wrote:
> 
> While looking through the source of cpia.c I got the impression that the
> driver will not really perform double buffering in the sense that one
> buffer is filled in the background while the other is 'used' by the
> client. Am I right, and would such behaviour be required/wanted by
> video4linux?

Sorry for the late reply. Your impression is correct. I wrote the
v4l-layer with a single parport camera. With the 2.2. parport-driver I
could never get the interrupt-handling correct that you need to
implement streaming camera driven capturing. This might work with the
cleaner 2.4 parport driver.

Also due my limited time I wanted to devote to this and non-existing
kernel-knowlege on my side things became unstable on SMP-machines. So I
fell back to a synchronous polling scheme which works resonable well in
all cases for a single camera on a fast enough machine. You basically
have to rewrite fetch_frame/capture_frame in cpia.c to switch to an
interrupt-drive scheme. The hooks for the interrupt-routines should be
there in cpai_usb.c and cpia_pp.c. As for the first one I have no idea
if the interrupts are generated correctly. As for the second I am
almost sure that it needs quite some debugging.

Now your question: is this really necessary? I have a parport and a
usb-camera right now. On PIII-350 I get no visible performance
degradation if I have gqcam open with both. So I guess unless you don't
want to do serious video-capturing on a smp-machine streaming will not
gain you that much. But who wants to do that with a bunch of
CPiA-cameras anyway? In short right now it is a desktop driver for a
desktop camera.

I will get some usb-cameras in a few weeks. Until I do have the
hardware to test I don't want to dig into the two-usb cameras driver
problem.

Greetings,  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@email.com




From bas@brijn.nu Sat, 09 Sep 2000 15:00:32 +0200
Date: Sat, 09 Sep 2000 15:00:32 +0200
From: Bas Rijniersce bas@brijn.nu
Subject: [cpia] Cheetah Video Daemon

Hi,

Did anybody get the CVD to work with a Creative Webcam II, parport?

TIA,
Bas




From kopecjc@att.net Sun, 10 Sep 2000 03:02:14 -0400
Date: Sun, 10 Sep 2000 03:02:14 -0400
From: Joseph C. Kopec kopecjc@att.net
Subject: [cpia] AAiptek HyperVCam Fun and gqcam:  RGB/BGR Swap

As mentioned earlier, I got an Aiptek HyperVCam Fun USB webcam to work
using the ov511 module (not cpia) and gqcam.  Another poster to cpia
reported that the Aiptek worked with cpia -- perhaps there are different
versions of the Aiptek camera.  The blueish skin coloration I reported
was due to an RGB/BRG inversion -- using the -s switch in gqcam fixed
this and the image quality is now quite good.




From vlothuizen@fel.tno.nl Tue, 12 Sep 2000 11:06:04 +0200
Date: Tue, 12 Sep 2000 11:06:04 +0200
From: WJ Vlothuizen vlothuizen@fel.tno.nl
Subject: [cpia] Re: 2 cameras streaming at once?

> Now your question: is this really necessary? I have a parport and a
> usb-camera right now. On PIII-350 I get no visible performance
> degradation if I have gqcam open with both. So I guess unless you don't
> want to do serious video-capturing on a smp-machine streaming will not
> gain you that much. But who wants to do that with a bunch of
> CPiA-cameras anyway? In short right now it is a desktop driver for a
> desktop camera.

The reason why I would favor streaming and double buffering is that I
use the camera's to provide vision for a robot, where I want a high
update rate and every bit of performance counts. I entirely agree with
you that this is not the way most people will use these cameras. Instead
of a interrupt driven scheme I would envision the use of a kernel thread
that works when incoming data and an outgoing buffer are available, and
otherwise goes to sleep.
Further experiments on my side show that the driver *always* fails after
a hub disconnect. I don't know whether the CPiA-driver could sense such
a disconnect and reinitialize the camera, but the disconnect should not
be there in the first place. After some reading on www.usb.org I removed
the EMI-control components on the USB formcard: this clearly improved
the results, but the problem still remained. I have never seen a
disconnect when using one camera, so there seems to be some mutual
electrical influence (I don't think this is a software issue).

Regards,
Wouter Vlothuizen




From Peter.Pregler@risc.uni-linz.ac.at Tue, 12 Sep 2000 11:25:51 +0200
Date: Tue, 12 Sep 2000 11:25:51 +0200
From: Peter Pregler Peter.Pregler@risc.uni-linz.ac.at
Subject: [cpia] Re: 2 cameras streaming at once?

On Tue, Sep 12, 2000 at 11:06:04AM +0200, WJ Vlothuizen wrote:
> The reason why I would favor streaming and double buffering is that I
> use the camera's to provide vision for a robot, where I want a high
> update rate and every bit of performance counts. I entirely agree with
> you that this is not the way most people will use these cameras. Instead
> of a interrupt driven scheme I would envision the use of a kernel thread
> that works when incoming data and an outgoing buffer are available, and
> otherwise goes to sleep.

Okay, I see now that the two things are independant. The design I had
finally in mind would have used a kernel thread too. But if you drive
the kernel-thread by polling or by interrupts is of cause
independent. So go ahead! :) One side-note, in v4l there are no real
API-hooks to control the start and stop of streaming. If you really
start coding please contact me and I can give you the details about
where and why this matters.

> Further experiments on my side show that the driver *always* fails after
> a hub disconnect. I don't know whether the CPiA-driver could sense such
> a disconnect and reinitialize the camera, but the disconnect should not
> be there in the first place. After some reading on www.usb.org I removed
> the EMI-control components on the USB formcard: this clearly improved
> the results, but the problem still remained. I have never seen a
> disconnect when using one camera, so there seems to be some mutual
> electrical influence (I don't think this is a software issue).

I did yesterday some tests with disconnecting the usb-camera and had
in no time a kernel-ooops. That was with the 2.2.16 usb
backport. However I have not looked closer at it. So there are
definitly software issue around. The question is if this the
cpia-driver or the hub.

Have fun, Peter

-- 
Email: Peter.Pregler@risc.uni-linz.ac.at
WWW:   http://www.risc.uni-linz.ac.at/people/ppregler
ICQ:   61011460




From root@velenje.cx 13 Sep 2000 09:02:16 CEST
Date: 13 Sep 2000 09:02:16 CEST
From: Samo Gabrovec root@velenje.cx
Subject: [cpia] USB terracam problems..

Hi!
I bought another cam (terracam USB) and on SuSe 7.0 which has usb support and
cpia 1.0 in the kernel 
cam started to work in secunds i pluged it in ... But things aren`t so great
after all.
I get (for my knowledge of USB and this stuff) weird messages when looking the
in the /var/log/messages..
there are a lot of "gekko kernel: usb-uhci.c: interrupt, status 2, frame# 198 "
messages and it`s just the matter of time 
when i get this 
--
bash-2.04# tail /var/log/messages
Sep 13 08:47:32 gekko kernel: usb_control/bulk_msg: timeout
Sep 13 08:47:32 gekko kernel: usb-uhci.c: interrupt, status 3, frame# 187
Sep 13 08:47:32 gekko kernel: usb-uhci.c: interrupt, status 3, frame# 191
Sep 13 08:47:32 gekko kernel: usb-uhci.c: interrupt, status 3, frame# 193
Sep 13 08:47:32 gekko kernel: usb-uhci.c: interrupt, status 3, frame# 195
Sep 13 08:47:32 gekko kernel: usb-uhci.c: interrupt, status 2, frame# 198
Sep 13 08:47:32 gekko kernel: usb-uhci.c: interrupt, status 2, frame# 223
Sep 13 08:47:32 gekko kernel: usb-uhci.c: interrupt, status 3, frame# 261
Sep 13 08:47:32 gekko kernel: usb-uhci.c: interrupt, status 3, frame# 266
Sep 13 08:47:32 gekko kernel: usb-uhci.c: interrupt, status 3, frame# 271 
--
After that i have to kill the program that was used for capturing.
I tried them all xawtv, gqcam, w3cam they all "crash" in like 5-10 minutes of
using them.
The funny thing is that if i use for exsample gqcam and if it`s running
(showing the the live video)
i`ll get similar messages (with out gekko kernel: usb_control/bulk_msg:
timeout) but it can run all night and maybe more 
but if i access the cam every 30 sec or less or more (interval pics for the
webcam) it crashes very quickly.

Before i upgraded to Suse 7.0 i used a 2.2.16 with the latest backport USB
driver and it was the same story ( from suse box..
SuSE already provides a Linux kernel which can truly be called a 2.2.17-pre
thanks to its variety of extensions. The extended USB support ...)
I think they use the same backport as i did on 2.2.16 which wouldn`t matter
much as i got the same results using my compiled kernel too.

Could someone point me to the right direction how to solve this?
thanks

Samo Gabrovec.
- 
----------------------------------------------------------------
visit http://www.velenje.cx
----------------------------------------------------------------

In /dev/null no one can hear you scream...
----------------------------------------------------------------





From marco_brosda@yahoo.de Wed, 13 Sep 2000 09:28:52 +0200 (CEST)
Date: Wed, 13 Sep 2000 09:28:52 +0200 (CEST)
From: =?iso-8859-1?q?Marco=20Brosda?= marco_brosda@yahoo.de
Subject: [cpia] USB terracam problems..

Hello,

I have 2 Terracams USB using the 2.2.16 Kernel from
RedHat 7.0 Beta (incl. USB Backport).

I've encountered the same Problems (using the ohci
driver (but the same with uhci on the other
mainboard)) when using ONE webcam. 
If i use gqcam i can capture the hole night long, but
when making pics with w3cam.cgi every 10 secs, after
2-10 minutes the ohci usb driver stops working. Then i
have to unload/load the ohci module and things are
going on. Sometimes i can make pics for hours (it
depends on the location of the cam ?!?). When using 2
cams the /dev/video0(1) Devices  are not accessible
after one minute of capturing with one cam. Then i've
to reboot the machine (from time to time linux crashes
totally).

Any Ideas ?

Marco



--- Samo Gabrovec <root@velenje.cx> schrieb: > Hi!
> I bought another cam (terracam USB) and on SuSe 7.0
> which has usb support and
> cpia 1.0 in the kernel 
> cam started to work in secunds i pluged it in ...
> But things aren`t so great
> after all.
> I get (for my knowledge of USB and this stuff) weird
> messages when looking the
> in the /var/log/messages..
> there are a lot of "gekko kernel: usb-uhci.c:
> interrupt, status 2, frame# 198 "
> messages and it`s just the matter of time 
> when i get this 
> --


__________________________________________________________________
Do You Yahoo!?
Gesendet von Yahoo! Mail - http://mail.yahoo.de
Yahoo! Mail auf Ihrem Handy? - http://mobil.yahoo.de




From adam@antispin.org Fri, 15 Sep 2000 12:32:48 +0100
Date: Fri, 15 Sep 2000 12:32:48 +0100
From: Adam Harrison adam@antispin.org
Subject: [cpia] STV0680

Hi All,

Since my last posts, I've spoken to someone within ST off the list (name 
witheld by request) regarding their STV0680 chip. This is a just a status 
report FYI:

1) Henry Bruce no longer works for ST, and he was the only person within 
the company au fait with Linux.

2) The STV0680 has the same IP issues as the Mattel camera (namely they 
have a good way of doing Bayer->RGB which they don't want to disclose) 
therefore no software will be released for it. However, apparently most 
future chips will have this functionality built into a co-processor.

3) The documentation for the USB and serial protocols are not fit for 
external use, and since ST would have to expend resource bringing them up 
to scratch we won't be seeing these either (despite them being offered a 
complete driver free of charge).

In summary, 1) is a shame, 2) looks like it will become a non-issue in 
future but I can't see 3) changing - if they won't release the docs for 
this chip, then they're unlikely to do it for further versions regardless 
of IPR issues. Avoid!

Cheers,

Adam.

-- 
"All that is necessary for the triumph of evil is that good men do nothing" 
- Edmunde Burke




From cryptus@ngi.de Fri, 15 Sep 2000 14:38:15 +0200
Date: Fri, 15 Sep 2000 14:38:15 +0200
From: F. H. cryptus@ngi.de
Subject: [cpia] Problem with parport and parallel Webcam II

Hi folks,

could anyone pls help me to get my Creative Webcam II started ?
The parport doesn't seem to find my camera.
Whats going wrong ?
And: Is the BIOS setting of the parallel port of any importance ?
I tried both ECP and ECP+EEP, (io=0x378, IRQ 7 set up in the BIOS),
both dont work but gives the same results, 
as stated below.

Many thanks, Frank

My configuration:

I have a Pentium II, SuSE Linux 6.3, kernel updated to 2.2.17,
(it didnt work with 2.2.13 before either)
cpia 1.1 driver installed,
parport configured as module:

My current modules.conf:
...
alias parport_lowlevel    parport_pc
options parport_pc io=0x378 irq=none,none
...

When I load the modules, with:

	modprobe parport
	modprobe parport_pc dma=3 irq=7
	modprobe videodev
	insmod cpia
	insmod cpia_pp parport=0

dmesg says:

parport0: PC-style at 0x378 (0x778), irq 7, dma 3
[SPP,ECP,ECPEPP,ECPPS2]
Linux video capture interface: v1.00
V4L-Driver for Vision CPiA based cameras v1.1.0
parport_probe: failed
parport0: no IEEE-1284 device present.
Parallel port driver for Vision CPiA based cameras v1.1.0
  0 camera(s) found
Parallel port driver for Vision CPiA based cameras v1.1.0
  using DMA mode (irq 7, DMA 3)
cpia_pp.c(33166):my_wait_peripheral(327):failed 0x50 should be 0x38
waited 33 jiffies
cpia_pp.c(33166):Negotiate2SetupPhase(375):B failed
cpia_pp.c(33166):ForwardSetup(835):could not negotiate for setup phase
cpia_pp.c(33199):my_wait_peripheral(327):failed 0x40 should be 0x0
waited 33 jiffies
cpia_pp.c(33199):Valid1284Termination(501):nAck should go low in
Valid1284Termination
cpia_pp.c(33199):Valid1284Termination(502):nsel D per D naut U nstrob U
nak U busy U nfaul D sel U init
U dir F
cpia_pp.c(33199):WritePacket(1096):Write failed in setup
cpia_pp.c(33199):cpia_pp_transferCmd(1293):Error writing command
cpia.c:do_command(1776):4005 - failed, retval=-5
  1 camera(s) found       

autoprobe says:
	cryptus:~ # more /proc/parport/0/autoprobe
	MODEL:Unknown device;
	MANUFACTURER:Unknown vendor


probably then its not astonishing that mcam doesnt find the camera ?

======   mcam-1.5  by Panteltje   =====

LPT1 at 0x378 -- ECP / 4 Bit

mcam: Get1284DeviceID() failed
mcam: unable to find DUAL on LPT1
CLINK_DetectPort: LPT2: not found

mcam: LPT2 does not exist
mcam: unable to find DUAL on LPT2
TransferMsg: SetTransferMode failed
TransferMsg: SetTransferMode failed
TransferMsg: SetTransferMode failed
TransferMsg: SetTransferMode failed
TransferMsg: SetTransferMode failed
...




From emeb@goodnet.com Fri, 15 Sep 2000 07:33:40 -0700 (MST)
Date: Fri, 15 Sep 2000 07:33:40 -0700 (MST)
From: Eric M. Brombaugh emeb@goodnet.com
Subject: [cpia] STV0680


On Fri, 15 Sep 2000, Adam Harrison wrote:

> 2) The STV0680 has the same IP issues as the Mattel camera (namely they 
> have a good way of doing Bayer->RGB which they don't want to disclose) 
> therefore no software will be released for it. However, apparently most 
> future chips will have this functionality built into a co-processor.

In case anyone's interested, I've got a pretty decent Bayer->RGB
method going on my Mattel camera application. Check out the code and some
examples at my website:

http://www.goodnet.com/~emeb/mattel_cam.html

Eric
 





From Peter_Pregler@email.com Sat, 16 Sep 2000 11:06:25 +0200
Date: Sat, 16 Sep 2000 11:06:25 +0200
From: Peter Pregler Peter_Pregler@email.com
Subject: [cpia] Problem with parport and parallel Webcam II

On Fri, Sep 15, 2000 at 02:38:15PM +0200, F. H. wrote:
> dmesg says:
> 
> parport0: PC-style at 0x378 (0x778), irq 7, dma 3
> [SPP,ECP,ECPEPP,ECPPS2]

This is sufficient. The parport is configured correctly.

> Linux video capture interface: v1.00
> V4L-Driver for Vision CPiA based cameras v1.1.0
> parport_probe: failed
> parport0: no IEEE-1284 device present.

I think this is the indicator of your problems. The Creative Webcam II
camera is an IEEE-1284 device. So either the camera is not connected
correctly, your parport-chip is something non-standard or there is
something wrong with your kernel. Here is what you should get with a
stock 2.2.17 and the 1.1.0 driver compiled against it:

parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [SPP,ECP,ECPEPP,ECPPS2]
Linux video capture interface: v1.00
V4L-Driver for Vision CPiA based cameras v1.1.0
parport0: read2 timeout.
parport_probe: succeeded
parport0: Multimedia device, VLSI Vision Ltd PPC2 Camera
Parallel port driver for Vision CPiA based cameras v1.1.0
  using DMA mode (irq 7, DMA 3)
cpia.c(144433):goto_low_power(3079):camera now in LOW power state
cpia.c(144441):goto_high_power(3065):camera now in HIGH power state
cpia.c(144441):dispatch_commands(2363):1 1 0 0 1 1 1 1 
cpia.c(144441):dispatch_commands(2364):0 1 1 1 1 1 1 1 
cpia.c(144494):save_camera_state(3101):0/0/185/0/220/214/214/230
cpia.c(144494):save_camera_state(3105):32/6/92
  CPiA Version: 1.20 (2.0)
  CPiA PnP-ID: 0553:0002:0100
  VP-Version: 1.0 0100
  1 camera(s) found

This is after:

root@gretel:/home/ppregler/proj/wc/cpia-1.1/module# modprobe videodev
root@gretel:/home/ppregler/proj/wc/cpia-1.1/module# insmod ./cpia.o
root@gretel:/home/ppregler/proj/wc/cpia-1.1/module# insmod ./cpia_pp.o

The parport was loaded at boot-time. The parport_probe is done
automagically during the insmod of cpia.o.

-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@email.com




From davey@doa.org Tue, 19 Sep 2000 00:52:55 +1100 (EST)
Date: Tue, 19 Sep 2000 00:52:55 +1100 (EST)
From: David Murn davey@doa.org
Subject: [cpia] aiptek webcam works

On Sun, 27 Aug 2000, Ries van Twisk wrote:

> I just wanted top tell you that the 'webcam HyperVcam Fun' is supported 
> using the Cpia driver (0553:0002).
> You can find more information on this webcam on www.aiptek.de

On a similar note, my "Swann SmartCam" works using the cpia/cpia_usb
driver too. (www.swann.com.au)

usb.c: USB new device connect, assigned device number 2
usb.c: kmalloc IF c0fcfb80, numif 1
usb.c: new device strings: Mfr=2, Product=1, SerialNumber=0
usb.c: USB device number 2 default language ID 0x409
Manufacturer: VLSI Vision Ltd.
Product: USB Camera
USB CPiA camera found
  CPiA Version: 1.33 (2.10)
  CPiA PnP-ID: 0553:0002:0106
  VP-Version: 1.0 0141
usb.c: cpia driver claimed interface c0fcfb80

> This is tested in a 2.2.16 kernel with the USB patch.

I'm using 2.3.99-pre6 kernel, with the built-in USB support.

> Only one minor thing is that i sometimes get a VIDIOCGFBUF ioctl error.

I get occasional bugs too, when reading from the camera, about invalid
line lengths and stuff.  If anyones interested I can paste a dmesg log of
what happens.

Davey







From root@velenje.cx 19 Sep 2000 20:33:55 CEST
Date: 19 Sep 2000 20:33:55 CEST
From: Samo Gabrovec root@velenje.cx
Subject: [cpia] Terracam USB

Hi.
I`ve writen before that i`ve had problems with terracam USB 
in the log files there`s lot`s of similar lines like this.
Sep 13 08:47:32 gekko kernel: usb-uhci.c: interrupt, status 3, frame# 191
and the cam doesnt last long then i get 
--
>  Sep 13 08:47:32 gekko kernel: usb_control/bulk_msg: timeout
>  Sep 13 08:47:32 gekko kernel: usb-uhci.c: interrupt, status 3, frame# 187
>  Sep 13 08:47:32 gekko kernel: usb-uhci.c: interrupt, status 3, frame# 191
>  Sep 13 08:47:32 gekko kernel: usb-uhci.c: interrupt, status 3, frame# 193
>  Sep 13 08:47:32 gekko kernel: usb-uhci.c: interrupt, status 3, frame# 195
and some more of those.
--
I`m using the USB backport on 2.2.16 (cpia 1.0)
What i`m asking is this...
Is this normal for all USB cams or is the terracam a shity one?
Has anyone solved this?
Peter you have an USB cam too does this happen to you ?

Thanks

Samo Gabrovec.
-- 
----------------------------------------------------------------
visit http://www.velenje.cx
----------------------------------------------------------------

In /dev/null no one can hear you scream...
----------------------------------------------------------------





From johannes@erdfelt.com Wed, 20 Sep 2000 15:15:28 -0400
Date: Wed, 20 Sep 2000 15:15:28 -0400
From: Johannes Erdfelt johannes@erdfelt.com
Subject: [cpia] Terracam USB

On Tue, Sep 19, 2000, Samo Gabrovec <root@velenje.cx> wrote:
> Hi.
> I`ve writen before that i`ve had problems with terracam USB 
> in the log files there`s lot`s of similar lines like this.
> Sep 13 08:47:32 gekko kernel: usb-uhci.c: interrupt, status 3, frame# 191
> and the cam doesnt last long then i get 
> --
> >  Sep 13 08:47:32 gekko kernel: usb_control/bulk_msg: timeout
> >  Sep 13 08:47:32 gekko kernel: usb-uhci.c: interrupt, status 3, frame# 187
> >  Sep 13 08:47:32 gekko kernel: usb-uhci.c: interrupt, status 3, frame# 191
> >  Sep 13 08:47:32 gekko kernel: usb-uhci.c: interrupt, status 3, frame# 193
> >  Sep 13 08:47:32 gekko kernel: usb-uhci.c: interrupt, status 3, frame# 195
> and some more of those.
> --
> I`m using the USB backport on 2.2.16 (cpia 1.0)
> What i`m asking is this...

You can try using the other UHCI driver (the Alternate or "JE" driver).

> Is this normal for all USB cams or is the terracam a shity one?

Well, you will get some errors with all cameras, but you're getting
errors pretty regularly.

> Has anyone solved this?
> Peter you have an USB cam too does this happen to you ?

I get errors, but not as many as you seem to be getting. Do you have the
camera plugged into a hub?

JE





From root@velenje.cx 20 Sep 2000 21:25:56 CEST
Date: 20 Sep 2000 21:25:56 CEST
From: Samo Gabrovec root@velenje.cx
Subject: [cpia] Terracam USB

On Wed, 20 Sep 2000 15:15:28 -0400, Johannes Erdfelt said:


>  
>  You can try using the other UHCI driver (the Alternate or "JE" driver).
>  
what do you mean by that ? 
>  
>  Well, you will get some errors with all cameras, but you're getting
>  errors pretty regularly.
>  
I compiled cpia 1.1 now i get even more errors but it doesnt crash ?!?! ( maybe
it does but not as often as it did before)
like 
---
Sep 20 21:23:30 gekko kernel: usb-uhci.c: interrupt, status 2, frame# 885 
Sep 20 21:23:30 gekko kernel: cpia.c:do_command(1776):c0b2 - failed, retval=-32 
Sep 20 21:23:38 gekko kernel: usb-uhci.c: interrupt, status 2, frame# 323 
Sep 20 21:23:38 gekko kernel: cpia.c:do_command(1776):c0b2 - failed, retval=-32 
.
===
>  I get errors, but not as many as you seem to be getting. Do you have the
>  camera plugged into a hub?
>  
No, no hub directly in the box.

-- 
----------------------------------------------------------------
visit http://www.velenje.cx
----------------------------------------------------------------

In /dev/null no one can hear you scream...
----------------------------------------------------------------





From johannes@erdfelt.com Wed, 20 Sep 2000 17:12:25 -0400
Date: Wed, 20 Sep 2000 17:12:25 -0400
From: Johannes Erdfelt johannes@erdfelt.com
Subject: [cpia] Terracam USB

On Wed, Sep 20, 2000, Samo Gabrovec <root@velenje.cx> wrote:
> On Wed, 20 Sep 2000 15:15:28 -0400, Johannes Erdfelt said:
> >  You can try using the other UHCI driver (the Alternate or "JE" driver).
>
> what do you mean by that ? 

Pretty much what I said. Try using the other driver. You'll have to
unselect the current UHCI driver in the kernel configuration and then it
will prompt you for the other driver.

> >  Well, you will get some errors with all cameras, but you're getting
> >  errors pretty regularly.
>
> I compiled cpia 1.1 now i get even more errors but it doesnt crash ?!?! ( maybe
> it does but not as often as it did before)
> like 
> ---
> Sep 20 21:23:30 gekko kernel: usb-uhci.c: interrupt, status 2, frame# 885 
> Sep 20 21:23:30 gekko kernel: cpia.c:do_command(1776):c0b2 - failed, retval=-32 
> Sep 20 21:23:38 gekko kernel: usb-uhci.c: interrupt, status 2, frame# 323 
> Sep 20 21:23:38 gekko kernel: cpia.c:do_command(1776):c0b2 - failed, retval=-32 

-32 = EPIPE

EPIPE gets returned on a babble or STALL. Could be a STALL. Hmmm.

> >  I get errors, but not as many as you seem to be getting. Do you have the
> >  camera plugged into a hub?
> 
> No, no hub directly in the box.

Is it a laptop?

JE





From Peter_Pregler@email.com Thu, 21 Sep 2000 13:23:40 +0200
Date: Thu, 21 Sep 2000 13:23:40 +0200
From: Peter Pregler Peter_Pregler@email.com
Subject: [cpia] Terracam USB

On Wed, Sep 20, 2000 at 03:15:28PM -0400, Johannes Erdfelt wrote:
> On Tue, Sep 19, 2000, Samo Gabrovec <root@velenje.cx> wrote:
> > Hi.
> > I`ve writen before that i`ve had problems with terracam USB 
> > in the log files there`s lot`s of similar lines like this.
> > Sep 13 08:47:32 gekko kernel: usb-uhci.c: interrupt, status 3, frame# 191
> > and the cam doesnt last long then i get 
> 
> You can try using the other UHCI driver (the Alternate or "JE"
> driver).

I have compiled the usb-stuff as a module and use the one named
'usb-uhci.o'. There is another one named 'uhci.o'. I have to check
which is which.

> > Is this normal for all USB cams or is the terracam a shity one?
> 
> Well, you will get some errors with all cameras, but you're getting
> errors pretty regularly.
> 
> > Has anyone solved this?
> > Peter you have an USB cam too does this happen to you ?

I do get those errors too from time to time but I never noticed
something bad. However, I have used only the gqcam shipped with the
driver lately. I will do some more tests as soon as I have upgraded my
machine at home.

-Peter

-- 
I will not waste chalk. --Bart Simpson at the blackboard
--------------------------------------------------------
Email: Peter_Pregler@email.com
WWW:   http://www.risc.uni-linz.ac.at/people/ppregler
ICQ:   61011460




From davey@doa.org Fri, 22 Sep 2000 07:58:29 +1100 (EST)
Date: Fri, 22 Sep 2000 07:58:29 +1100 (EST)
From: David Murn davey@doa.org
Subject: [cpia] Terracam USB

On 19 Sep 2000, Samo Gabrovec wrote:

> in the log files there`s lot`s of similar lines like this.
> Sep 13 08:47:32 gekko kernel: usb-uhci.c: interrupt, status 3, frame# 191

I get these frequently when I use my cam.

> I`m using the USB backport on 2.2.16 (cpia 1.0)

I'm using the proper USB version on 2.3.99-pre6 with both cpia 0.7.4 and
1.1.  Both versions give the same sorts of errors, although the 1.1
version seems to recover better.  Ie. when the 0.7.4 driver gets the
errors the only way to fix it is to reload the modules.  With 1.1, it
seems to work again after 5-10 seconds.

> Is this normal for all USB cams or is the terracam a shity one?

Well, its the same for my Swann SmartCam.

I'm using the UHCI module with an onboard USB controller on my ABit LX6
motherboard, with a 433mhz celeron (overclocked to 541).  I still get the
same errors when the machine is not overclocked.

Davey