From jmbuena@isys.dia.fi.upm.es Mon, 03 Apr 2000 13:14:53 +0200
Date: Mon, 03 Apr 2000 13:14:53 +0200
From: Jose Miguel Buenaposada Biencinto jmbuena@isys.dia.fi.upm.es
Subject: [cpia] Again: 2.2.14. & USB 2.3.50 Backport
Hi again !
I have resolved my problems with not resolved symbols loading the cpia
and
cpia_usb modules. It was my mistake, in kernel module configuration is
necessary
to say CONFIG_MODVERSIONS=N, if you say Y the symbols of the modules
will not match with the kernel's ones. I undertanded in a wrong way the
help
about it.
Now I can again use gqcam with the kernel 2.3.51 but I can not view it
with
2.2.14 patched with the usb backport. I get:
Apr 3 13:01:33 hal kernel: usb-uhci.c: version v1.184 time 19:47:42 Mar
31 2000
Apr 3 13:01:33 hal kernel: usb-uhci.c: Detected 2 ports
Apr 3 13:01:33 hal kernel: usb.c: new USB bus registered, assigned bus
number 1
Apr 3 13:01:33 hal kernel: usb.c: USB new device connect, assigned
device number 1
Apr 3 13:01:33 hal kernel: usb.c: new device strings: Mfr=0, Product=0,
SerialNumber=0
Apr 3 13:01:33 hal kernel: hub.c: USB hub found
Apr 3 13:01:33 hal kernel: hub.c: 2 ports detected
Apr 3 13:01:33 hal kernel: Length = 18
Apr 3 13:01:33 hal kernel: DescriptorType = 01
Apr 3 13:01:33 hal kernel: USB version = 1.00
Apr 3 13:01:33 hal kernel: Vendor:Product = 0000:0000
Apr 3 13:01:33 hal kernel: MaxPacketSize0 = 8
Apr 3 13:01:33 hal kernel: NumConfigurations = 1
Apr 3 13:01:33 hal kernel: Device version = 0.00
Apr 3 13:01:33 hal kernel: Device Class:SubClass:Protocol = 09:00:00
Apr 3 13:01:33 hal kernel: Hub device class
Apr 3 13:01:33 hal kernel: Configuration:
Apr 3 13:01:33 hal kernel: bLength = 9
Apr 3 13:01:33 hal kernel: bDescriptorType = 02
Apr 3 13:01:33 hal kernel: wTotalLength = 0019
Apr 3 13:01:33 hal kernel: bNumInterfaces = 01
Apr 3 13:01:33 hal kernel: bConfigurationValue = 01
Apr 3 13:01:33 hal kernel: iConfiguration = 00
Apr 3 13:01:33 hal kernel: bmAttributes = 40
Apr 3 13:01:33 hal kernel: MaxPower = 0mA
Apr 3 13:01:33 hal kernel:
Apr 3 13:01:33 hal kernel: Interface: 0
Apr 3 13:01:33 hal kernel: Alternate Setting: 0
Apr 3 13:01:33 hal kernel: bLength = 9
Apr 3 13:01:33 hal kernel: bDescriptorType = 04
Apr 3 13:01:33 hal kernel: bInterfaceNumber = 00
Apr 3 13:01:33 hal kernel: bAlternateSetting = 00
Apr 3 13:01:33 hal kernel: bNumEndpoints = 01
Apr 3 13:01:33 hal kernel: bInterface Class:SubClass:Protocol =
09:00:00 Apr 3 13:01:33 hal kernel: iInterface = 00
Apr 3 13:01:33 hal kernel: Endpoint:
Apr 3 13:01:33 hal kernel: bLength = 7
Apr 3 13:01:33 hal kernel: bDescriptorType = 05
Apr 3 13:01:33 hal kernel: bEndpointAddress = 81 (in)
Apr 3 13:01:33 hal kernel: bmAttributes = 03 (Interrupt)
Apr 3 13:01:33 hal kernel: wMaxPacketSize = 0008
Apr 3 13:01:33 hal kernel: bInterval = ff
Apr 3 13:01:34 hal kernel: usb.c: USB new device connect, assigned
device number 2
Apr 3 13:01:37 hal kernel: usb_control/bulk_msg: timeout
Apr 3 13:01:40 hal kernel: usb_control/bulk_msg: timeout
Apr 3 13:01:42 hal modprobe: modprobe: Can't locate module
char-major-81-0
Apr 3 13:01:43 hal kernel: usb_control/bulk_msg: timeout
Apr 3 13:01:49 hal last message repeated 2 times
Apr 3 13:01:49 hal kernel: usb.c: USB device not responding, giving up
(error=-110)
Apr 3 13:02:05 hal kernel: usb.c: USB disconnect on device -1
Apr 3 13:02:08 hal kernel: usb.c: USB new device connect, assigned
device number 2
Apr 3 13:02:11 hal kernel: usb_control/bulk_msg: timeout
Apr 3 13:02:23 hal last message repeated 4 times
Apr 3 13:02:23 hal kernel: usb.c: USB device not responding, giving up
(error=-110)
So I can not get usb connection with the cammera. What is wrong ? I know
the
difference is the kernel version and the patch, but somebody said that
he
was, with the same kernel and patch, running the driver without
problems.
Anybody can suggest anything ?
I have a zoomtel usb cammera.
--
-------------------------------------------------------------------
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 Peter_Pregler@email.com Tue, 4 Apr 2000 17:05:53 +0200
Date: Tue, 4 Apr 2000 17:05:53 +0200
From: Peter Pregler Peter_Pregler@email.com
Subject: [cpia] GPL release of the windows parport driver code
Hi all,
Henry Bruce from STMicroelectronics (former VLSI) sent me the windows
parport driver code for the cpia cameras licensed under the GPL. So
please have a look at it and integrate the good stuff to the
linux-CPiA driver. Especially could someone look at the initialisation
code and do a comparison to the linux cvs-code? I had only a short
look at it and did not notice any _big_ differences. Even the comments
for the firmware version-1.02 code sounded similar. :) But I guess the
solution to the initialisation problems that people some encounter
lies somewhere down there. I had also a short look at the dma-code and
apart from some speed tunings for special chip-sets there seems to be
no really big difference. Anyway, I have enough to do to get
fifo/dma-read work for the 2.3.99 kernel. After that I might have a
look at how streaming is done in the windows driver. Almost forgot,
the stuff is available from http://webcam.sourceforge.net/.
Once again I would like to thank Henry Bruce for his ongoing efforts
to release relevant programming information to the linux community.
Have fun, Peter
--
Email: Peter_Pregler@email.com
WWW: http://www.risc.uni-linz.ac.at/people/ppregler
From roger@cs.strath.ac.uk Tue, 04 Apr 2000 16:18:22 +0100
Date: Tue, 04 Apr 2000 16:18:22 +0100
From: Roger Hardiman roger@cs.strath.ac.uk
Subject: [cpia] moving my CPiA camera to a linux/win 2000 dual boot box
Hi,
I've got my CPiA camera (one of the Pace ones in the UK)
on a linux / Win98 box right now.
I wanted to move it to my Linux / Win 2000 box.
Sorry this is slightly off topic but none of the
CPiA vendors seem to have Windows 2000 drivers for
the camera.
Does anyone on the list have any ideas about Win 2K
support.
Perhaps Henry knows if anyone wrote a WDM driver.
I'm just happy good old Linux supports my
USB camera and my OPTi 931 sound card.
Cheers
Roger
--
Roger Hardiman
Strathclyde University
roger@cs.strath.ac.uk
From vlothuizen@fel.tno.nl Thu, 06 Apr 2000 09:54:49 +0200
Date: Thu, 06 Apr 2000 09:54:49 +0200
From: WJ Vlothuizen vlothuizen@fel.tno.nl
Subject: [cpia] minor bug for GREYSCALE in cpia-0.7.4
I don't think many people need VIDEO_PALETTE_GREY, but I found a minor
bug when using this palette:
In function skipcount() a "return count;" is needed after "case
VIDEO_PALETTE_GREY:"
The driver is working like a breeze, keep up the good work.
Wouter
From chitta@cse.iitkgp.ernet.in Fri, 7 Apr 2000 21:56:57 +0530 (IST)
Date: Fri, 7 Apr 2000 21:56:57 +0530 (IST)
From: Chittaranjan Mandal chitta@cse.iitkgp.ernet.in
Subject: [cpia] Support for Creative Webcam Go.
Is there Video4Linux support for Creative Webcam Go?
Thanks,
Chitta
From natorro@yahoo.com Fri, 07 Apr 2000 22:53:41 -0500
Date: Fri, 07 Apr 2000 22:53:41 -0500
From: Carlos Ernesto =?iso-8859-1?Q?L=F3pez=20Natar=E9n?= natorro@yahoo.com
Subject: [cpia] Can I use multiple cameras???
Hi, first I want to give a BIG thanks to all the people making
this stuff possible :-) now my problem is the following:
I want to make a kindergarden monitor for five classrooms using
5 Web cams II, my main concern is in how to connect them in the
server, is there anything like a hub for the parallel port or
anything like that??? then, assuming I can connect them all in
the computer, just inserting the cpia and cpia_pp (cpia_usb) modules
the cameras will be detected??? I mean how many cameras can be
detected???
I recieve a message saying something like: 1 cameras detected, that
made me think I can use more than one :-) I guess...
the next problem is assuming I can put them all in the "hub" how can
I amplify the signal from the cameras because the five rooms are
separated and I need some extra cable to concentrate all the cameras
ports.
Any help will be greatly appreciated.
Thanks
natorro
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
From harvengj@skynet.be Sat, 8 Apr 2000 17:20:32 +0200
Date: Sat, 8 Apr 2000 17:20:32 +0200
From: Harvengt Jean-Marc harvengj@skynet.be
Subject: [cpia] zoom webcam and ISA
This is a multi-part message in MIME format.
------=_NextPart_000_0004_01BFA17E.BECCB060
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Does somebody know about a driver for the ISA version of the Zoom Webcam =
?
Is your driver supporting it ?
Thanks,
Jean-Marc
------=_NextPart_000_0004_01BFA17E.BECCB060
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Does somebody know about a driver =
for the ISA=20
version of the Zoom Webcam ?
Is your driver =
supporting it=20
?
Thanks,
Jean-Marc
------=_NextPart_000_0004_01BFA17E.BECCB060--
From sbertin@mindspring.com Sat, 8 Apr 2000 11:57:20 -0400 (EDT)
Date: Sat, 8 Apr 2000 11:57:20 -0400 (EDT)
From: sbertin@mindspring.com sbertin@mindspring.com
Subject: [cpia] Can I use multiple cameras???
On 7 Apr, Carlos Ernesto López Natarén wrote:
> I want to make a kindergarden monitor for five classrooms using
> 5 Web cams II, my main concern is in how to connect them in the
> server
You'll need 1 parallel port for each camera. The kernel can support up
to 8 parallel ports.
> assuming I can connect them all in
> the computer, just inserting the cpia and cpia_pp (cpia_usb) modules
> the cameras will be detected??? I mean how many cameras can be
> detected???
The cpia_pp driver supports as many cameras as the kernel supports
parallel ports. Video4Linux supports up to 64 video capture devices, so
that would probably be the limit for USB.
Those are code limits, there are practical limits also. With more that
2 or 3 parallel port cameras, you will run out of DMAs. That means that
additional cameras will need MUCH more CPU time to read from the port,
and a faster CPU may not help much. At that point USB is probably a
better option.
USB also has its limits. Each camera needs at least 2.5Mb/s. With 12Mb/s
available bandwidth, that means a max of 4 cameras active at once. To
get that low bandwidth usage would probably require hardware and driver
modifications. The current driver with most cameras will need 7.4Mb/s,
so only 1 active at a time.
> the next problem is assuming I can put them all in the "hub" how can
> I amplify the signal from the cameras because the five rooms are
> separated and I need some extra cable to concentrate all the cameras
> ports.
I have seen devices to extend the cable length for printers, but I doubt
they would work with cameras.
Scott J. Bertin
sbertin@mindspring.com
From Nick.Holloway@alfie.demon.co.uk 9 Apr 2000 17:21:26 +0100
Date: 9 Apr 2000 17:21:26 +0100
From: Nick Holloway Nick.Holloway@alfie.demon.co.uk
Subject: [cpia] Inclusion in mainstream kernel
I see that version 0.7.4 will be included in 2.3.99-pre4. Excellent!
--
`O O' | Nick.Holloway@alfie.demon.co.uk
// ^ \\ | http://www.alfie.demon.co.uk/
From jerdfelt@sventech.com Sun, 9 Apr 2000 18:16:47 -0400
Date: Sun, 9 Apr 2000 18:16:47 -0400
From: Johannes Erdfelt jerdfelt@sventech.com
Subject: [cpia] Inclusion in mainstream kernel
On Sun, Apr 09, 2000, Nick Holloway wrote:
> I see that version 0.7.4 will be included in 2.3.99-pre4. Excellent!
Yup. I submitted a week or two ago. It's the CVS version without the 2.2
compatibility code.
JE
From Peter_Pregler@email.com Mon, 10 Apr 2000 09:24:25 +0200
Date: Mon, 10 Apr 2000 09:24:25 +0200
From: Peter Pregler Peter_Pregler@email.com
Subject: [cpia] Can I use multiple cameras???
On Sat, Apr 08, 2000 at 11:57:20AM -0400, sbertin@mindspring.com wrote:
> On 7 Apr, Carlos Ernesto López Natarén wrote:
> > I want to make a kindergarden monitor for five classrooms using
> > 5 Web cams II, my main concern is in how to connect them in the
> > server
>
> USB also has its limits. Each camera needs at least 2.5Mb/s. With 12Mb/s
> available bandwidth, that means a max of 4 cameras active at once. To
> get that low bandwidth usage would probably require hardware and driver
> modifications. The current driver with most cameras will need 7.4Mb/s,
> so only 1 active at a time.
I guess for surveilance purposes you do not need 10fps. Taking a
snap-shop every second might be enough. However, I have no idea how
fast kindergarden-kids are these days. :) I'd say the main problem is
distance.
-Peter
--
I will not waste chalk. --Bart Simpson at the blackboard
--------------------------------------------------------
Email: Peter.Pregler@email.com
WWW: http://www.risc.uni-linz.ac.at/people/ppregler
From ben@oaktree.co.uk Mon, 10 Apr 2000 14:26:33 +0100
Date: Mon, 10 Apr 2000 14:26:33 +0100
From: Ben Dooks ben@oaktree.co.uk
Subject: [cpia] Microtek EyeStar2
Hi, i've just purchased one of these cameras (EyeStar2) and was wondering
if anyone knew if there is a driver for this device available? If not,
is there anyone who'd point me in the right direction to start an driver?
The CPIA driver detects the camera, but does not work (kernel oops).
Machine is based on ABIT Bp6, 2xCeleron400, 128Mb RAM,...
----- inserting the compiled modules
V4L-Driver for Vision CPiA based cameras v0.7.4
Parallel port driver for Vision CPiA based cameras v0.7.4
using PIO mode
cpia_pp.c(13561):Negotiate2SetupPhase(360):Busy should be high at beginning
cpia_pp.c(13594):my_wait_peripheral(325):failed 0x58 should be 0xd0 waited 33 ji
ffies
cpia_pp.c(13594):Valid1284Termination(512):status bit did not go to the correct
value
cpia_pp.c(13594):Negotiate2SetupPhase(360):Busy should be high at beginning
cpia_pp.c(13627):my_wait_peripheral(325):failed 0x58 should be 0xd0 waited 33 ji
ffies
cpia_pp.c(13627):Valid1284Termination(512):status bit did not go to the correct
value
cpia_pp.c(13627):Negotiate2SetupPhase(360):Busy should be high at beginning
cpia_pp.c(13660):my_wait_peripheral(325):failed 0x40 should be 0x0 waited 33 jif
fies
cpia_pp.c(13660):SimECPReadBuffer(538):nAck didn't went down after read 1 bytes
no more data ?
cpia_pp.c(13693):my_wait_peripheral(325):failed 0x58 should be 0xd0 waited 33 ji
ffies
cpia_pp.c(13693):Valid1284Termination(512):status bit did not go to the correct
value
cpia.c(13693):do_command(1651):c003 - failed, retval=-5
1 camera(s) found
-----
----- kernel oops
Unable to handle kernel NULL pointer dereference at virtual address 0000000c
current->tss.cr3 = 06762000, %cr3 = 06762000
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[]
EFLAGS: 00010206
eax: 00000000 ebx: 00032000 ecx: c6770000 edx: 00000322
esi: c8859000 edi: c8859000 ebp: 0000001f esp: c6771ec4
ds: 0018 es: 0018 ss: 0018
Process webcam (pid: 434, process nr: 34, stackpage=c6771000)
Stack: c68e8cc0 c66e78a0 c6771ef4 c0130dcd c7f880e0 c884de4b 00031ba5 c01ba24b
c69c30c0 ffffffe9 c6b05ab0 00000000 c6971005 00000006 070f23c0 c0129fc0
00000051 c8844177 c6b05ab0 00000000 00000000 c69c30c0 00000020 c013109a
-----
----- output from ksyms
c885585c cpia_pp_init [cpia_pp]
c8854164 ECPReadBuffer_DMA [cpia_pp]
c88545b0 ECPReadBuffer [cpia_pp]
c884f030 cpia_video_init [cpia]
c884f468 cpia_unregister_camera [cpia]
c884f32c cpia_register_camera [cpia]
c884423c video_register_device [videodev]
c884430c video_unregister_device [videodev]
-----
cheers,
--
Ben
As you exit the plane, please make sure to gather all of your
belongings. Anything left behind will be distributed evenly among the
flight attendants. Please do not leave children or spouses.
--
Ben
As you exit the plane, please make sure to gather all of your
belongings. Anything left behind will be distributed evenly among the
flight attendants. Please do not leave children or spouses.
From nikom@merl.com Mon, 10 Apr 2000 09:55:59 -0400
Date: Mon, 10 Apr 2000 09:55:59 -0400
From: Jacob Nikom nikom@merl.com
Subject: [cpia] Inclusion in mainstream kernel
Is it possible to download this kernel?
Jacob Nikom
Nick Holloway wrote:
>
> I see that version 0.7.4 will be included in 2.3.99-pre4. Excellent!
>
> --
> `O O' | Nick.Holloway@alfie.demon.co.uk
> // ^ \\ | http://www.alfie.demon.co.uk/
>
> _______________________________________________
> cpia mailing list - cpia@risc.uni-linz.ac.at
> http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia
From Peter_Pregler@email.com Mon, 10 Apr 2000 17:11:59 +0200
Date: Mon, 10 Apr 2000 17:11:59 +0200
From: Peter Pregler Peter_Pregler@email.com
Subject: [cpia] Inclusion in mainstream kernel
On Mon, Apr 10, 2000 at 09:55:59AM -0400, Jacob Nikom wrote:
> Is it possible to download this kernel?
The patch is on your favorite kernel mirror in the subdirectory 'testing'
instead of 'v2.3'. The pre4.5 seems was the latest as of writing this.
-Peter
>
> Jacob Nikom
>
> Nick Holloway wrote:
> >
> > I see that version 0.7.4 will be included in 2.3.99-pre4. Excellent!
> >
>
> _______________________________________________
> 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
From Peter_Pregler@email.com Mon, 10 Apr 2000 17:18:03 +0200
Date: Mon, 10 Apr 2000 17:18:03 +0200
From: Peter Pregler Peter_Pregler@email.com
Subject: [cpia] Microtek EyeStar2
On Mon, Apr 10, 2000 at 02:26:33PM +0100, Ben Dooks wrote:
> Hi, i've just purchased one of these cameras (EyeStar2) and was wondering
> if anyone knew if there is a driver for this device available? If not,
> is there anyone who'd point me in the right direction to start an
> driver?
> The CPIA driver detects the camera, but does not work (kernel oops).
> Machine is based on ABIT Bp6, 2xCeleron400, 128Mb RAM,...
Since CPiA is detected the driver is most probably correct. What
kernel-version is this? Could you give us more information,
kernel-version, parport-config, interrupt setting, and also compile
the driver with DEBUG turned on.
-Peter
--
I will not waste chalk. --Bart Simpson at the blackboard
--------------------------------------------------------
Email: Peter.Pregler@email.com
WWW: http://www.risc.uni-linz.ac.at/people/ppregler
From ben@oaktree.co.uk Mon, 10 Apr 2000 23:06:55 +0100
Date: Mon, 10 Apr 2000 23:06:55 +0100
From: Ben Dooks ben@oaktree.co.uk
Subject: [cpia] Re: [ADSLtrials] Tweak your Registry!
On Mon, Apr 10, 2000 at 05:50:44PM +0100, Faye Pearson wrote:
> Ben Dooks [ben@oaktree.co.uk] wrote:
> > I only use windows 'cos i'm too lazy to get quake3 running nicely under linux
> > and the webcam i own working ok as well (well, it keeps causing kernel oops')
>
> Install utahglx to get hardware GL for linux for tnt, g200 and something else
> I forget.
didn't manage to get nvidia's solution running for my TNT2
> Install kernel 2.3.99pre3 to get the Creative Webcam 2 USB working :)
don't like development kernels...
--
Ben
As you exit the plane, please make sure to gather all of your
belongings. Anything left behind will be distributed evenly among the
flight attendants. Please do not leave children or spouses.
From ben@oaktree.co.uk Tue, 11 Apr 2000 15:22:02 +0100
Date: Tue, 11 Apr 2000 15:22:02 +0100
From: Ben Dooks ben@oaktree.co.uk
Subject: [cpia] WinBond 9966
It turns out that the EyeStar2 (parallel) is based on the 29966 chipset.
I have downloaded the datasheet, and I am thinking of writing a driver
for this. Is there any points that people would like to make before
I start, or helpful hints if possible.
cheers,
--
Ben
As you exit the plane, please make sure to gather all of your
belongings. Anything left behind will be distributed evenly among the
flight attendants. Please do not leave children or spouses.
From kopecjc@att.net Tue, 11 Apr 2000 23:23:01 -0400
Date: Tue, 11 Apr 2000 23:23:01 -0400
From: Joseph C. Kopec kopecjc@att.net
Subject: [cpia] No Rule to make target '...usbdev_fs_i.h'
I am running version 2.3.99pre3 of the Linux Kernel and I have been
trying to 'make' cpia-0.7.4 in the modules directory, with my intent
being to use cpia as a module for a USB camera (Aiptek HyperVcam Fun),
but I have been getting the above-mentioned error message. Does anyone
have any suggestions as to what is going wrong? I am pretty sure I have
USB support and USB-UHCI, Video4Linux and Preliminary USB device
filesystem correctly compiled into the kernel. (Does usbdev_fs_i.h have
anything to do with filesystems, as 'fs' seems to suggest?) I do not
have CPiA Camera support compiled in the kernel or as a module. One
though I have is that I may have not prepared the Makefile properly --
would anyone be able to suggest what I should do to the default Makefile
to enable cpia-0.7.4 to support USB as a module under 2.3.99 (the README
instructions are rather brief)? Any suggestions would be much
appreciated.
From jerdfelt@sventech.com Tue, 11 Apr 2000 23:35:32 -0400
Date: Tue, 11 Apr 2000 23:35:32 -0400
From: Johannes Erdfelt jerdfelt@sventech.com
Subject: [cpia] No Rule to make target '...usbdev_fs_i.h'
On Tue, Apr 11, 2000, Joseph C. Kopec wrote:
> I am running version 2.3.99pre3 of the Linux Kernel and I have been
> trying to 'make' cpia-0.7.4 in the modules directory, with my intent
> being to use cpia as a module for a USB camera (Aiptek HyperVcam Fun),
> but I have been getting the above-mentioned error message. Does anyone
> have any suggestions as to what is going wrong? I am pretty sure I have
> USB support and USB-UHCI, Video4Linux and Preliminary USB device
> filesystem correctly compiled into the kernel. (Does usbdev_fs_i.h have
> anything to do with filesystems, as 'fs' seems to suggest?) I do not
> have CPiA Camera support compiled in the kernel or as a module. One
> though I have is that I may have not prepared the Makefile properly --
> would anyone be able to suggest what I should do to the default Makefile
> to enable cpia-0.7.4 to support USB as a module under 2.3.99 (the README
> instructions are rather brief)? Any suggestions would be much
> appreciated.
Well, you can upgrade to 2.3.99pre4 and have the CPiA driver from CVS
already in the main line kernel, without any dependancy problems.
JE
From lunarbard@moonman.com Wed, 12 Apr 2000 02:00:16 CDT
Date: Wed, 12 Apr 2000 02:00:16 CDT
From: David Cougle lunarbard@moonman.com
Subject: [cpia] better pic
can someone tell me why i get so much fuzz?
http://www.slidellweb.com/dcougle/sheesh.jpg
and, with lights out, same prob...
http://www.slidellweb.com/dcougle/sheesh2.jpg
my quickcam black and white had a better picture than these:(
--
http://www.slidellweb.com/dcougle
ICQ #3795561
Lunarbard on AOL(Instant Messenger)
Proverbs 15:3
Linux, operating system of the future
Fight The Apathy
From kopecjc@att.net Wed, 12 Apr 2000 14:49:24 +0000
Date: Wed, 12 Apr 2000 14:49:24 +0000
From: kopecjc@att.net kopecjc@att.net
Subject: [cpia] No Rule to make target '...usbdev_fs_i.h' (fwd)
---------------------- Forwarded Message: ---------------------
From: kopecjc@att.net
To: Johannes Erdfelt
Subject: Re: [cpia] No Rule to make target '...usbdev_fs_i.h'
Date: Wed, 12 Apr 2000 14:09:10 +0000
Am I correct to understand that in pre4 cpia-0.7.4 is an
option that can be compiled into the kernel by making the
appropriate selection in 'config' during kernel
configuration? (What about pre5, which is now the
latest?) The reason I ask is that the CPiA README says
'Do not enable USB CPiA Camera support in the kernel.
That will conflict with this driver.' On the other hand,
in the notes to CPiA-control, Peter Pregler said on March
13 that 'Sometime in the future the driver will be part
of the standard kernels.' Has this happened already
> On Tue, Apr 11, 2000, Joseph C. Kopec wrote:
> > I am running version 2.3.99pre3 of the Linux Kernel and I have been
> > trying to 'make' cpia-0.7.4 in the modules directory, with my intent
> > being to use cpia as a module for a USB camera (Aiptek HyperVcam Fun),
> > but I have been getting the above-mentioned error message. Does anyone
> > have any suggestions as to what is going wrong? I am pretty sure I have
> > USB support and USB-UHCI, Video4Linux and Preliminary USB device
> > filesystem correctly compiled into the kernel. (Does usbdev_fs_i.h have
> > anything to do with filesystems, as 'fs' seems to suggest?) I do not
> > have CPiA Camera support compiled in the kernel or as a module. One
> > though I have is that I may have not prepared the Makefile properly --
> > would anyone be able to suggest what I should do to the default Makefile
> > to enable cpia-0.7.4 to support USB as a module under 2.3.99 (the README
> > instructions are rather brief)? Any suggestions would be much
> > appreciated.
>
> Well, you can upgrade to 2.3.99pre4 and have the CPiA driver from CVS
> already in the main line kernel, without any dependancy problems.
>
> JE
>
>
> _______________________________________________
> cpia mailing list - cpia@risc.uni-linz.ac.at
> http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia
From jerdfelt@sventech.com Wed, 12 Apr 2000 14:01:02 -0400
Date: Wed, 12 Apr 2000 14:01:02 -0400
From: Johannes Erdfelt jerdfelt@sventech.com
Subject: [cpia] No Rule to make target '...usbdev_fs_i.h' (fwd)
It's a part of the standard kernel as of 2.3.99-pre4
JE
On Wed, Apr 12, 2000, kopecjc@att.net wrote:
>
> ---------------------- Forwarded Message: ---------------------
> From: kopecjc@att.net
> To: Johannes Erdfelt
> Subject: Re: [cpia] No Rule to make target '...usbdev_fs_i.h'
> Date: Wed, 12 Apr 2000 14:09:10 +0000
>
> Am I correct to understand that in pre4 cpia-0.7.4 is an
> option that can be compiled into the kernel by making the
> appropriate selection in 'config' during kernel
> configuration? (What about pre5, which is now the
> latest?) The reason I ask is that the CPiA README says
> 'Do not enable USB CPiA Camera support in the kernel.
> That will conflict with this driver.' On the other hand,
> in the notes to CPiA-control, Peter Pregler said on March
> 13 that 'Sometime in the future the driver will be part
> of the standard kernels.' Has this happened already
> > On Tue, Apr 11, 2000, Joseph C. Kopec wrote:
> > > I am running version 2.3.99pre3 of the Linux Kernel and I have been
> > > trying to 'make' cpia-0.7.4 in the modules directory, with my intent
> > > being to use cpia as a module for a USB camera (Aiptek HyperVcam Fun),
> > > but I have been getting the above-mentioned error message. Does anyone
> > > have any suggestions as to what is going wrong? I am pretty sure I have
> > > USB support and USB-UHCI, Video4Linux and Preliminary USB device
> > > filesystem correctly compiled into the kernel. (Does usbdev_fs_i.h have
> > > anything to do with filesystems, as 'fs' seems to suggest?) I do not
> > > have CPiA Camera support compiled in the kernel or as a module. One
> > > though I have is that I may have not prepared the Makefile properly --
> > > would anyone be able to suggest what I should do to the default Makefile
> > > to enable cpia-0.7.4 to support USB as a module under 2.3.99 (the README
> > > instructions are rather brief)? Any suggestions would be much
> > > appreciated.
> >
> > Well, you can upgrade to 2.3.99pre4 and have the CPiA driver from CVS
> > already in the main line kernel, without any dependancy problems.
> >
> > JE
> >
> >
> > _______________________________________________
> > 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 gstalusan@math.uwaterloo.ca Wed, 12 Apr 2000 19:32:51 EDT
Date: Wed, 12 Apr 2000 19:32:51 EDT
From: George Talusan gstalusan@math.uwaterloo.ca
Subject: [cpia] ezonics
Hi folks,
I'm running 2.3.99-pre4 and after using gqcam-0.7.2 for a few
minutes the driver hangs. gqcam goes into D state and the
only way to get CPiA working again is by rebooting.
I'm using an Abit BP6 2x466MHz, and an EZonics EZcam USB.
Could this be a USB or CPiA problem?
Here's dmesg.
cpia data error: [9] len=768, status=FFFFFFAC
cpia.c:parse_picture(1960):line length was not 1 but -2 after 3806/19886
bytes
cpia data error: [7] len=288, status=FFFFFFAC
cpia.c:parse_picture(1960):line length was not 1 but 0 after 18483/20836
bytes
cpia data error: [6] len=128, status=FFFFFFAC
cpia data error: [7] len=320, status=FFFFFFAC
cpia data error: [8] len=128, status=FFFFFFAC
cpia data error: [9] len=96, status=FFFFFFAC
cpia.c:parse_picture(1960):line length was not 1 but -1 after 14574/18075
bytes
usb-uhci.c: interrupt, status 2, frame# 1071
cpia data error: [0] len=416, status=FFFFFFAC
cpia data error: [5] len=256, status=FFFFFFAC
cpia.c:parse_picture(1960):line length was not 1 but -2 after 12901/25178
bytes
usb-uhci.c: interrupt, status 2, frame# 1449
usb-uhci.c: interrupt, status 2, frame# 661
usb-uhci.c: interrupt, status 2, frame# 1575
usb-uhci.c: interrupt, status 2, frame# 295
usb-uhci.c: interrupt, status 2, frame# 1541
usb-uhci.c: interrupt, status 2, frame# 1673
george
From jerdfelt@sventech.com Wed, 12 Apr 2000 19:46:32 -0400
Date: Wed, 12 Apr 2000 19:46:32 -0400
From: Johannes Erdfelt jerdfelt@sventech.com
Subject: [cpia] ezonics
On Wed, Apr 12, 2000, George Talusan wrote:
>
> I'm running 2.3.99-pre4 and after using gqcam-0.7.2 for a few
> minutes the driver hangs. gqcam goes into D state and the
> only way to get CPiA working again is by rebooting.
>
> I'm using an Abit BP6 2x466MHz, and an EZonics EZcam USB.
>
> Could this be a USB or CPiA problem?
>
> Here's dmesg.
>
> cpia data error: [9] len=768, status=FFFFFFAC
> cpia.c:parse_picture(1960):line length was not 1 but -2 after 3806/19886
> bytes
> cpia data error: [7] len=288, status=FFFFFFAC
> cpia.c:parse_picture(1960):line length was not 1 but 0 after 18483/20836
> bytes
> cpia data error: [6] len=128, status=FFFFFFAC
> cpia data error: [7] len=320, status=FFFFFFAC
> cpia data error: [8] len=128, status=FFFFFFAC
> cpia data error: [9] len=96, status=FFFFFFAC
> cpia.c:parse_picture(1960):line length was not 1 but -1 after 14574/18075
> bytes
> usb-uhci.c: interrupt, status 2, frame# 1071
> cpia data error: [0] len=416, status=FFFFFFAC
> cpia data error: [5] len=256, status=FFFFFFAC
> cpia.c:parse_picture(1960):line length was not 1 but -2 after 12901/25178
> bytes
> usb-uhci.c: interrupt, status 2, frame# 1449
> usb-uhci.c: interrupt, status 2, frame# 661
> usb-uhci.c: interrupt, status 2, frame# 1575
> usb-uhci.c: interrupt, status 2, frame# 295
> usb-uhci.c: interrupt, status 2, frame# 1541
> usb-uhci.c: interrupt, status 2, frame# 1673
Try using the Alternate UHCI driver I wrote, people have reported better
results.
But, I think there's a bug in the CPiA driver which is causing it to get
stuck in D. You will always get errors like you mentioned above, but you
shouldn't get too many of them (depending on cable length, etc). I think
if a couple of frames in a row get dropped things could go bad and it'll
get stuck.
JE
From galmasi@leo.cs.uiuc.edu Thu, 13 Apr 2000 08:46:48 -0500 (CDT)
Date: Thu, 13 Apr 2000 08:46:48 -0500 (CDT)
From: George Almasi galmasi@leo.cs.uiuc.edu
Subject: [cpia] making the Intel QX3 work
Hi everyone,
The Intel QX3 is a toy microscope with a CPIA chip inside. It hooks up
to the USB port. I bought the thing, hooked it up and discovered that
it needed win98 (which I don't have and don't want to buy).
In the linux community, noone else seems to have bothered with this
microscope. But I discovered the linux/cpia home page, backpatched my
kernel, downloaded the cpia driver, and tweaked it (the product id
returned by the webcam is not 0x553, but 0x810 ... "Mattel Inc"). It
works.
*BUT*: The microscope has two lights and a pushbutton hooked up.
AFAIK there is no extra circuitry in the microscope, so the lights and
the button have to be hooked up to the CPIA chip somehow. The button
is unimportant, but the lights are crucial, because you can't take
good pictures by shining a flashlight on the microscope :-) The lights
must be low-power, because the microscope is powered through the USB
connector and it says it won't gobble up more than 500mA, of which 400
are already spoken for, right?
I tried playing with the MCPorts, but although they do return some
funny values (178, 192, 0, 0) writing them doesn't seem to be doing
much except occasionally crash the driver. (the write command fails
with a timeout, and I don't know what that means). The lights
definitely don't turn on.
My question is: does anyone have an idea where the lights might be
hooked up, and how to command them?
Another ignorant basic question: is the program in the CPIA's 8052
changeable? is it possibly customized for the microscope? would it be
possible to download and disassemble it without accessing the RS232
port? the reason I'm asking these questions is because the
documentation is kinda ambiguous on these points. My thought here is
that maybe there is a subroutine in the 8052 that has to be called to
turn the dang lights on.
George
PS No, I haven't opened up the microscope. I'll do that only if I have
no choice - then I'll see where the lights are wired.
From hartley@AIC.NRL.Navy.Mil Thu, 13 Apr 2000 11:03:25 -0400
Date: Thu, 13 Apr 2000 11:03:25 -0400
From: Ralph Hartley hartley@AIC.NRL.Navy.Mil
Subject: [cpia] SMALL cameras
I am trying to find the smallest and lightest possible digital camera.
I need to know the size, and more important to me the weight, of just
the camera and electronics.
My application is a very small aircraft, with an extremely (maybe
unrealistically) limited payload. I really do care about grams. Within
reason, $s don't matter as much.
The computer I am planning on using weighs ~20g, how much is the
camera likely to be? The only interface I know for sure I have is a
parallel port. Of course I need a somewhat civilized OS.
Ralph Hartley
Naval Research Lab
hartley@aic.nrl.navy.mil
From jeffl@SPATIALinfo.com Fri, 14 Apr 2000 13:29:58 +1000
Date: Fri, 14 Apr 2000 13:29:58 +1000
From: Jeff Laing jeffl@SPATIALinfo.com
Subject: [cpia] Barbie Cam
At the risk of being laughed at, has anyone managed to get anywhere with the
Barbie Cam? I have read through the scicomms.doc and understand whats in
it. However, there are a number of holes (big enough to push a truck
through).
Specifically, does anyone know what baudrate, etc to talk to the camera?
And is there a state diagram available? ie, up till now, when I talk to it
at 19200, 8N1, it seems to echo everything I send it exactly as-is. I'm
assuming its in some sort of test mode, but even the SB_EXIT_SELFTEST
messages seems to get echoed back.
Failing that, does anyone know of any Windows 95 tools I can use to sniff
whats going down the comms port while the camera is active? I'm despairing
of having to write a lot of software and needing to get multiple PC's
together...
Any help is appreciated,
Jeff Laing
----------------------------------------------------------------------------
---
"But when I am alone, I do not have the effrontery to consider myself an
artist
at all, not in the grand old meaning of the word: Giotto, Titian, Rembrandt,
Goya were great painters. I am only a public clown -- a mountebank. I have
understood my time and have exploited the imbecility, the vanity, the greed
of
my contemporaries. It is a bitter confession, this confession of mine, more
painful than it may seem. But at least and at last it does have the merit of
being honest." -- Pablo Picasso
From kopecjc@att.net Sun, 16 Apr 2000 19:40:33 -0400
Date: Sun, 16 Apr 2000 19:40:33 -0400
From: Joseph C. Kopec kopecjc@att.net
Subject: [cpia] 2.3.99-pre5 and cpia
I have installed 2.3.99-pre5 and have configured V4L and cpia into the
kernel (the kernel messages show that this has been done). I can't seem
to get my Aiptek Hyper Vcam Fun recognized, however. Trying to use
cpia-control returns a message indicating that /proc/cpia/video0 cannot
be opened -- which is no surprise, because it doesn't exist! Trying to
use gqcam returns a message something like device cannot be found at
/dev/video. Does anyone have any suggestions as to what I am doing
wrong? Thanks in advance.
From kopecjc@att.net Sun, 16 Apr 2000 22:29:24 -0400
Date: Sun, 16 Apr 2000 22:29:24 -0400
From: Joseph C. Kopec kopecjc@att.net
Subject: [cpia] Aiptek HyperVcam Fun
As mentioned in my earlier message, I have been having some problems
getting the Aiptek HyperVcam Fun webcam to operate, though it is
mentioned among the CPiA USB cameras on the webcam.sourceforge.net
site. Has anyone managed to get this to work under Linux with the cpia
software? When I boot up, I get the attached messages in dmesg --
basically, it says "usb.c: This device is not recognized by any
installed USB driver." One thing I noticed, is that it seemed that
usb-uchi and my ethernet port were both listed as using IRQ ll (and the
ethernet port worked fine) -- could this be causing the problem? Any
help would be much appreciated.
080
hub.c: USB hub found
hub.c: 2 ports detected
hub.c: ganged power switching
hub.c: standalone hub
hub.c: global over-current protection
hub.c: power on to power good time: 2ms
hub.c: hub controller current requirement: 0mA
hub.c: port 1 is removable
hub.c: port 2 is removable
hub.c: local power source is good
hub.c: no over-current condition exists
hub.c: enabling power on all ports
usb.c: hub driver claimed interface c11ba8a0
Linux NET4.0 for Linux 2.3
Based upon Swansea University Computer Society NET3.039
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 8192 bind 8192)
Initializing RT netlink socket
Starting kswapd v1.6
parport0: PC-style at 0x378 [PCSPP]
pty: 256 Unix98 ptys configured
lp0: using parport0 (polling).
Linux video capture interface: v1.00
V4L-Driver for Vision CPiA based cameras v0.7.4
Uniform Multi-Platform E-IDE driver Revision: 6.30
ide: Assuming 40MHz system bus speed for PIO modes; override with
idebus=xx
PIIX4: IDE controller on PCI bus 00 dev a1
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x20a0-0x20a7, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0x20a8-0x20af, BIOS settings: hdc:DMA, hdd:pio
hda: QUANTUM Bigfoot TX8.0AT, ATA DISK drive
hdc: COMPAQ DVD-ROM GD-2000, ATAPI CDROM drive
hdd: IOMEGA ZIP 100, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: 15698592 sectors (8038 MB) w/69KiB Cache, CHS=1038/240/63
hdd: 196608 sectors (101 MB) w/16KiB Cache, CHS=512/12/32
hub.c: port 2 connection change
hdc: ATAPI 20X DVD-ROM drive, 512kB Cache
Uniform CD-ROM driver Revision: 3.07
Partition check:
hda: hda1 hda2 < hda5 hda6 hda7 >
hdd:<7>hub.c: portstatus 101, change 1, High Speed
hub.c: portstatus 103, change 0, High Speed
usb.c: USB new device connect, assigned device number 2
usb.c: kmalloc IF c5fc7cc0, numif 1
usb.c: new device strings: Mfr=0, Product=0, SerialNumber=0
usb.c: unhandled interfaces on device
usb.c: This device is not recognized by any installed USB driver.
Length = 18
DescriptorType = 01
USB version = 1.00
Vendor:Product = 05a9:0511
MaxPacketSize0 = 8
NumConfigurations = 1
Device version = 1.00
Device Class:SubClass:Protocol = 00:00:00
Per-interface classes
Configuration:
bLength = 9
bDescriptorType = 02
wTotalLength = 0089
bNumInterfaces = 01
bConfigurationValue = 01
iConfiguration = 00
bmAttributes = 80
MaxPower = 500mA
Interface: 0
Alternate Setting: 0
bLength = 9
bDescriptorType = 04
bInterfaceNumber = 00
bAlternateSetting = 00
bNumEndpoints = 01
bInterface Class:SubClass:Protocol = ff:00:00
iInterface = 00
Endpoint:
bLength = 7
bDescriptorType = 05
bEndpointAddress = 81 (in)
bmAttributes = 01 (Isochronous)
wMaxPacketSize = 03e0
bInterval = 01
Alternate Setting: 1
bLength = 9
bDescriptorType = 04
bInterfaceNumber = 00
bAlternateSetting = 01
bNumEndpoints = 01
bInterface Class:SubClass:Protocol = ff:00:00
iInterface = 00
Endpoint:
bLength = 7
bDescriptorType = 05
bEndpointAddress = 81 (in)
bmAttributes = 01 (Isochronous)
wMaxPacketSize = 03e1
bInterval = 01
Alternate Setting: 2
bLength = 9
bDescriptorType = 04
bInterfaceNumber = 00
bAlternateSetting = 02
bNumEndpoints = 01
bInterface Class:SubClass:Protocol = ff:00:00
iInterface = 00
Endpoint:
bLength = 7
bDescriptorType = 05
bEndpointAddress = 81 (in)
bmAttributes = 01 (Isochronous)
wMaxPacketSize = 0300
bInterval = 01
Alternate Setting: 3
bLength = 9
bDescriptorType = 04
bInterfaceNumber = 00
bAlternateSetting = 03
bNumEndpoints = 01
bInterface Class:SubClass:Protocol = ff:00:00
iInterface = 00
Endpoint:
bLength = 7
bDescriptorType = 05
bEndpointAddress = 81 (in)
bmAttributes = 01 (Isochronous)
wMaxPacketSize = 0301
bInterval = 01
Alternate Setting: 4
bLength = 9
bDescriptorType = 04
bInterfaceNumber = 00
bAlternateSetting = 04
bNumEndpoints = 01
bInterface Class:SubClass:Protocol = ff:00:00
iInterface = 00
Endpoint:
bLength = 7
bDescriptorType = 05
bEndpointAddress = 81 (in)
bmAttributes = 01 (Isochronous)
wMaxPacketSize = 0200
bInterval = 01
Alternate Setting: 5
bLength = 9
bDescriptorType = 04
bInterfaceNumber = 00
bAlternateSetting = 05
bNumEndpoints = 01
bInterface Class:SubClass:Protocol = ff:00:00
iInterface = 00
Endpoint:
bLength = 7
bDescriptorType = 05
bEndpointAddress = 81 (in)
bmAttributes = 01 (Isochronous)
wMaxPacketSize = 0201
bInterval = 01
Alternate Setting: 6
bLength = 9
bDescriptorType = 04
bInterfaceNumber = 00
bAlternateSetting = 06
bNumEndpoints = 01
bInterface Class:SubClass:Protocol = ff:00:00
iInterface = 00
Endpoint:
bLength = 7
bDescriptorType = 05
bEndpointAddress = 81 (in)
bmAttributes = 01 (Isochronous)
wMaxPacketSize = 0101
bInterval = 01
Alternate Setting: 7
bLength = 9
bDescriptorType = 04
bInterfaceNumber = 00
bAlternateSetting = 07
bNumEndpoints = 01
bInterface Class:SubClass:Protocol = ff:00:00
iInterface = 00
Endpoint:
bLength = 7
bDescriptorType = 05
bEndpointAddress = 81 (in)
bmAttributes = 01 (Isochronous)
wMaxPacketSize = 0000
bInterval = 01
hdd4
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
scsi : 0 hosts.
scsi : detected total.
Serial driver version 4.93 (2000-03-20) with MANY_PORTS SHARE_IRQ
SERIAL_PCI ISAPNP enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at port 0x02f8 (irq = 3) is a 16550A
PPP generic driver version 2.4.1
Linux Tulip driver version 0.9.4.2 (Mar 21, 2000)
eth0: Digital DS21143 Tulip rev 65 at 0x2000, 00:40:D0:00:C8:13, IRQ 11.
eth0: EEPROM default media type Autosense.
eth0: Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY (2)
block.
eth0: Index #1 - Media 10baseT-FD (#4) described by a 21142 Serial PHY
(2) block.
PPP Deflate Compression module registered
[drm] Initialized tdfx 0.0.1 19991009 on minor 63
kmem_create: Forcing size word alignment - nfs_fh
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 164k freed
Adding Swap: 68000k swap-space (priority -1)
From Peter_Pregler@email.com Mon, 17 Apr 2000 10:28:19 +0200
Date: Mon, 17 Apr 2000 10:28:19 +0200
From: Peter Pregler Peter_Pregler@email.com
Subject: [cpia] Aiptek HyperVcam Fun
On Sun, Apr 16, 2000 at 10:29:24PM -0400, Joseph C. Kopec wrote:
> As mentioned in my earlier message, I have been having some problems
> getting the Aiptek HyperVcam Fun webcam to operate, though it is
> mentioned among the CPiA USB cameras on the webcam.sourceforge.net
> site. Has anyone managed to get this to work under Linux with the cpia
> software? When I boot up, I get the attached messages in dmesg --
> basically, it says "usb.c: This device is not recognized by any
> installed USB driver."
> usb.c: This device is not recognized by any installed USB driver.
> Length = 18
> DescriptorType = 01
> USB version = 1.00
> Vendor:Product = 05a9:0511
The vendor-id of the cpia-chip is 0553. So I guess it is not a
cpia-based camera.
-Peter
--
I will not waste chalk. --Bart Simpson at the blackboard
--------------------------------------------------------
Email: Peter_Pregler@email.com
WWW: http://www.risc.uni-linz.ac.at/people/ppregler
From Peter_Pregler@email.com Mon, 17 Apr 2000 15:50:27 +0200
Date: Mon, 17 Apr 2000 15:50:27 +0200
From: Peter Pregler Peter_Pregler@email.com
Subject: [cpia] Aiptek HyperVcam Fun
On Mon, Apr 17, 2000 at 10:28:19AM +0200, Peter Pregler wrote:
> On Sun, Apr 16, 2000 at 10:29:24PM -0400, Joseph C. Kopec wrote:
> > As mentioned in my earlier message, I have been having some problems
> > getting the Aiptek HyperVcam Fun webcam to operate, though it is
> > mentioned among the CPiA USB cameras on the webcam.sourceforge.net
> > site. Has anyone managed to get this to work under Linux with the cpia
> > software? When I boot up, I get the attached messages in dmesg --
> > basically, it says "usb.c: This device is not recognized by any
> > installed USB driver."
>
> > usb.c: This device is not recognized by any installed USB driver.
> > Length = 18
> > DescriptorType = 01
> > USB version = 1.00
> > Vendor:Product = 05a9:0511
>
> The vendor-id of the cpia-chip is 0553. So I guess it is not a
> cpia-based camera.
I just scanned some source-code and saw that your Vendor:Product
matches the OV511 chip. So the Webcam III driver (don't know how they
called it) in the 2.3-something kernels should work. Can anyone
confirm why this camera is listed as CPiA-based? Are there different
versions?
-Peter
--
I will not waste chalk. --Bart Simpson at the blackboard
--------------------------------------------------------
Email: Peter_Pregler@email.com
WWW: http://www.risc.uni-linz.ac.at/people/ppregler
From jto@domino.bdc.no Mon, 17 Apr 2000 17:11:41 +0200
Date: Mon, 17 Apr 2000 17:11:41 +0200
From: Jarl Totland jto@domino.bdc.no
Subject: [cpia] Aiptek HyperVcam Fun
At 15:50 2000-04-17 +0200, Peter_Pregler@email.com wrote:
>I just scanned some source-code and saw that your Vendor:Product
>matches the OV511 chip. So the Webcam III driver (don't know how they
>called it) in the 2.3-something kernels should work. Can anyone
>confirm why this camera is listed as CPiA-based? Are there different
>versions?
According to John Roark 2000-02-18:
> I have gotten my Aiptek Hyper Vcam Fun to work with the usbcore,
> usb-uhci, videodev, and cpia modules in kernel 2.3.42.
Probably just a mixup. I've removed it from the homepage for now.
Vyrdsamt,
-Jarl
From srainwater@ncc.com Mon, 17 Apr 2000 10:28:26 -0500
Date: Mon, 17 Apr 2000 10:28:26 -0500
From: R. Steven Rainwater srainwater@ncc.com
Subject: [cpia] 2.3.99-pre5 doesn't recognize USB Zoom CPiA camera
I've got a Zoom CPiA camera that worked fine with the
last 2.3.x kernel I tried (this was before the 2.3.99pre
series and prior to the merge between the USB and par
CPiA drivers).
I just downloaded the lastest kernel and found that my
Zoom CPiA no is longer recognized. The message I get is:
"This device is not recognized by any installed USB driver"
I've compiled the kernel with USB support for the correct
chipset, with video support, and with the CPiA and CPiA
USB lowlevel support. All were compiled in static rather
than as modules.
Any advice?
Heres the debug info from the system log:
Apr 17 15:14:16 dev kernel: usb.c: USB new device connect, assigned device number 2
Apr 17 15:14:16 dev kernel: usb.c: This device is not recognized by any installed USB driver.
Apr 17 15:14:16 dev kernel: Length = 18
Apr 17 15:14:16 dev kernel: DescriptorType = 01
Apr 17 15:14:16 dev kernel: USB version = 1.00
Apr 17 15:14:16 dev kernel: Vendor:Product = 0553:0002
Apr 17 15:14:16 dev kernel: MaxPacketSize0 = 8
Apr 17 15:14:16 dev kernel: NumConfigurations = 1
Apr 17 15:14:16 dev kernel: Device version = 1.00
Apr 17 15:14:16 dev kernel: Device Class:SubClass:Protocol = 00:00:00
Apr 17 15:14:16 dev kernel: Per-interface classes
Apr 17 15:14:16 dev kernel: Configuration:
Apr 17 15:14:16 dev kernel: bLength = 9
Apr 17 15:14:16 dev kernel: bDescriptorType = 02
Apr 17 15:14:16 dev kernel: wTotalLength = 0049
Apr 17 15:14:16 dev kernel: bNumInterfaces = 01
Apr 17 15:14:16 dev kernel: bConfigurationValue = 01
Apr 17 15:14:16 dev kernel: iConfiguration = 00
Apr 17 15:14:16 dev kernel: bmAttributes = 80
Apr 17 15:14:16 dev kernel: MaxPower = 400mA
Apr 17 15:14:16 dev kernel:
Apr 17 15:14:16 dev kernel: Interface: 0
Apr 17 15:14:16 dev kernel: Alternate Setting: 0
Apr 17 15:14:16 dev kernel: bLength = 9
Apr 17 15:14:16 dev kernel: bDescriptorType = 04
Apr 17 15:14:16 dev kernel: bInterfaceNumber = 01
Apr 17 15:14:16 dev kernel: bAlternateSetting = 00
Apr 17 15:14:16 dev kernel: bNumEndpoints = 01
Apr 17 15:14:16 dev kernel: bInterface Class:SubClass:Protocol = ff:00:ff
Apr 17 15:14:16 dev kernel: iInterface = 00
Apr 17 15:14:16 dev kernel: Endpoint:
Apr 17 15:14:16 dev kernel: bLength = 7
Apr 17 15:14:16 dev kernel: bDescriptorType = 05
Apr 17 15:14:16 dev kernel: bEndpointAddress = 81 (in)
Apr 17 15:14:16 dev kernel: bmAttributes = 01 (Isochronous)
Apr 17 15:14:16 dev kernel: wMaxPacketSize = 0000
Apr 17 15:14:16 dev kernel: bInterval = 01
Apr 17 15:14:16 dev kernel: Alternate Setting: 1
Apr 17 15:14:16 dev kernel: bLength = 9
Apr 17 15:14:16 dev kernel: bDescriptorType = 04
Apr 17 15:14:16 dev kernel: bInterfaceNumber = 01
Apr 17 15:14:16 dev kernel: bAlternateSetting = 01
Apr 17 15:14:16 dev kernel: bNumEndpoints = 01
Apr 17 15:14:16 dev kernel: bInterface Class:SubClass:Protocol = ff:00:ff
Apr 17 15:14:16 dev kernel: iInterface = 00
Apr 17 15:14:16 dev kernel: Endpoint:
Apr 17 15:14:16 dev kernel: bLength = 7
Apr 17 15:14:16 dev kernel: bDescriptorType = 05
Apr 17 15:14:16 dev kernel: bEndpointAddress = 81 (in)
Apr 17 15:14:16 dev kernel: bmAttributes = 01 (Isochronous)
Apr 17 15:14:16 dev kernel: wMaxPacketSize = 01c0
Apr 17 15:14:16 dev kernel: bInterval = 01
Apr 17 15:14:16 dev kernel: Alternate Setting: 2
Apr 17 15:14:16 dev kernel: bLength = 9
Apr 17 15:14:16 dev kernel: bDescriptorType = 04
Apr 17 15:14:16 dev kernel: bInterfaceNumber = 01
Apr 17 15:14:16 dev kernel: bAlternateSetting = 02
Apr 17 15:14:16 dev kernel: bNumEndpoints = 01
Apr 17 15:14:16 dev kernel: bInterface Class:SubClass:Protocol = ff:00:ff
Apr 17 15:14:16 dev kernel: iInterface = 00
Apr 17 15:14:16 dev kernel: Endpoint:
Apr 17 15:14:16 dev kernel: bLength = 7
Apr 17 15:14:16 dev kernel: bDescriptorType = 05
Apr 17 15:14:16 dev kernel: bEndpointAddress = 81 (in)
Apr 17 15:14:16 dev kernel: bmAttributes = 01 (Isochronous)
Apr 17 15:14:16 dev kernel: wMaxPacketSize = 02c0
Apr 17 15:14:16 dev kernel: bInterval = 01
Apr 17 15:14:16 dev kernel: Alternate Setting: 3
Apr 17 15:14:16 dev kernel: bLength = 9
Apr 17 15:14:16 dev kernel: bDescriptorType = 04
Apr 17 15:14:16 dev kernel: bInterfaceNumber = 01
Apr 17 15:14:16 dev kernel: bAlternateSetting = 03
Apr 17 15:14:16 dev kernel: bNumEndpoints = 01
Apr 17 15:14:16 dev kernel: bInterface Class:SubClass:Protocol = ff:00:ff
Apr 17 15:14:16 dev kernel: iInterface = 00
Apr 17 15:14:16 dev kernel: Endpoint:
Apr 17 15:14:16 dev kernel: bLength = 7
Apr 17 15:14:16 dev kernel: bDescriptorType = 05
Apr 17 15:14:16 dev kernel: bEndpointAddress = 81 (in)
Apr 17 15:14:16 dev kernel: bmAttributes = 01 (Isochronous)
Apr 17 15:14:16 dev kernel: wMaxPacketSize = 03c0
Apr 17 15:14:16 dev kernel: bInterval = 01
From eggles@rsch.comm.mot.com Mon, 17 Apr 2000 11:29:06 -0500
Date: Mon, 17 Apr 2000 11:29:06 -0500
From: Joseph Eggleston eggles@rsch.comm.mot.com
Subject: [cpia] compaq armada 7800
I'm trying to get the webcam II to work under kernel 2.2.14-5 on a
Compaq Armada 7800 (laptop). The BIOS calls the parallel port an "ECP
printer port" but for some reason linux doesn't recognize it as such.
Here's the relevant log info:
parport0: PC-style at 0x378 [SPP,PS2]
parport0: read2 timeout.
parport0: Multimedia device, VLSI Vision Ltd PPC2 Camera
Linux video capture interface: v1.00
V4L-Driver for Vision CPiA based cameras v0.7.4
Parallel port driver for Vision CPiA based cameras v0.7.4
cpia_pp.c:cpia_pp_register(1469):port is not ECP capable
0 camera(s) found
Does anyone have experience with this problem? Which is lying to me, the
BIOS or the kernel?
thanks,
Joe
From jerdfelt@sventech.com Mon, 17 Apr 2000 12:46:00 -0400
Date: Mon, 17 Apr 2000 12:46:00 -0400
From: Johannes Erdfelt jerdfelt@sventech.com
Subject: [cpia] 2.3.99-pre5 doesn't recognize USB Zoom CPiA camera
I bet you the CPiA USB support won't work statically since the USB core
doesn't know about the drivers outside of it's tree. I'm sure if you
compile everything dynamically (as modules) it will work.
JE
On Mon, Apr 17, 2000, R. Steven Rainwater wrote:
> I've got a Zoom CPiA camera that worked fine with the
> last 2.3.x kernel I tried (this was before the 2.3.99pre
> series and prior to the merge between the USB and par
> CPiA drivers).
>
> I just downloaded the lastest kernel and found that my
> Zoom CPiA no is longer recognized. The message I get is:
>
> "This device is not recognized by any installed USB driver"
>
> I've compiled the kernel with USB support for the correct
> chipset, with video support, and with the CPiA and CPiA
> USB lowlevel support. All were compiled in static rather
> than as modules.
>
> Any advice?
>
> Heres the debug info from the system log:
>
> Apr 17 15:14:16 dev kernel: usb.c: USB new device connect, assigned device number 2
> Apr 17 15:14:16 dev kernel: usb.c: This device is not recognized by any installed USB driver.
> Apr 17 15:14:16 dev kernel: Length = 18
> Apr 17 15:14:16 dev kernel: DescriptorType = 01
> Apr 17 15:14:16 dev kernel: USB version = 1.00
> Apr 17 15:14:16 dev kernel: Vendor:Product = 0553:0002
> Apr 17 15:14:16 dev kernel: MaxPacketSize0 = 8
> Apr 17 15:14:16 dev kernel: NumConfigurations = 1
> Apr 17 15:14:16 dev kernel: Device version = 1.00
> Apr 17 15:14:16 dev kernel: Device Class:SubClass:Protocol = 00:00:00
> Apr 17 15:14:16 dev kernel: Per-interface classes
> Apr 17 15:14:16 dev kernel: Configuration:
> Apr 17 15:14:16 dev kernel: bLength = 9
> Apr 17 15:14:16 dev kernel: bDescriptorType = 02
> Apr 17 15:14:16 dev kernel: wTotalLength = 0049
> Apr 17 15:14:16 dev kernel: bNumInterfaces = 01
> Apr 17 15:14:16 dev kernel: bConfigurationValue = 01
> Apr 17 15:14:16 dev kernel: iConfiguration = 00
> Apr 17 15:14:16 dev kernel: bmAttributes = 80
> Apr 17 15:14:16 dev kernel: MaxPower = 400mA
> Apr 17 15:14:16 dev kernel:
> Apr 17 15:14:16 dev kernel: Interface: 0
> Apr 17 15:14:16 dev kernel: Alternate Setting: 0
> Apr 17 15:14:16 dev kernel: bLength = 9
> Apr 17 15:14:16 dev kernel: bDescriptorType = 04
> Apr 17 15:14:16 dev kernel: bInterfaceNumber = 01
> Apr 17 15:14:16 dev kernel: bAlternateSetting = 00
> Apr 17 15:14:16 dev kernel: bNumEndpoints = 01
> Apr 17 15:14:16 dev kernel: bInterface Class:SubClass:Protocol = ff:00:ff
> Apr 17 15:14:16 dev kernel: iInterface = 00
> Apr 17 15:14:16 dev kernel: Endpoint:
> Apr 17 15:14:16 dev kernel: bLength = 7
> Apr 17 15:14:16 dev kernel: bDescriptorType = 05
> Apr 17 15:14:16 dev kernel: bEndpointAddress = 81 (in)
> Apr 17 15:14:16 dev kernel: bmAttributes = 01 (Isochronous)
> Apr 17 15:14:16 dev kernel: wMaxPacketSize = 0000
> Apr 17 15:14:16 dev kernel: bInterval = 01
> Apr 17 15:14:16 dev kernel: Alternate Setting: 1
> Apr 17 15:14:16 dev kernel: bLength = 9
> Apr 17 15:14:16 dev kernel: bDescriptorType = 04
> Apr 17 15:14:16 dev kernel: bInterfaceNumber = 01
> Apr 17 15:14:16 dev kernel: bAlternateSetting = 01
> Apr 17 15:14:16 dev kernel: bNumEndpoints = 01
> Apr 17 15:14:16 dev kernel: bInterface Class:SubClass:Protocol = ff:00:ff
> Apr 17 15:14:16 dev kernel: iInterface = 00
> Apr 17 15:14:16 dev kernel: Endpoint:
> Apr 17 15:14:16 dev kernel: bLength = 7
> Apr 17 15:14:16 dev kernel: bDescriptorType = 05
> Apr 17 15:14:16 dev kernel: bEndpointAddress = 81 (in)
> Apr 17 15:14:16 dev kernel: bmAttributes = 01 (Isochronous)
> Apr 17 15:14:16 dev kernel: wMaxPacketSize = 01c0
> Apr 17 15:14:16 dev kernel: bInterval = 01
> Apr 17 15:14:16 dev kernel: Alternate Setting: 2
> Apr 17 15:14:16 dev kernel: bLength = 9
> Apr 17 15:14:16 dev kernel: bDescriptorType = 04
> Apr 17 15:14:16 dev kernel: bInterfaceNumber = 01
> Apr 17 15:14:16 dev kernel: bAlternateSetting = 02
> Apr 17 15:14:16 dev kernel: bNumEndpoints = 01
> Apr 17 15:14:16 dev kernel: bInterface Class:SubClass:Protocol = ff:00:ff
> Apr 17 15:14:16 dev kernel: iInterface = 00
> Apr 17 15:14:16 dev kernel: Endpoint:
> Apr 17 15:14:16 dev kernel: bLength = 7
> Apr 17 15:14:16 dev kernel: bDescriptorType = 05
> Apr 17 15:14:16 dev kernel: bEndpointAddress = 81 (in)
> Apr 17 15:14:16 dev kernel: bmAttributes = 01 (Isochronous)
> Apr 17 15:14:16 dev kernel: wMaxPacketSize = 02c0
> Apr 17 15:14:16 dev kernel: bInterval = 01
> Apr 17 15:14:16 dev kernel: Alternate Setting: 3
> Apr 17 15:14:16 dev kernel: bLength = 9
> Apr 17 15:14:16 dev kernel: bDescriptorType = 04
> Apr 17 15:14:16 dev kernel: bInterfaceNumber = 01
> Apr 17 15:14:16 dev kernel: bAlternateSetting = 03
> Apr 17 15:14:16 dev kernel: bNumEndpoints = 01
> Apr 17 15:14:16 dev kernel: bInterface Class:SubClass:Protocol = ff:00:ff
> Apr 17 15:14:16 dev kernel: iInterface = 00
> Apr 17 15:14:16 dev kernel: Endpoint:
> Apr 17 15:14:16 dev kernel: bLength = 7
> Apr 17 15:14:16 dev kernel: bDescriptorType = 05
> Apr 17 15:14:16 dev kernel: bEndpointAddress = 81 (in)
> Apr 17 15:14:16 dev kernel: bmAttributes = 01 (Isochronous)
> Apr 17 15:14:16 dev kernel: wMaxPacketSize = 03c0
> Apr 17 15:14:16 dev kernel: bInterval = 01
>
>
>
>
>
> _______________________________________________
> cpia mailing list - cpia@risc.uni-linz.ac.at
> http://mailman.risc.uni-linz.ac.at/mailman/cgi-bin/listinfo/cpia
>
From kopecjc@att.net Mon, 17 Apr 2000 21:55:38 -0400
Date: Mon, 17 Apr 2000 21:55:38 -0400
From: Joseph C. Kopec kopecjc@att.net
Subject: [cpia] 2.3.99-pre5 and EZCam USB
I swapped my Aiptek (which Peter Pregler informs me was wrongly thought
to be a CPiA-based camera) for a Ezonics EZCam USB (not a Pro or a
Plus), but I am still having a hard time getting it to work with
2.3.99-pre5 -- my dmesg file is attached. First the good news -- its
Vendor:Product code is 0553:0002, which appears to be a good CPiA. But
it still does not get recognized. Note that I compiled everything into
the kernel -- Johannes Erdfelt stated in an earlier message:
"I bet you the CPiA USB support won't work statically since the USB core
doesn't know about the drivers outside of it's tree. I'm sure if you
compile everything dynamically (as modules) it will work."
I guess I will give modules a shot. By "everything" did he mean
usb-uhci, cpia, video4linux, usb preliminary filesystem ... what else?
Any suggestions would be much appreciated.
***********************
Linux version 2.3.99-pre5 (root@jck0) (gcc version egcs-2.91.66
19990314/Linux (egcs-1.1.2 release)) #1 Sun Apr 16 21:00:02 EDT 2000
e820: 0009fc00 @ 00000000 (usable)
e820: 00000400 @ 0009fc00 (reserved)
e820: 00010000 @ 000f0000 (reserved)
e820: 05f00000 @ 00100000 (usable)
e820: 00020000 @ fffe0000 (reserved)
On node 0 totalpages: 24576
zone(0): 4096 pages.
zone(1): 20480 pages.
zone(2): 0 pages.
Initializing CPU#0
Detected 397333496 Hz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 792.99 BogoMIPS
Memory: 93764k/98304k available (1590k kernel code, 4152k reserved, 99k
data, 164k init, 0k highmem)
Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes)
Page-cache hash table entries: 32768 (order: 5, 131072 bytes)
CPU: Intel Pentium II (Deschutes) stepping 01
Checking 386/387 coupling... OK, FPU using exception 16 error reporting.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.36 (20000221) Richard Gooch (rgooch@atnf.csiro.au)
PCI: PCI BIOS revision 2.10 entry at 0xfa104, last bus=1
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Using IRQ router PIIX [8086/7000] at 00:14.0
Limiting direct PCI/PCI transfers.
isapnp: Scanning for Pnp cards...
isapnp: Card 'Creative Modem Blaster Flash56 DI5601-1'
isapnp: 1 Plug & Play card detected total
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.228 $ time 21:02:22 Apr 16 2000
usb-uhci.c: High bandwidth mode enabled
usb-uhci.c: Intel USB controller: setting latency timer to 0
usb-uhci.c: USB UHCI at I/O 0x2080, IRQ 11
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
usb.c: USB new device connect, assigned device number 1
usb.c: kmalloc IF c11ba8a0, numif 1
usb.c: new device strings: Mfr=0, Product=2, SerialNumber=1
usb.c: USB device number 1 default language ID 0x0
Product: USB UHCI Root Hub
SerialNumber: 2080
hub.c: USB hub found
hub.c: 2 ports detected
hub.c: ganged power switching
hub.c: standalone hub
hub.c: global over-current protection
hub.c: power on to power good time: 2ms
hub.c: hub controller current requirement: 0mA
hub.c: port 1 is removable
hub.c: port 2 is removable
hub.c: local power source is good
hub.c: no over-current condition exists
hub.c: enabling power on all ports
usb.c: hub driver claimed interface c11ba8a0
Linux NET4.0 for Linux 2.3
Based upon Swansea University Computer Society NET3.039
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 8192 bind 8192)
Initializing RT netlink socket
Starting kswapd v1.6
parport0: PC-style at 0x378 [PCSPP]
pty: 256 Unix98 ptys configured
lp0: using parport0 (polling).
Linux video capture interface: v1.00
V4L-Driver for Vision CPiA based cameras v0.7.4
Uniform Multi-Platform E-IDE driver Revision: 6.30
ide: Assuming 40MHz system bus speed for PIO modes; override with
idebus=xx
PIIX4: IDE controller on PCI bus 00 dev a1
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x20a0-0x20a7, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0x20a8-0x20af, BIOS settings: hdc:DMA, hdd:pio
hda: QUANTUM Bigfoot TX8.0AT, ATA DISK drive
hdc: COMPAQ DVD-ROM GD-2000, ATAPI CDROM drive
hdd: IOMEGA ZIP 100, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: 15698592 sectors (8038 MB) w/69KiB Cache, CHS=1038/240/63
hdd: 196608 sectors (101 MB) w/16KiB Cache, CHS=512/12/32
hub.c: port 2 connection change
hdc: ATAPI 20X DVD-ROM drive, 512kB Cache
Uniform CD-ROM driver Revision: 3.07
Partition check:
hda: hda1 hda2 < hda5 hda6 hda7 >
hdd:<7>hub.c: portstatus 101, change 1, High Speed
hdd4
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
scsi : 0 hosts.
scsi : detected total.
Serial driver version 4.93 (2000-03-20) with MANY_PORTS SHARE_IRQ
SERIAL_PCI ISAPNP enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at port 0x02f8 (irq = 3) is a 16550A
PPP generic driver version 2.4.1
Linux Tulip driver version 0.9.4.2 (Mar 21, 2000)
eth0: Digital DS21143 Tulip rev 65 at 0x2000, 00:40:D0:00:C8:13, IRQ 11.
eth0: EEPROM default media type Autosense.
eth0: Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY (2)
block.
eth0: Index #1 - Media 10baseT-FD (#4) described by a 21142 Serial PHY
(2) block.
PPP Deflate Compression module registered
[drm] Initialized tdfx 0.0.1 19991009 on minor 63
kmem_create: Forcing size word alignment - nfs_fh
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 164k freed
hub.c: portstatus 103, change 0, High Speed
usb.c: USB new device connect, assigned device number 2
usb.c: kmalloc IF c5f9b060, numif 1
usb.c: new device strings: Mfr=0, Product=1, SerialNumber=0
usb.c: USB device number 2 default language ID 0x409
Product: USB Camera
usb.c: unhandled interfaces on device
usb.c: This device is not recognized by any installed USB driver.
Length = 18
DescriptorType = 01
USB version = 1.00
Vendor:Product = 0553:0002
MaxPacketSize0 = 8
NumConfigurations = 1
Device version = 1.00
Device Class:SubClass:Protocol = 00:00:00
Per-interface classes
Configuration:
bLength = 9
bDescriptorType = 02
wTotalLength = 0049
bNumInterfaces = 01
bConfigurationValue = 01
iConfiguration = 00
bmAttributes = 80
MaxPower = 250mA
Interface: 0
Alternate Setting: 0
bLength = 9
bDescriptorType = 04
bInterfaceNumber = 00
bAlternateSetting = 00
bNumEndpoints = 01
bInterface Class:SubClass:Protocol = ff:00:ff
iInterface = 00
Endpoint:
bLength = 7
bDescriptorType = 05
bEndpointAddress = 81 (in)
bmAttributes = 01 (Isochronous)
wMaxPacketSize = 0000
bInterval = 01
Alternate Setting: 1
bLength = 9
bDescriptorType = 04
bInterfaceNumber = 00
bAlternateSetting = 01
bNumEndpoints = 01
bInterface Class:SubClass:Protocol = ff:00:ff
iInterface = 00
Endpoint:
bLength = 7
bDescriptorType = 05
bEndpointAddress = 81 (in)
bmAttributes = 01 (Isochronous)
wMaxPacketSize = 01c0
bInterval = 01
Alternate Setting: 2
bLength = 9
bDescriptorType = 04
bInterfaceNumber = 00
bAlternateSetting = 02
bNumEndpoints = 01
bInterface Class:SubClass:Protocol = ff:00:ff
iInterface = 00
Endpoint:
bLength = 7
bDescriptorType = 05
bEndpointAddress = 81 (in)
bmAttributes = 01 (Isochronous)
wMaxPacketSize = 02c0
bInterval = 01
Alternate Setting: 3
bLength = 9
bDescriptorType = 04
bInterfaceNumber = 00
bAlternateSetting = 03
bNumEndpoints = 01
bInterface Class:SubClass:Protocol = ff:00:ff
iInterface = 00
Endpoint:
bLength = 7
bDescriptorType = 05
bEndpointAddress = 81 (in)
bmAttributes = 01 (Isochronous)
wMaxPacketSize = 03c0
bInterval = 01
Adding Swap: 68000k swap-space (priority -1)
From jerdfelt@valinux.com Mon, 17 Apr 2000 19:15:48 -0700
Date: Mon, 17 Apr 2000 19:15:48 -0700
From: Johannes Erdfelt jerdfelt@valinux.com
Subject: [cpia] 2.3.99-pre5 and EZCam USB
--OpLPJvDmhXTZE4Lg
Content-Type: text/plain; charset=us-ascii
On Mon, Apr 17, 2000, Joseph C. Kopec wrote:
> I swapped my Aiptek (which Peter Pregler informs me was wrongly thought
> to be a CPiA-based camera) for a Ezonics EZCam USB (not a Pro or a
> Plus), but I am still having a hard time getting it to work with
> 2.3.99-pre5 -- my dmesg file is attached. First the good news -- its
> Vendor:Product code is 0553:0002, which appears to be a good CPiA. But
> it still does not get recognized. Note that I compiled everything into
> the kernel -- Johannes Erdfelt stated in an earlier message:
>
> "I bet you the CPiA USB support won't work statically since the USB core
> doesn't know about the drivers outside of it's tree. I'm sure if you
> compile everything dynamically (as modules) it will work."
>
> I guess I will give modules a shot. By "everything" did he mean
> usb-uhci, cpia, video4linux, usb preliminary filesystem ... what else?
>
> Any suggestions would be much appreciated.
What I really meant to say was that I forgot to make one change during the
merge for CPiA to allow CPiA to be compiled into the kernel versus being
a module. This is all my fault :)
Here's the patch.
Randy, could you please submit this.
JE
--OpLPJvDmhXTZE4Lg
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="cpia-usb-init.patch"
--- drivers/usb/usb-core.c.old Mon Apr 17 19:12:31 2000
+++ drivers/usb/usb-core.c Mon Apr 17 19:13:53 2000
@@ -28,6 +28,7 @@
* USB device drivers
*/
+int usb_cpia_init(void);
int usb_audio_init(void);
int usb_ibmcam_init(void);
int dabusb_init(void);
@@ -68,6 +69,9 @@
usb_hub_init();
#ifndef CONFIG_USB_MODULE
+#ifdef CONFIG_VIDEO_CPIA_USB
+ usb_cpia_init();
+#endif
#ifdef CONFIG_USB_AUDIO
usb_audio_init();
#endif
--OpLPJvDmhXTZE4Lg--
From jerdfelt@valinux.com Mon, 17 Apr 2000 19:21:31 -0700
Date: Mon, 17 Apr 2000 19:21:31 -0700
From: Johannes Erdfelt jerdfelt@valinux.com
Subject: [cpia] [patch] semaphore deadlock
--YhFoJY/gx7awiIuK
Content-Type: text/plain; charset=us-ascii
This is actually a bug I found a little while ago, but I forgot to send
to the list.
Well, I ran into it again and fixed it again.
In do_command, we down a semaphore, but don't up it if the command failed.
For some reason, one of my cameras fails (STALLs the control pipe) every
so often, triggering this bug.
This will up the semaphore in the error path.
It also fixes a minor nit in the beginning for cpia_usb.c :)
I'll submit something like this for the 2.3 version. Can someone submit the
patch for 2.2?
JE
--YhFoJY/gx7awiIuK
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="cpia-sema-fix.patch"
Index: module/cpia.c
===================================================================
RCS file: /cvsroot/webcam/cpia/module/cpia.c,v
retrieving revision 0.12
diff -u -r0.12 cpia.c
--- module/cpia.c 2000/04/17 14:53:40 0.12
+++ module/cpia.c 2000/04/18 02:18:06
@@ -1688,9 +1688,13 @@
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 {
+ if (command == CPIA_COMMAND_GetColourParams ||
+ command == CPIA_COMMAND_GetColourBalance ||
+ command == CPIA_COMMAND_GetExposure)
+ up(&cam->param_lock);
+ } else {
switch(command) {
case CPIA_COMMAND_GetCPIAVersion:
cam->params.version.firmwareVersion = data[0];
Index: module/cpia_usb.c
===================================================================
RCS file: /cvsroot/webcam/cpia/module/cpia_usb.c,v
retrieving revision 0.10
diff -u -r0.10 cpia_usb.c
--- module/cpia_usb.c 2000/04/17 14:53:40 0.10
+++ module/cpia_usb.c 2000/04/18 02:18:06
@@ -1,5 +1,5 @@
/*
- * cpia_pp CPiA USB driver
+ * cpia_usb CPiA USB driver
*
* Supports CPiA based parallel port Video Camera's.
*
--YhFoJY/gx7awiIuK--
From Peter_Pregler@email.com Tue, 18 Apr 2000 08:31:37 +0200
Date: Tue, 18 Apr 2000 08:31:37 +0200
From: Peter Pregler Peter_Pregler@email.com
Subject: [cpia] compaq armada 7800
On Mon, Apr 17, 2000 at 11:29:06AM -0500, Joseph Eggleston wrote:
> I'm trying to get the webcam II to work under kernel 2.2.14-5 on a
> Compaq Armada 7800 (laptop). The BIOS calls the parallel port an "ECP
> printer port" but for some reason linux doesn't recognize it as such.
> Here's the relevant log info:
>
> parport0: PC-style at 0x378 [SPP,PS2]
> parport0: read2 timeout.
> parport0: Multimedia device, VLSI Vision Ltd PPC2 Camera
> Linux video capture interface: v1.00
> V4L-Driver for Vision CPiA based cameras v0.7.4
> Parallel port driver for Vision CPiA based cameras v0.7.4
> cpia_pp.c:cpia_pp_register(1469):port is not ECP capable
> 0 camera(s) found
>
> Does anyone have experience with this problem? Which is lying to me, the
> BIOS or the kernel?
Maybe you better ask the parport-people. As long as ECP is not in the
[SPP,PS]-list there is nothing the cpia-driver can do. Also check out
the compaq-pages. AFAIR they have nice white-papers describing how to
setup linux on some of their laptops.
-Peter
--
I will not waste chalk. --Bart Simpson at the blackboard
--------------------------------------------------------
Email: Peter_Pregler@email.com
WWW: http://www.risc.uni-linz.ac.at/people/ppregler
From root@mail.velenje.cx Tue, 18 Apr 2000 10:19:16 +0200 (CEST)
Date: Tue, 18 Apr 2000 10:19:16 +0200 (CEST)
From: Samo Gabrovec root@mail.velenje.cx
Subject: [cpia] Motion detection
I know that this is a bit off topic but here it goes.
does anyone know if there is any software that could do motion detection
with kamera that uses cpia.
Thanks.
Samo Gabrovec
----------------------------------------------------------------
PC! Politically Correct (or) Pure Crap!
----------------------------------------------------------------
Visit http://www.velenje.cx
----------------------------------------------------------------
From root@mail.velenje.cx Tue, 18 Apr 2000 21:50:42 +0200 (CEST)
Date: Tue, 18 Apr 2000 21:50:42 +0200 (CEST)
From: Samo Gabrovec root@mail.velenje.cx
Subject: [cpia] Fatal error
1. I would like to tell that i had a working setup with webcam II for at
least 2 months. I didn`t change anything except i rebooted.
Is my camera broken?
the modules load like they should but when i try to run a program like
gqcam it says: /dev/video: Input/output error
and in the logs i get :cpia.c(18780):reset_camera(2475):fatal_error:
0x20
what is this fatal error?
i have included which modules i have loaded, log file, cat
/proc/cpia/video0 belove.
Please tell me what could be wrong (so that i`ll know to wheather to
throw tha cam away or not)
Samo Gabrovec
thanks
===============================================================
modules loaded
--------
mail:~ # lsmod
Module Size Used by
cpia_pp 17436 0
cpia 49344 0 [cpia_pp]
videodev 2496 1 [cpia]
parport_pc 5744 1
parport 6716 1 [cpia_pp parport_pc]
es1371 25888 0 (autoclean)
soundcore 2336 4 (autoclean) [es1371]
3c59x 19008 1 (autoclean)
serial 42932 1 (autoclean)
memstat 1604 0 (unused)
---------
messages
---------
Apr 18 21:14:36 mail kernel: parport0: PC-style at 0x378, irq 7, dma 3
[SPP,ECP,ECPEPP,ECPPS2]
Apr 18 21:14:36 mail kernel: parport1: PC-style at 0x278 [SPP]
Apr 18 21:14:45 mail kernel: Linux video capture interface: v1.00
Apr 18 21:14:55 mail kernel: V4L-Driver for Vision CPiA based cameras
v0.7.4
Apr 18 21:14:55 mail modprobe: modprobe: Can't locate module cpia_pp
Apr 18 21:15:01 mail kernel: Parallel port driver for Vision CPiA based
cameras v0.7.4
Apr 18 21:15:01 mail kernel: using DMA mode (irq 7, DMA 3)
Apr 18 21:15:01 mail kernel: cpia.c(18772):goto_low_power(2338):camera now
in LOW power state
Apr 18 21:15:01 mail kernel: cpia.c(18780):goto_high_power(2324):camera
now in HIGH power state
Apr 18 21:15:01 mail kernel: cpia.c(18780):reset_camera(2475):fatal_error:
0x20
Apr 18 21:15:01 mail kernel: cpia.c(18780):reset_camera(2477):vp_status:
0x01
Apr 18 21:15:01 mail kernel: cpia_pp.c:cpia_pp_register(1469):port is not
ECP capable
Apr 18 21:15:01 mail kernel: 1 camera(s) found
Apr 18 21:15:07 mail kernel: cpia.c(19342):goto_low_power(2338):camera now
in LOW power state
Apr 18 21:15:07 mail kernel: cpia.c(19349):goto_high_power(2324):camera
now in HIGH power state
Apr 18 21:15:07 mail kernel: cpia.c(19349):reset_camera(2475):fatal_error:
0x20
Apr 18 21:15:07 mail kernel: cpia.c(19349):reset_camera(2477):vp_status:
0x01
---------
mail:~ # gqcam
/dev/video: Input/output error
--------
cat /proc/cpia/video0
-------
mail:/proc/cpia # cat video0
read-only
-----------------------
CPIA Version: 1.02 (1.0)
CPIA PnP-ID: 0553:0001:0100
VP-Version: 0.0 0000
system_state: 0x03
grab_state: 0x01
stream_state: 0x00
fatal_error: 0x20
cmd_error: 0x01
debug_flags: 0x00
vp_status: 0x01
error_code: 0x00
video_size: CIF
sub_sample: 422
yuv_order: YUYV
roi: ( 0, 0) to (352, 288)
actual_fps: 0
transfer_rate: 0kB/s
read-write
----------------------- current min max default comment
brightness: 50 0 100 50
contrast: 48 0 80 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 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 255 0
coarse_exp: 185 0 255 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: 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
mail:/proc/cpia #
----------------------------------------------------------------
PC! Politically Correct (or) Pure Crap!
----------------------------------------------------------------
Visit http://www.velenje.cx
----------------------------------------------------------------
From Peter.Pregler@risc.uni-linz.ac.at Wed, 19 Apr 2000 08:43:45 +0200
Date: Wed, 19 Apr 2000 08:43:45 +0200
From: Peter Pregler Peter.Pregler@risc.uni-linz.ac.at
Subject: [cpia] Fatal error
On Tue, Apr 18, 2000 at 09:50:42PM +0200, Samo Gabrovec wrote:
> 1. I would like to tell that i had a working setup with webcam II for at
> least 2 months. I didn`t change anything except i rebooted.
> Is my camera broken?
> the modules load like they should but when i try to run a program like
> gqcam it says: /dev/video: Input/output error
> and in the logs i get :cpia.c(18780):reset_camera(2475):fatal_error:
> 0x20
> what is this fatal error?
IIRC this means that the VP cannot be powered on. In case of a parport
camera this usually happens if the camera is connected to the parallel
port but not to the keyboad (i.e. no power).
-Peter
--
Email: Peter.Pregler@risc.uni-linz.ac.at
WWW: http://www.risc.uni-linz.ac.at/people/ppregler
From root@mail.velenje.cx Wed, 19 Apr 2000 09:16:23 +0200 (CEST)
Date: Wed, 19 Apr 2000 09:16:23 +0200 (CEST)
From: Samo Gabrovec root@mail.velenje.cx
Subject: [cpia] Fatal error
Aha than there`s a fault in the camera cable.... because it`s connected to
the keyboard (i`m typeing ;))
i`ll take a look into the cable.
Thanks!!!
----------------------------------------------------------------
The way to a man's heart is through the left ventricle.
----------------------------------------------------------------
Visit http://www.velenje.cx
----------------------------------------------------------------
On Wed, 19 Apr 2000, Peter Pregler wrote:
> On Tue, Apr 18, 2000 at 09:50:42PM +0200, Samo Gabrovec wrote:
> > 1. I would like to tell that i had a working setup with webcam II for at
> > least 2 months. I didn`t change anything except i rebooted.
> > Is my camera broken?
> > the modules load like they should but when i try to run a program like
> > gqcam it says: /dev/video: Input/output error
> > and in the logs i get :cpia.c(18780):reset_camera(2475):fatal_error:
> > 0x20
> > what is this fatal error?
>
> IIRC this means that the VP cannot be powered on. In case of a parport
> camera this usually happens if the camera is connected to the parallel
> port but not to the keyboad (i.e. no power).
>
> -Peter
>
> --
> Email: Peter.Pregler@risc.uni-linz.ac.at
> WWW: http://www.risc.uni-linz.ac.at/people/ppregler
>
From zort@penrithcity.nsw.gov.au Wed, 19 Apr 2000 17:43:44 +1000
Date: Wed, 19 Apr 2000 17:43:44 +1000
From: Dean Hamstead zort@penrithcity.nsw.gov.au
Subject: [cpia] logitech quick cam
Info seems shectchy in this area, however i get the impression
logitech is holding out on info.
However im extremely interested in working with any developers to
get it working. Even if its being reverse engineered.
Im currently on the v3tv devel team (but am awaiting code so i can
start to unleesh this beast)
all the best
Dean
--
BONG: http://bong.pnc.com.au
LANZAC: http://bong.pnc.com.au/lanzac
EMAIL: dean@penrithcity.nsw.gov.au
zort@penrithcity.nsw.gov.au
zort@aussiegamer.com
ICQ: 16867613
From kopecjc@att.net Wed, 19 Apr 2000 22:29:35 -0400
Date: Wed, 19 Apr 2000 22:29:35 -0400
From: Joseph C. Kopec kopecjc@att.net
Subject: [cpia] Ezonics EZCam Success Story (More or Less)
Putting cpia and cpia_usb in modules under 2.3.99-pre5 solved my
problems, and I was able to get gqcam to display beautiful color video
of me typing away -- many thanks to all who have made this possible!
Several points to note:
1. cpia-control failed with a Python error in some function with
"float" in its name -- I will try to get the full error message next
time it comes up.
2. In upgrading to 2.3.99-pre5 from 2.2.12-20, I found that ppp became
non-functional, and to resolve this I had to upgrade to version 2.3.11
of ppp.
3. gqcam displays a "kernel: shmget: shm filesystem not mounted"
message upon launch but appears to work (but see next item).
4. Like George Talusan, I also experienced several failures of gqcam
with "usb-uchi.c: interrupt, status 2, frame# ____" messages sent to
log. Johannes Erdfelt mentioned the Alternate UHCI driver he wrote as
the possible solution -- is this the alternate UHCI option provided in
2.3.99-pre5?
Again, many thanks -- its great to see the progress that is being made
on the hardware/driver front in Linux.
From jerdfelt@sventech.com Wed, 19 Apr 2000 22:47:41 -0400
Date: Wed, 19 Apr 2000 22:47:41 -0400
From: Johannes Erdfelt jerdfelt@sventech.com
Subject: [cpia] Ezonics EZCam Success Story (More or Less)
On Wed, Apr 19, 2000, Joseph C. Kopec wrote:
> Putting cpia and cpia_usb in modules under 2.3.99-pre5 solved my
> problems, and I was able to get gqcam to display beautiful color video
> of me typing away -- many thanks to all who have made this possible!
>
> Several points to note:
>
> 3. gqcam displays a "kernel: shmget: shm filesystem not mounted"
> message upon launch but appears to work (but see next item).
I think you need
mount -t shm none /var/shm
or something similar
> 4. Like George Talusan, I also experienced several failures of gqcam
> with "usb-uchi.c: interrupt, status 2, frame# ____" messages sent to
> log.
That's not always a problem. That UHCI driver is very verbose and shows
all interrupt status' other than the standard interrupt.
That means an error occured, but some errors are normal.
> Johannes Erdfelt mentioned the Alternate UHCI driver he wrote as
> the possible solution -- is this the alternate UHCI option provided in
> 2.3.99-pre5?
Yes it is.
> Again, many thanks -- its great to see the progress that is being made
> on the hardware/driver front in Linux.
Thanks for the feedback. I'm glad to see another success story.
JE
From kopecjc@att.net Fri, 21 Apr 2000 14:50:38 -0400
Date: Fri, 21 Apr 2000 14:50:38 -0400
From: Joseph C. Kopec kopecjc@att.net
Subject: [cpia] shm filesystem (was Ezonics...)
As mentioned earlier, I have been trying out the 2.3.99-pre5 kernel to
get the Ezonics usb webcam to work. I can get video for a while but
then the viewer (a
modified version of gqcam) stops working. I get error messages that
indicate that the problem might be lack of support for the shm
filesystem. I suspect that my problem might be a failure to make the
appropriate selection in xconfig to support this. The 'help' page for
the System V IPC (CONFIG_SYSVIPC) in xconfig states that one should
place into /etc/fstab the following:
none /var/shm shm defaults 0 0
Similarly, Johannes Erdfelt suggested using the mount command, which I
guess accomplishes the same thing. Making the change to /etc/fstab
leads to boot messages indicating that there is no /var/shm mount
point. What would I have to do to create the shm filesystem and mount
point -- for instance, what config option would I have to select)?
Any suggestions would be much appreciated.
From root@mail.velenje.cx Fri, 21 Apr 2000 21:54:15 +0200 (CEST)
Date: Fri, 21 Apr 2000 21:54:15 +0200 (CEST)
From: Samo Gabrovec root@mail.velenje.cx
Subject: [cpia] Fatal error
The problem was in the cable. it was cut at the entrance to the camera.
there are 9 wires and only one was cut.... i found that thanks`s to you
peter now tha cam works again.
Thank you thank you!
----------------------------------------------------------------
Its a JOKE, like the funny kind but different.
----------------------------------------------------------------
Visit http://www.velenje.cx
----------------------------------------------------------------
On Wed, 19 Apr 2000, Peter Pregler wrote:
> On Tue, Apr 18, 2000 at 09:50:42PM +0200, Samo Gabrovec wrote:
> > 1. I would like to tell that i had a working setup with webcam II for at
> > least 2 months. I didn`t change anything except i rebooted.
> > Is my camera broken?
> > the modules load like they should but when i try to run a program like
> > gqcam it says: /dev/video: Input/output error
> > and in the logs i get :cpia.c(18780):reset_camera(2475):fatal_error:
> > 0x20
> > what is this fatal error?
>
> IIRC this means that the VP cannot be powered on. In case of a parport
> camera this usually happens if the camera is connected to the parallel
> port but not to the keyboad (i.e. no power).
>
> -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
>
From nikom@merl.com Fri, 21 Apr 2000 16:45:21 -0400
Date: Fri, 21 Apr 2000 16:45:21 -0400
From: Jacob Nikom nikom@merl.com
Subject: [cpia] Building a kernel with CPiA support
Hi,
I am trying to configure a kernel 2.3.99 pre5 trying to
get CPiA driver supported by the kernel. However, when I run
menuconfig or xconfig utilities they never asked me about
CPiA driver.
In the file Config.help there is an information about the
driver, like CONFIG_VIDEO_CPIA, CONFIG_VIDEO_CPIA_USB.
Which utility should I run to put those configuration parameters
into the kernel?
I am running Redhat 6.2, Pentium II, current kernel 2.2.12-20.
Thank you,
Jacob Nikom
From jerdfelt@sventech.com Fri, 21 Apr 2000 17:03:59 -0400
Date: Fri, 21 Apr 2000 17:03:59 -0400
From: Johannes Erdfelt jerdfelt@sventech.com
Subject: [cpia] Building a kernel with CPiA support
On Fri, Apr 21, 2000, Jacob Nikom wrote:
> Hi,
>
> I am trying to configure a kernel 2.3.99 pre5 trying to
> get CPiA driver supported by the kernel. However, when I run
> menuconfig or xconfig utilities they never asked me about
> CPiA driver.
>
> In the file Config.help there is an information about the
> driver, like CONFIG_VIDEO_CPIA, CONFIG_VIDEO_CPIA_USB.
>
> Which utility should I run to put those configuration parameters
> into the kernel?
>
> I am running Redhat 6.2, Pentium II, current kernel 2.2.12-20.
This is a problem with the current config system. They have dependancy
information which hides options if previous options were not specified.
You need to enable USB first, then go back to video4linux and then
select CPiA.
However, it should have atleast prompted you for the CPiA core driver.
JE
From nikom@merl.com Fri, 21 Apr 2000 17:54:56 -0400
Date: Fri, 21 Apr 2000 17:54:56 -0400
From: Jacob Nikom nikom@merl.com
Subject: [cpia] Building a kernel with CPiA support
Thank you Johannes,
I would never get it by myself,
Jacob Nikom
Johannes Erdfelt wrote:
>
> On Fri, Apr 21, 2000, Jacob Nikom wrote:
> > Hi,
> >
> > I am trying to configure a kernel 2.3.99 pre5 trying to
> > get CPiA driver supported by the kernel. However, when I run
> > menuconfig or xconfig utilities they never asked me about
> > CPiA driver.
> >
> > In the file Config.help there is an information about the
> > driver, like CONFIG_VIDEO_CPIA, CONFIG_VIDEO_CPIA_USB.
> >
> > Which utility should I run to put those configuration parameters
> > into the kernel?
> >
> > I am running Redhat 6.2, Pentium II, current kernel 2.2.12-20.
>
> This is a problem with the current config system. They have dependancy
> information which hides options if previous options were not specified.
>
> You need to enable USB first, then go back to video4linux and then
> select CPiA.
>
> However, it should have atleast prompted you for the CPiA core driver.
>
> JE
From kopecjc@att.net Fri, 21 Apr 2000 22:04:54 -0400
Date: Fri, 21 Apr 2000 22:04:54 -0400
From: Joseph C. Kopec kopecjc@att.net
Subject: [cpia] gqcam hanging (was 'shm filesystem...')
I am using an Ezonics EZCam USB on a Pentium II 400 MHz running version
2.3.99-pre5 of the kernel (upgraded from the 2.2.12-20 kernel that came
with Redhat 6.1), with the JE UHCI USB option. Everything is compiled
into the kernel except for cpia and cpia_usb, which I have as modules.
I managed to get the shm filesystem up and running (my earlier problem)
by creating a /var/shm directory with mkdir. This stops gqcam from
complaining about shm when it starts up. It runs fine for a few
minutes, but then gqcam invariably hangs (goes into 'D' state). The
hanging seems unrelated to any activity with respect to gqcam or other
applications (for instance, it does not seem to be caused by taking
snapshots). Does anyone have any suggestions as to what may be going
wrong?
Additional question: where can I get a man page type description of the
gqcam command line interface? It did not seem to be in the materials on
sourceforge.
From jerdfelt@valinux.com Fri, 21 Apr 2000 20:55:50 -0700
Date: Fri, 21 Apr 2000 20:55:50 -0700
From: Johannes Erdfelt jerdfelt@valinux.com
Subject: [cpia] [patch] CPiA deadlock for 2.3 kernel
--dTy3Mrz/UPE2dbVg
Content-Type: text/plain; charset=us-ascii
This is identical to the deadlock patch I sent to the CPiA list a week ago
but for 2.3 kernels (just offsets are different).
Joseph, give this patch a try and see if your problem goes away.
Randy, this patch isn't specifically for USB. Do you want these sent to
you? And, if you don't mind, please send it on to Linus :)
JE
--dTy3Mrz/UPE2dbVg
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="cpia-deadlock.patch"
--- linux-2.3.99-pre6-5/drivers/char/cpia.c Mon Mar 27 10:22:31 2000
+++ linux-2.3.99-pre4-5/drivers/char/cpia.c Fri Apr 21 19:51:36 2000
@@ -1577,9 +1577,13 @@
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 {
+ if (command == CPIA_COMMAND_GetColourParams ||
+ command == CPIA_COMMAND_GetColourBalance ||
+ command == CPIA_COMMAND_GetExposure)
+ up(&cam->param_lock);
+ } else {
switch(command) {
case CPIA_COMMAND_GetCPIAVersion:
cam->params.version.firmwareVersion = data[0];
--dTy3Mrz/UPE2dbVg--
From nikom@merl.com Mon, 24 Apr 2000 19:44:10 -0400
Date: Mon, 24 Apr 2000 19:44:10 -0400
From: Jacob Nikom nikom@merl.com
Subject: [cpia] Problem with cpia-0.7.4
Hi,
I am trying to get my WebCamII work with USB driver.
I used to work with old parallel port version of this
camera. My machine is Pentium II (Klamath) with 128MB.
I was able to get 2.3.99-pre5 kernel working and \
configured the cpia driver inside the kernel:
CONFIG_VIDEO_BWQCAM=y
CONFIG_VIDEO_CQCAM=y
CONFIG_VIDEO_CPIA=y
CONFIG_VIDEO_CPIA_PP=y
CONFIG_VIDEO_CPIA_USB=y
Following the discussion I create shm directory in the
/var directory and mounted it :
mount -t shm none /var/shm
Then I successfully configured and compiled my files.
However, when I started to run gqcam executable, it complained:
/dev/video: No such device
Actually, such a device exists, but it does not have major number:
#ls -l vid*
lrwxrwxrwx 1 root root 6 Mar 31 05:35 video -> video0
crw------- 1 nikom root 81, 0 Jan 28 16:59 video0
crw------- 1 nikom root 81, 1 Jan 28 16:59 video1
Should I create new video device using mknod command?
I am not sure what else has to be done to make it work.
I would appreciate any help.
Regards,
Jacob Nikom
From jerdfelt@sventech.com Mon, 24 Apr 2000 20:12:11 -0400
Date: Mon, 24 Apr 2000 20:12:11 -0400
From: Johannes Erdfelt jerdfelt@sventech.com
Subject: [cpia] Problem with cpia-0.7.4
On Mon, Apr 24, 2000, Jacob Nikom wrote:
> Hi,
>
> I am trying to get my WebCamII work with USB driver.
> I used to work with old parallel port version of this
> camera. My machine is Pentium II (Klamath) with 128MB.
> I was able to get 2.3.99-pre5 kernel working and \
> configured the cpia driver inside the kernel:
> CONFIG_VIDEO_BWQCAM=y
> CONFIG_VIDEO_CQCAM=y
> CONFIG_VIDEO_CPIA=y
> CONFIG_VIDEO_CPIA_PP=y
> CONFIG_VIDEO_CPIA_USB=y
>
>
> Following the discussion I create shm directory in the
> /var directory and mounted it :
> mount -t shm none /var/shm
>
> Then I successfully configured and compiled my files.
> However, when I started to run gqcam executable, it complained:
> /dev/video: No such device
>
> Actually, such a device exists, but it does not have major number:
> #ls -l vid*
> lrwxrwxrwx 1 root root 6 Mar 31 05:35 video -> video0
> crw------- 1 nikom root 81, 0 Jan 28 16:59 video0
> crw------- 1 nikom root 81, 1 Jan 28 16:59 video1
>
> Should I create new video device using mknod command?
> I am not sure what else has to be done to make it work.
You don't need to create a new device node.
Is USB working correctly?
Did you mount /proc/bus/usb? If so, do a cat /proc/bus/usb/devices and
see what it's in there.
JE
From nikom@merl.com Tue, 25 Apr 2000 15:25:02 -0400
Date: Tue, 25 Apr 2000 15:25:02 -0400
From: Jacob Nikom nikom@merl.com
Subject: [cpia] Problem with cpia-0.7.4
Hi Johannes,
Thank you very much for your response. There is nothing
in my /proc/bus/usb directory. I think it is empty because
I did not have any devices but CPIA camera.
Here is the list of my configuration settings related
to USB and CPIA:
#
# USB support
#
CONFIG_USB=y
CONFIG_USB_DEBUG=y
CONFIG_USB_DEVICEFS=y
CONFIG_USB_UHCI=y
# CONFIG_USB_OHCI is not set
# CONFIG_USB_PRINTER is not set
# CONFIG_USB_SCANNER is not set
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_ACM is not set
# CONFIG_USB_SERIAL is not set
# CONFIG_USB_IBMCAM is not set
# CONFIG_USB_OV511 is not set
# CONFIG_USB_DC2XX is not set
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_STORAGE is not set
# CONFIG_USB_USS720 is not set
# CONFIG_USB_DABUSB is not set
# CONFIG_USB_PLUSB is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_DSBR is not set
# CONFIG_USB_HID is not set
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_WMFORCE is not set
# CONFIG_INPUT_KEYBDEV is not set
# CONFIG_INPUT_MOUSEDEV is not set
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_EVDEV is not set
CONFIG_VIDEO_BWQCAM=y
CONFIG_VIDEO_CQCAM=y
CONFIG_VIDEO_CPIA=y
CONFIG_VIDEO_CPIA_PP=y
CONFIG_VIDEO_CPIA_USB=y
When I tried to mount my /proc/bus/usb directory,
I got an error:
[nikom@xxx linux]# mount /proc/bus/usb
mount: can't find /proc/bus/usb in /etc/fstab or /etc/mtab
[nikom@xxx linux]#
Should I edit fstab manually or the correct version should be
created automatically? I suspect, there is something wrong in
my kernel configuration settings but I don't know what it could be.
Regards,
Jacob Nikom
Johannes Erdfelt wrote:
>
> On Mon, Apr 24, 2000, Jacob Nikom wrote:
> > Hi,
> >
> > I am trying to get my WebCamII work with USB driver.
> > I used to work with old parallel port version of this
> > camera. My machine is Pentium II (Klamath) with 128MB.
> > I was able to get 2.3.99-pre5 kernel working and \
> > configured the cpia driver inside the kernel:
> > CONFIG_VIDEO_BWQCAM=y
> > CONFIG_VIDEO_CQCAM=y
> > CONFIG_VIDEO_CPIA=y
> > CONFIG_VIDEO_CPIA_PP=y
> > CONFIG_VIDEO_CPIA_USB=y
> >
> >
> > Following the discussion I create shm directory in the
> > /var directory and mounted it :
> > mount -t shm none /var/shm
> >
> > Then I successfully configured and compiled my files.
> > However, when I started to run gqcam executable, it complained:
> > /dev/video: No such device
> >
> > Actually, such a device exists, but it does not have major number:
> > #ls -l vid*
> > lrwxrwxrwx 1 root root 6 Mar 31 05:35 video -> video0
> > crw------- 1 nikom root 81, 0 Jan 28 16:59 video0
> > crw------- 1 nikom root 81, 1 Jan 28 16:59 video1
> >
> > Should I create new video device using mknod command?
> > I am not sure what else has to be done to make it work.
>
> You don't need to create a new device node.
>
> Is USB working correctly?
>
> Did you mount /proc/bus/usb? If so, do a cat /proc/bus/usb/devices and
> see what it's in there.
>
> JE
From jerdfelt@sventech.com Tue, 25 Apr 2000 17:14:28 -0400
Date: Tue, 25 Apr 2000 17:14:28 -0400
From: Johannes Erdfelt jerdfelt@sventech.com
Subject: [cpia] Problem with cpia-0.7.4
On Tue, Apr 25, 2000, Jacob Nikom wrote:
> Thank you very much for your response. There is nothing
> in my /proc/bus/usb directory. I think it is empty because
> I did not have any devices but CPIA camera.
All USB devices will be listed in there. And even if you don't have any
USB devices connected, there will be a devices and drivers file.
If it's empty, the filesystem hasn't been mounted.
> When I tried to mount my /proc/bus/usb directory,
> I got an error:
> [nikom@xxx linux]# mount /proc/bus/usb
> mount: can't find /proc/bus/usb in /etc/fstab or /etc/mtab
> [nikom@xxx linux]#
mount -t usbdevfs none /proc/bus/usb
> Should I edit fstab manually or the correct version should be
> created automatically? I suspect, there is something wrong in
> my kernel configuration settings but I don't know what it could be.
It's not automatic. You need to manually mount it. You can add it to
fstab as well.
JE
From nikom@merl.com Tue, 25 Apr 2000 18:17:53 -0400
Date: Tue, 25 Apr 2000 18:17:53 -0400
From: Jacob Nikom nikom@merl.com
Subject: [cpia] Problem with cpia-0.7.4
Hi Johannes,
Thank you very much for your help. I followed your advice and
mounted the device using fstab. Here is my fstab file:
/dev/sda1 / ext2
defaults 1 1
/dev/cdrom /mnt/cdrom iso9660
noauto,owner,ro 0 0
/dev/fd0 /mnt/floppy auto
noauto,owner 0 0
none /proc proc
defaults 0 0
none /dev/pts devpts
gid=5,mode=620 0 0
/dev/sda5 swap swap
defaults 0 0
/dev/video /proc/bus/usb usbdevfs
defaults 0 0
However, the gqcam program still cannot recognize the video device:
prompt>gqcam
/dev/video: No such device
Here are my mounted devices:
prompt> mount
/dev/sda1 on / type ext2 (rw)
none on /proc type proc (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/video0 on /proc/bus/usb type usbdevfs (rw)
automount(pid447) on /releases-sgi type autofs
(rw,fd=5,pgrp=447,minproto=2,maxproto=3)
automount(pid463) on /projects type autofs
(rw,fd=5,pgrp=463,minproto=2,maxproto=3)
automount(pid477) on /homes type autofs
(rw,fd=5,pgrp=477,minproto=2,maxproto=3)
automount(pid434) on /distributions type autofs
(rw,fd=5,pgrp=434,minproto=2,maxproto=3)
automount(pid429) on /releases-linux type autofs
(rw,fd=5,pgrp=429,minproto=2,maxproto=3)
hercules:/homes/nikom on /homes/nikom type nfs
(rw,intr,rsize=8192,wsize=8192,addr=137.203.128.5,addr=137.203.128.5)
none on /var/shm type shm (rw)
prompt>
I thought I need "video0" instead of "video" and recompiled frontend.c
but it did not help.
Do you know what could be wrong?
Regards,
Jacob Nikom
Johannes Erdfelt wrote:
>
> On Tue, Apr 25, 2000, Jacob Nikom wrote:
> > Thank you very much for your response. There is nothing
> > in my /proc/bus/usb directory. I think it is empty because
> > I did not have any devices but CPIA camera.
>
> All USB devices will be listed in there. And even if you don't have any
> USB devices connected, there will be a devices and drivers file.
>
> If it's empty, the filesystem hasn't been mounted.
>
> > When I tried to mount my /proc/bus/usb directory,
> > I got an error:
> > [nikom@xxx linux]# mount /proc/bus/usb
> > mount: can't find /proc/bus/usb in /etc/fstab or /etc/mtab
> > [nikom@xxx linux]#
>
> mount -t usbdevfs none /proc/bus/usb
>
> > Should I edit fstab manually or the correct version should be
> > created automatically? I suspect, there is something wrong in
> > my kernel configuration settings but I don't know what it could be.
>
> It's not automatic. You need to manually mount it. You can add it to
> fstab as well.
>
> JE
From jerdfelt@sventech.com Tue, 25 Apr 2000 18:30:34 -0400
Date: Tue, 25 Apr 2000 18:30:34 -0400
From: Johannes Erdfelt jerdfelt@sventech.com
Subject: [cpia] Problem with cpia-0.7.4
On Tue, Apr 25, 2000, Jacob Nikom wrote:
>
> Thank you very much for your help. I followed your advice and
> mounted the device using fstab. Here is my fstab file:
>
> /dev/video /proc/bus/usb usbdevfs
> defaults 0 0
This is incorrect. It happens to work, but it should read:
none /proc/bus/usb usbdevfs defaults 0 0
> However, the gqcam program still cannot recognize the video device:
>
> prompt>gqcam
> /dev/video: No such device
>
> I thought I need "video0" instead of "video" and recompiled frontend.c
> but it did not help.
> Do you know what could be wrong?
video is a symlink to video0 on your machine so they are identical.
Could you give me the output of /proc/bus/usb/devices?
JE
From nikom@merl.com Tue, 25 Apr 2000 18:44:37 -0400
Date: Tue, 25 Apr 2000 18:44:37 -0400
From: Jacob Nikom nikom@merl.com
Subject: [cpia] Problem with cpia-0.7.4
Hi Johannes,
I appreciate your help very much. Here is my directory
/proc/bus/usb and its content:
[ usb]# pwd
/proc/bus/usb
[ usb]# ls -l
total 0
dr-xr-xr-x 1 root root 0 Apr 25 17:40 001
-r--r--r-- 1 root root 0 Apr 25 17:40 devices
-r--r--r-- 1 root root 0 Apr 25 17:40 drivers
[ usb]#
[ prompt]# more devices
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 0.00
S: Product=USB UHCI Root Hub
S: SerialNumber=ff80
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0553 ProdID=0002 Rev= 1.00
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=400mA
I: If#= 1 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=00 Prot=ff Driver=(none)
E: Ad=81(I) Atr=01(Isoc) MxPS= 0 Ivl= 1ms
I: If#= 1 Alt= 1 #EPs= 1 Cls=ff(vend.) Sub=00 Prot=ff Driver=(none)
E: Ad=81(I) Atr=01(Isoc) MxPS= 448 Ivl= 1ms
I: If#= 1 Alt= 2 #EPs= 1 Cls=ff(vend.) Sub=00 Prot=ff Driver=(none)
E: Ad=81(I) Atr=01(Isoc) MxPS= 704 Ivl= 1ms
I: If#= 1 Alt= 3 #EPs= 1 Cls=ff(vend.) Sub=00 Prot=ff Driver=(none)
E: Ad=81(I) Atr=01(Isoc) MxPS= 960 Ivl= 1ms
[ prompt]# more drivers
hub
usbdevfs
[ prompt]# more drivers
Regards,
Jacob Nikom
Johannes Erdfelt wrote:
>
> On Tue, Apr 25, 2000, Jacob Nikom wrote:
> >
> > Thank you very much for your help. I followed your advice and
> > mounted the device using fstab. Here is my fstab file:
> >
> > /dev/video /proc/bus/usb usbdevfs
> > defaults 0 0
>
> This is incorrect. It happens to work, but it should read:
>
> none /proc/bus/usb usbdevfs defaults 0 0
>
> > However, the gqcam program still cannot recognize the video device:
> >
> > prompt>gqcam
> > /dev/video: No such device
> >
> > I thought I need "video0" instead of "video" and recompiled frontend.c
> > but it did not help.
> > Do you know what could be wrong?
>
> video is a symlink to video0 on your machine so they are identical.
>
> Could you give me the output of /proc/bus/usb/devices?
>
> JE
From jerdfelt@sventech.com Tue, 25 Apr 2000 19:01:47 -0400
Date: Tue, 25 Apr 2000 19:01:47 -0400
From: Johannes Erdfelt jerdfelt@sventech.com
Subject: [cpia] Problem with cpia-0.7.4
--5mCyUwZo2JvN/JJP
Content-Type: text/plain; charset=us-ascii
On Tue, Apr 25, 2000, Jacob Nikom wrote:
> Hi Johannes,
>
> I appreciate your help very much. Here is my directory
> /proc/bus/usb and its content:
>
> [ usb]# pwd
> /proc/bus/usb
> [ usb]# ls -l
> total 0
> dr-xr-xr-x 1 root root 0 Apr 25 17:40 001
> -r--r--r-- 1 root root 0 Apr 25 17:40 devices
> -r--r--r-- 1 root root 0 Apr 25 17:40 drivers
> [ usb]#
>
> [ prompt]# more devices
> T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
> B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
> D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
> P: Vendor=0000 ProdID=0000 Rev= 0.00
> S: Product=USB UHCI Root Hub
> S: SerialNumber=ff80
> C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
> I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
> E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
> T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
> D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
> P: Vendor=0553 ProdID=0002 Rev= 1.00
> C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=400mA
> I: If#= 1 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=00 Prot=ff Driver=(none)
> E: Ad=81(I) Atr=01(Isoc) MxPS= 0 Ivl= 1ms
> I: If#= 1 Alt= 1 #EPs= 1 Cls=ff(vend.) Sub=00 Prot=ff Driver=(none)
> E: Ad=81(I) Atr=01(Isoc) MxPS= 448 Ivl= 1ms
> I: If#= 1 Alt= 2 #EPs= 1 Cls=ff(vend.) Sub=00 Prot=ff Driver=(none)
> E: Ad=81(I) Atr=01(Isoc) MxPS= 704 Ivl= 1ms
> I: If#= 1 Alt= 3 #EPs= 1 Cls=ff(vend.) Sub=00 Prot=ff Driver=(none)
> E: Ad=81(I) Atr=01(Isoc) MxPS= 960 Ivl= 1ms
>
> [ prompt]# more drivers
> hub
> usbdevfs
> [ prompt]# more drivers
The CPiA driver never got registered. Are you running this patch that I
posted a week or two back?
JE
--5mCyUwZo2JvN/JJP
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="cpia-usb-init.patch"
--- drivers/usb/usb-core.c.old Mon Apr 17 19:12:31 2000
+++ drivers/usb/usb-core.c Mon Apr 17 19:13:53 2000
@@ -28,6 +28,7 @@
* USB device drivers
*/
+int usb_cpia_init(void);
int usb_audio_init(void);
int usb_ibmcam_init(void);
int dabusb_init(void);
@@ -68,6 +69,9 @@
usb_hub_init();
#ifndef CONFIG_USB_MODULE
+#ifdef CONFIG_VIDEO_CPIA_USB
+ usb_cpia_init();
+#endif
#ifdef CONFIG_USB_AUDIO
usb_audio_init();
#endif
--5mCyUwZo2JvN/JJP--
From nikom@merl.com Tue, 25 Apr 2000 20:49:31 -0400
Date: Tue, 25 Apr 2000 20:49:31 -0400
From: Jacob Nikom nikom@merl.com
Subject: [cpia] It works!!!
Hi Johannes,
It works!!!
I patched the file manually and compiling the kernel now.
I think the reason for patch failing was that I renamed
the /usr/src/linux directory as /usr/src/linux_2_3_99-pre5
and the patch could not recognize it.
It works great - I am so happy now.
Thank you very much for your REALLY GREAT help.
Thanks to all cpia guys who created driver and
gqcam application.
Jacob Nikom
Johannes Erdfelt wrote:
>
> On Tue, Apr 25, 2000, Jacob Nikom wrote:
> > Hi Johannes,
> >
> > Thank you very much for your help.
> >
> > I ran the patch in the /usr/src/linux directory:
> >
> > [ client]# cd /usr/src/linux
> > [ linux]# patch -p0 < cpia-usb-init.patch
> > patching file `drivers/usb/usb-core.c'
> > Hunk #1 FAILED at 28.
> > Hunk #2 FAILED at 69.
> > 2 out of 2 hunks FAILED -- saving rejects to drivers/usb/usb-core.c.rej
> >
> > Here the usb-core.c.rej file:
> >
> > //usr/src/linux/drivers/usb more usb-core.c.rej
> > ***************
> > *** 28,33 ****
> > * USB device drivers
> > */
> >
> > int usb_audio_init(void);
> > int usb_ibmcam_init(void);
> > int dabusb_init(void);
> > --- 28,34 ----
> > * USB device drivers
> > */
> >
> > + int usb_cpia_init(void);
> > int usb_audio_init(void);
> > int usb_ibmcam_init(void);
> > int dabusb_init(void);
> > ***************
> > *** 68,73 ****
> > usb_hub_init();
> >
> > #ifndef CONFIG_USB_MODULE
> > #ifdef CONFIG_USB_AUDIO
> > usb_audio_init();
> > #endif
> > --- 69,77 ----
> > usb_hub_init();
> >
> > #ifndef CONFIG_USB_MODULE
> > + #ifdef CONFIG_VIDEO_CPIA_USB
> > + usb_cpia_init();
> > + #endif
> > #ifdef CONFIG_USB_AUDIO
> > usb_audio_init();
> > #endif
> >
> > I feel that something went wrong. Am I correct?
>
> Yup. Something did go wrong.
>
> Apparentely you aren't using 2.3.99-pre5 or the patch file got corrupted
> some how.
>
> You may want to apply the patch by hand, it's very small patch.
>
> Where you see + signs, add that line (without the +)
>
> Or, you can upgrade to the latest 2.3.99-pre kernel which has the fix
> already in there.
>
> JE
From jeffl@SPATIALinfo.com Wed, 26 Apr 2000 14:15:05 +1000
Date: Wed, 26 Apr 2000 14:15:05 +1000
From: Jeff Laing jeffl@SPATIALinfo.com
Subject: [cpia] BarbieCam (again)
> > Specifically, does anyone know what baudrate, etc to talk
> to the camera?
>
> Details are as follows
>
> - 57,600 baud
> - 8 data bits, no parity, 1 stop bit
> - no handshaking
I have successfully managed to get data out of the camera and am going great
guns. It appears that it matches the VVL310 sufficiently for the
documentation there to be helpful, although the chip-id identifies it as
0x12A ???
My problem now lies in the image processing space - I've done some
rudimentary RGB blending to try and reduce the 162x124 array to a 160x120
rgb array and it looks "ok" although it has these horizontal lines about
every four rows which are much darker. The processing I've been doing just
takes the r & b values from the surrounding pixels, and averages the g
values.
I'm wondering whether there is any need for me to be adjusting the camera
values before processing them (ie, adding the average pixel value in, or
some other level offset). Alternately, is it possible that the camera is
interlacing somehow, and I should be rearranging the rows (as I had to do
for the columns)?
Any ideas would be most appreciated,
thanks in advance,
Jeff Laing
----------------------------------------------------------------------------
---
"But when I am alone, I do not have the effrontery to consider myself an
artist
at all, not in the grand old meaning of the word: Giotto, Titian, Rembrandt,
Goya were great painters. I am only a public clown -- a mountebank. I have
understood my time and have exploited the imbecility, the vanity, the greed
of
my contemporaries. It is a bitter confession, this confession of mine, more
painful than it may seem. But at least and at last it does have the merit of
being honest." -- Pablo Picasso
From roarjo2NOSPAM@usfca.edu Fri, 28 Apr 2000 16:01:38 -0700
Date: Fri, 28 Apr 2000 16:01:38 -0700
From: John Roark roarjo2NOSPAM@usfca.edu
Subject: [cpia] Aiptek HyperVcam Fun
Jarl Totland wrote:
>
> At 15:50 2000-04-17 +0200, Peter_Pregler@email.com wrote:
> >I just scanned some source-code and saw that your Vendor:Product
> >matches the OV511 chip. So the Webcam III driver (don't know how they
> >called it) in the 2.3-something kernels should work. Can anyone
> >confirm why this camera is listed as CPiA-based? Are there different
> >versions?
>
> According to John Roark 2000-02-18:
> > I have gotten my Aiptek Hyper Vcam Fun to work with the usbcore,
> > usb-uhci, videodev, and cpia modules in kernel 2.3.42.
>
> Probably just a mixup. I've removed it from the homepage for now.
>
> Vyrdsamt,
> -Jarl
That is very odd? I'm not exactly sure what this means? I am currently
running the camera with the stated drivers without any problems? It
reports itself as "CPiA USB Camera" stored in vid_caps.name when
ioctl(device, VIDIOCGCAP, &vid_caps); is called? I'm even using it as a
web cam right now. (http://138.202.112.49/)
I'm not sure what the Vendor:product code translates to here but maybe
you do?
Kernel Messages:
----------------
Apr 21 12:38:00 reshall-112-49 kernel: Product: USB Camera
Apr 21 12:38:00 reshall-112-49 kernel: Length = 18
Apr 21 12:38:00 reshall-112-49 kernel: DescriptorType = 01
Apr 21 12:38:00 reshall-112-49 kernel: USB version = 1.00
Apr 21 12:38:00 reshall-112-49 kernel: Vendor:Product = 0553:0002
Apr 21 12:38:00 reshall-112-49 kernel: MaxPacketSize0 = 8
Apr 21 12:38:00 reshall-112-49 kernel: NumConfigurations = 1
Apr 21 12:38:00 reshall-112-49 kernel: Device version = 1.00
Apr 21 12:38:00 reshall-112-49 kernel: Device Class:SubClass:Protocol
= 00:00:00
Apr 21 12:38:03 reshall-112-49 kernel: usb.c: registered new driver cpia
Apr 21 12:38:03 reshall-112-49 kernel: USB CPiA camera found
...not that you really needed to see all this, but it is here anyway.
keep me up to date on this
thanks
john
--
int fd = socket(AF_INET, SOCK_PACKET, htons(0x800));
struct ifreq ifr;
strcpy(ifr.ifr_name, "eth0"); ioctl(fd, SIOCGIFFLAGS, &ifr);
ifr.ifr_flags |= IFF_PROMISC; ioctl(fd, SIOCSIFFLAGS, &ifr);
From halset@pvv.ntnu.no Sat, 29 Apr 2000 17:55:49 +0200 (MET DST)
Date: Sat, 29 Apr 2000 17:55:49 +0200 (MET DST)
From: Tore Halset halset@pvv.ntnu.no
Subject: [cpia] vic and camserv from cpia
Hello.
I have a cpia camera that works with vic og camserv, but not vic and
camserv at the same time. Is it possible to make to programs read from the
same video4linux device at the same time?
- Tore.