Re: [Linux-uvc-devel] compat_ioctl32 errors while poking

2011-09-26 Thread Riccardo Magliocchetti 

Hi Laurent,

Il 26/09/2011 18:15, Laurent Pinchart ha scritto:

Hi Riccardo,

On Sunday 25 September 2011 16:06:53 Riccardo Magliocchetti wrote:

Hello,

i've started playing with opencv but the inlined python script does not
work and these messages are shown in dmesg:

[32452.730023] compat_ioctl32: unknown ioctl 'v', dir=1, #10 (0x4020760a)
[32452.730043] ioctl32(python:10359): Unknown cmd fd(3)
cmd(4020760a){t:'v';sz:32} arg(09f57f48) on /dev/video0


This is a V4L1 ioctl and the uvcvideo driver supports V4L2 only. V4L1 is
deprecated and has been removed from the kernel.


Thanks for the quick response! Will upgrade opencv then.

cheers,
riccardo
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

[Linux-uvc-devel] compat_ioctl32 errors while poking

2011-09-25 Thread Riccardo Magliocchetti 

Hello,

i've started playing with opencv but the inlined python script does not 
work and these messages are shown in dmesg:


[32452.730023] compat_ioctl32: unknown ioctl 'v', dir=1, #10 (0x4020760a)
[32452.730043] ioctl32(python:10359): Unknown cmd fd(3) 
cmd(4020760a){t:'v';sz:32} arg(09f57f48) on /dev/video0


This may well be an opencv issue.

$ cat cvtest.py
import cv

capture = cv.CreateCameraCapture(0)

cv.SetCaptureProperty(capture,cv.CV_CAP_PROP_FRAME_WIDTH, 640.0)
cv.SetCaptureProperty(capture,cv.CV_CAP_PROP_FRAME_HEIGHT, 480.0)

while True:
img = cv.QueryFrame(capture)
cv.ShowImage(camera, img)
cv.WaitKey(10)

kernel is 3.0 64 bit on 32 bit userspace, camera is 174f:5931, the 
camera works fine with luvcview.


thanks,
riccardo
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] sanyo cg10

2010-11-19 Thread Riccardo Magliocchetti 

Il 19/11/2010 01:28, Laurent Pinchart ha scritto:

Hi Riccardo,


Hi Laurent,


On Monday 01 November 2010 12:01:50 Riccardo Magliocchetti wrote:

Il 30/10/2010 20:58, Laurent Pinchart ha scritto:

On Friday 22 October 2010 21:19:22 Riccardo Magliocchetti wrote:

Il 20/10/2010 01:48, Laurent Pinchart ha scritto:

well, i've found that it's working fine out the box, it's actually a
call to luvcview -L -d /dev/video1 that breaks it.


I'm very surprised by that. luvcview -L doesn't modify the hardware
state. Maybe only the first stream attempt succeeds ? Could you try
running luvcview -d /dev/Video1 multiple times in a row ?


You are right, the first time luvcview -d /dev/video1 works fine, the
second it does not.


So the hardware probably crashes when the stream is stopped. Bad hardware :-(

This will be a bit hard to debug. We need to find out what makes the hardware
crash. It's probably a command send by the driver when stopping the stream, or
the lack of an expected command before restarting the stream.

The easiest way I can think of to try and debug the problem would be to
capture a USB trace when using the camera under Windows. Do you feel confident
enough to try that ?


Unfortunately I don't have a windows machine at hand, at work i have 
only mac os x machines. Are them any useful?


thanks,
riccardo
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] sanyo cg10

2010-11-01 Thread Riccardo Magliocchetti 

Il 30/10/2010 20:58, Laurent Pinchart ha scritto:

Hi Riccardo,


Hi Laurent,


On Friday 22 October 2010 21:19:22 Riccardo Magliocchetti wrote:

Il 20/10/2010 01:48, Laurent Pinchart ha scritto:

On Thursday 14 October 2010 19:32:01 Riccardo Magliocchetti wrote:

Hello,

i have a sanyo cg10 camcorder, i've tried to connect it to my pc using
it pc camera mode, it is recognized as uvc device but it is not
working. With vlc i see a green background, with luvcview:

$ luvcview -d /dev/video1
luvcview 0.2.6

SDL information:
 Video driver: x11
 A window manager is available

Device information:
 Device path:  /dev/video1

Stream settings:
 Frame format: MJPG

Unable to set format: Input/output error

Init v4L2 failed !! exit fatal


