The cam does function with with luvcview.
I've been getting the a similiar 'BadWindow' error with Ekiga though. When
patched with the USB reset patch, the white balance, contrast and brightness
appear to function better. The default setting are a little too low.
So, the patch does work, its how it interfaces with other applications that
seems to be the problem.
Mark.
From: D G <[EMAIL PROTECTED]>
To: <[email protected]>
Subject: [Linux-uvc-devel] Bison webcam: the patch doesn't work
Date: Mon, 11 Jun 2007 21:49:23 +0200
MIME-Version: 1.0
I tried your patch (add a few lines to uvc_driver.c for Bison, and
recompile). dmesg does not complain at boot time:
uvcvideo: Found UVC 1.00 device USB2.0 Camera (5986:0100)
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v0.1.0)
But it does not work. Examples with three applications:
* Camorama: A window with "Could not connect to video device (/dev/video0)"
(although /dev/video0 does exist). No output on the terminal
* amsn:
Type: IP-Restrict-NAT, Listening: false , the same if I completely
disconnect the firewall.
If I do "change video settings", dmesg says uvcvideo: Button event (0). (I
think it is at that moment, but not sure).
Surprisingly, when I change a video setting in amsn, the led on the webcam
lights and stays lit. But the message Type: IP-Restrict-NAT, Listening:
false is still the same.
* With xawtv . The led lights for a second and then stops. The capture
screen is black.
The output on the terminal:
# xawtv
This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.21-1-686)
xinerama 0: 1280x800+0+0
/dev/video0 [v4l2]: no overlay support
v4l-conf had some trouble, trying to continue anyway
Warning: Cannot convert string "-*-ledfixed-medium-r-*--39-*-*-*-c-*-*-*"
to type FontStruct
ioctl: VIDIOC_G_STD(std=0xbfbe3bb4
[PAL_G,PAL_I,PAL_D,PAL_K,PAL_M,PAL_N,PAL_60,NTSC_M,NTSC_M_JP,SECAM_D,SECAM_G,SECAM_H,SECAM_K,SECAM_K1,?ATSC_8_VSB,ATSC_16_VSB,(null),(null),(null),(null),(null),(null)]):
Invalid argument
ioctl: VIDIOC_S_STD(std=0x0 []): Invalid argument
libGL warning: 3D driver claims to not support visual 0x66
ioctl: VIDIOC_REQBUFS(count=1;type=VIDEO_CAPTURE;memory=MMAP): Invalid
argument
ioctl: VIDIOC_DQBUF(index=0;type=VIDEO_CAPTURE;bytesused=0;flags=0x0
[];field=ANY;;timecode.type=0;timecode.flags=0;timecode.frames=0;timecode.seconds=0;timecode.minutes=0;timecode.hours=0;timecode.userbits="";sequence=0;memory=unknown):
Invalid argument
ioctl: VIDIOC_REQBUFS(count=2;type=VIDEO_CAPTURE;memory=MMAP): Device or
resource busy
ioctl: VIDIOC_QBUF(index=0;type=unknown;bytesused=0;flags=0x0
[];field=ANY;;timecode.type=0;timecode.flags=0;timecode.frames=0;timecode.seconds=0;timecode.minutes=0;timecode.hours=0;timecode.userbits="";sequence=0;memory=unknown):
Invalid argument
v4l2: oops: select timeout
munmap: Invalid argument
ioctl: VIDIOC_REQBUFS(count=1;type=VIDEO_CAPTURE;memory=MMAP): Device or
resource busy
X Error of failed request: BadWindow (invalid Window parameter)
Major opcode of failed request: 2 (X_ChangeWindowAttributes)
Resource id in failed request: 0x1c0005c
Serial number of failed request: 1537
Current serial number in output stream: 1537
and dmesg stays the same.
Hope it helps,
David
_________________________________________________________________
Play free games, earn tickets, get cool prizes! Join Live Search Club.
http://club.live.com/home.aspx?icid=CLUB_wlmailtextlink
_______________________________________________
Linux-uvc-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
_________________________________________________________________
The next generation of Hotmail is here! http://www.newhotmail.co.uk/
_______________________________________________
Linux-uvc-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