Do you get any additional message printed to the kernel log when this
happens ? If not, please raise the driver trace level with

echo 0x   /sys/modules/uvcvideo/parameters/trace

and run luvcview again. The driver should then print additional debug
information.


well, i've found that it's working fine out the box, it's actually a
call to luvcview -L -d /dev/video1 that breaks it.


I'm very surprised by that. luvcview -L doesn't modify the hardware state.
Maybe only the first stream attempt succeeds ? Could you try running luvcview
-d /dev/Video1 multiple times in a row ?


You are right, the first time luvcview -d /dev/video1 works fine, the 
second it does not.


riccardo
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

[Linux-uvc-devel] sanyo cg10

2010-10-19 Thread Riccardo Magliocchetti 

[resending after subscribing]

Hello,

i have a sanyo cg10 camcorder, i've tried to connect it to my pc using 
it pc camera mode, it is recognized as uvc device but it is not 
working. With vlc i see a green background, with luvcview:


$ luvcview -d /dev/video1
luvcview 0.2.6

SDL information:
   Video driver: x11
   A window manager is available
Device information:
   Device path:  /dev/video1
Stream settings:
   Frame format: MJPG
Unable to set format: Input/output error
  Init v4L2 failed !! exit fatal

dmesg shows:

[ 2542.516177] usb 2-2: new high speed USB device using ehci_hcd and 
address 4

[ 2542.876873] usb 2-2: New USB device found, idVendor=0474, idProduct=02e0
[ 2542.876890] usb 2-2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3

[ 2542.876899] usb 2-2: Product: SANYO Digital Camera
[ 2542.876906] usb 2-2: Manufacturer: SANYO
[ 2542.876912] usb 2-2: SerialNumber: V2057131
[ 2543.224991] uvcvideo: Found UVC 1.00 device SANYO Digital Camera 
(0474:02e0)


Attached lsusb -v output.

thanks,
riccardo


Bus 002 Device 003: ID 0474:02e0 Sanyo Electric Co., Ltd 
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   2.00
  bDeviceClass  239 Miscellaneous Device
  bDeviceSubClass 2 ?
  bDeviceProtocol 1 Interface Association
  bMaxPacketSize064
  idVendor   0x0474 Sanyo Electric Co., Ltd
  idProduct  0x02e0 
  bcdDevice1.00
  iManufacturer   1 
  iProduct2 
  iSerial 3 
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength  150
bNumInterfaces  2
bConfigurationValue 1
iConfiguration  0 
bmAttributes 0xc0
  Self Powered
MaxPower0mA
Interface Association:
  bLength 8
  bDescriptorType11
  bFirstInterface 0
  bInterfaceCount 2
  bFunctionClass 14 Video
  bFunctionSubClass   3 Video Interface Collection
  bFunctionProtocol   0 
  iFunction   2 
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   0
  bInterfaceClass14 Video
  bInterfaceSubClass  1 Video Control
  bInterfaceProtocol  0 
  iInterface  4 
  VideoControl Interface Descriptor:
bLength13
bDescriptorType36
bDescriptorSubtype  1 (HEADER)
bcdUVC   1.00
wTotalLength   39
dwClockFrequency0.001000MHz
bInCollection   1
baInterfaceNr( 0)   1
  VideoControl Interface Descriptor:
bLength17
bDescriptorType36
bDescriptorSubtype  2 (INPUT_TERMINAL)
bTerminalID 1
wTerminalType  0x0201 Camera Sensor
bAssocTerminal  2
iTerminal   0 
wObjectiveFocalLengthMin  0
wObjectiveFocalLengthMax  0
wOcularFocalLength0
bControlSize  2
bmControls   0x
  VideoControl Interface Descriptor:
bLength 9
bDescriptorType36
bDescriptorSubtype  3 (OUTPUT_TERMINAL)
bTerminalID 2
wTerminalType  0x0101 USB Streaming
bAssocTerminal  1
bSourceID   1
iTerminal   0 
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber1
  bAlternateSetting   0
  bNumEndpoints   1
  bInterfaceClass14 Video
  bInterfaceSubClass  2 Video Streaming
  bInterfaceProtocol  0 
  iInterface  5 
  VideoStreaming Interface Descriptor:
bLength14
bDescriptorType36
bDescriptorSubtype  1 (INPUT_HEADER)
bNumFormats 1
wTotalLength   69
bEndPointAddress  130
bmInfo  0
bTerminalLink   2
bStillCaptureMethod 0
bTriggerSupport 0
bTriggerUsage   0
bControlSize1
bmaControls( 0)11
  VideoStreaming Interface Descriptor:
bLength11
bDescriptorType36
bDescriptorSubtype  6 (FORMAT_MJPEG)
bFormatIndex1
bNumFrameDescriptors

Re: [Linux-uvc-devel] issues with syntek usb webcam

2009-03-19 Thread Riccardo Magliocchetti 
On Thu, Mar 19, 2009 at 2:38 PM, Laurent Pinchart
laurent.pinch...@skynet.be wrote:
 On Wednesday 18 March 2009 20:35:28 Riccardo Magliocchetti wrote:
 Laurent Pinchart ha scritto:
  On Monday 16 March 2009 21:43:41 Riccardo Magliocchetti wrote:
  hi,
 
  my syntek webcam (174f:5931) does not work with ekiga and cheese but
  it works fine with luvcview.
 
  The kernel is latest linus git tree v2.6.29-rc8-124-g5bee17f , libv4l is
  0.5.9.
 
  I've attached lsusb -v output and this is cheese output:
  [snip]
  v4l2src name=video_source device=/dev/video0 ! capsfilter
  name=capsfilter
  caps=video/x-raw-rgb,width=800,height=600,framerate=7/1;video/x-raw-yuv,
 wid th=800,height=600,framerate=7/1 ! identity
  libv4l2: error setting pixformat: Device or resource busy
  libv4l2: error requesting 4 buffers: Device or resource busy
 
  The device seems to be already open. Use fuser to find out if an
  application is using the video device.

 Unfortunately fuser reports the device opened only by cheese.

 The driver returns -EBUSY either when the device is already opened or if the
 camera is streaming.

 Try to set the trace parameter to 255 (echo 255 
 /sys/modules/uvcvideo/parameters/trace). The driver will then print debug
 messages to the kernel log, including a trace of the functions called by the
 userspace application. You should then be able to check if the device is
 opened twice, or if streaming has been started prior to the failed set format
 call.

Yes, i see the device opened twice but i cannot see more :)

One thing i've missed to report is that i have this on boot:

Mar 19 14:59:13 montag kernel: [5.639794] uvcvideo: UVC non
compliance - GET_DEF(PROBE) not supported. Enabling workaround.

thanks a lot for your patience

-- 
Riccardo Magliocchetti


uvctrace.log
Description: Binary data
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

[Linux-uvc-devel] issues with syntek usb webcam

2009-03-16 Thread Riccardo Magliocchetti 
hi,

my syntek webcam (174f:5931) does not work with ekiga and cheese but
it works fine with luvcview.

The kernel is latest linus git tree v2.6.29-rc8-124-g5bee17f , libv4l is 0.5.9.

I've attached lsusb -v output and this is cheese output:

Cheese 2.24.3
Probing devices with HAL...
Found device 174f:5931, getting capabilities...
Detected v4l2 device: USB2.0 UVC PC Camera
Driver: uvcvideo, version: 256
Capabilities: 0x0401

Probing supported video formats...
Device: USB2.0 UVC PC Camera (/dev/video0)
video/x-raw-yuv 1280 x 1024 num_framerates 1
7/1 video/x-raw-yuv 1280 x 960 num_framerates 1
7/1 video/x-raw-yuv 1280 x 800 num_framerates 1
7/1 video/x-raw-yuv 1024 x 768 num_framerates 1
7/1 video/x-raw-yuv 800 x 600 num_framerates 1
7/1 video/x-raw-yuv 640 x 480 num_framerates 1
20/1 video/x-raw-yuv 352 x 288 num_framerates 1
24/1 video/x-raw-yuv 320 x 240 num_framerates 1
24/1 video/x-raw-yuv 176 x 144 num_framerates 1
24/1 video/x-raw-yuv 160 x 120 num_framerates 1
24/1 video/x-raw-yuv 1280 x 1024 num_framerates 1
[snip]

v4l2src name=video_source device=/dev/video0 ! capsfilter
name=capsfilter
caps=video/x-raw-rgb,width=800,height=600,framerate=7/1;video/x-raw-yuv,width=800,height=600,framerate=7/1
! identity
libv4l2: error setting pixformat: Device or resource busy
libv4l2: error requesting 4 buffers: Device or resource busy


thanks
--
Riccardo Magliocchetti


lsusb
Description: Binary data
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel