Re: [Linux-uvc-devel] fuji finepix support?

2007-01-17 Thread Laurent Pinchart
Hi Ioannis,

  I have a fuji finepix e550 which is recognised by the uvc driver. When I
 plug in the camera I see this messages in dmesg:

  usb 2-1: new full speed USB device using uhci_hcd and address 5
  usb 2-1: configuration #1 chosen from 1 choice
  uvcvideo: Found UVC 1.00 device USB Web Camera (04cb:0172)

  and a device node is created:
  /dev/video0

  (and a symlink /dev/video to it)

  unfortunately it does work. It fails with the following error message:
[snip]

This is definitely a bug in the UVC driver. It should not crash.

Could you please set the trace parameter to 127 ?

echo 127  /sys/modules/uvcvideo/parameters/trace

Then try to plug your camera and let the kernel crash :-) I'll need the dmesg 
output (you can leave out the syslog output) with all the uvcvideo messages 
and the crash dump.

Cheers,

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


Re: [Linux-uvc-devel] fuji finepix support?

2007-01-17 Thread Serge A. Suchkov
  Hi 
  
  I have a fuji finepix e550 which is recognised by the uvc driver. When I 
 plug in the camera I see this messages in dmesg: 
  
  usb 2-1: new full speed USB device using uhci_hcd and address 5 
  usb 2-1: configuration #1 chosen from 1 choice 
  uvcvideo: Found UVC 1.00 device USB Web Camera (04cb:0172) 
  
  and a device node is created: 
  /dev/video0 
  
  (and a symlink /dev/video to it) 
  Message from [EMAIL PROTECTED] at Wed Jan 17 01:20:25 2007 ... 
  dellD800 kernel:  [f8e74d13] v4l_compat_translate_ioctl+0xb7b/0x1b48 
 [v4l1_compat] 
^^
You are used V4L1 app ?

  Process camE (pid: 3997, ti=d0623000 task=f7ccd9f0 task.ti=d0623000) 

Seems true

AFAIK v4l_compat layer was broken.

Try use v4l2 app in this case e.g. luvcview or other.
  
  -Ioannis  

-- 
Regards,
Serge A. Suchkov
--
Commitment, n.:
Commitment can be illustrated by a breakfast of ham and eggs.
The chicken was involved, the pig was committed.
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel


Re: [Linux-uvc-devel] fuji finepix support?

2007-01-17 Thread Ioannis Nousias
Serge A. Suchkov wrote:
  Hi 
  
  I have a fuji finepix e550 which is recognised by the uvc driver. When I 
 plug in the camera I see this messages in dmesg: 
  
  usb 2-1: new full speed USB device using uhci_hcd and address 5 
  usb 2-1: configuration #1 chosen from 1 choice 
  uvcvideo: Found UVC 1.00 device USB Web Camera (04cb:0172) 
  
  and a device node is created: 
  /dev/video0 
  
  (and a symlink /dev/video to it) 
  Message from [EMAIL PROTECTED] at Wed Jan 17 01:20:25 2007 ... 
  dellD800 kernel:  [f8e74d13] v4l_compat_translate_ioctl+0xb7b/0x1b48 
 [v4l1_compat] 
 
 ^^
 You are used V4L1 app ?

   
  Process camE (pid: 3997, ti=d0623000 task=f7ccd9f0 task.ti=d0623000) 
 
 
 Seems true

 AFAIK v4l_compat layer was broken.

 Try use v4l2 app in this case e.g. luvcview or other.
   
  
  -Ioannis  
 

   
ok. In the previous one I was using camE. This is with ekiga in v4l2 
setting:


uvcvideo: Probing generic UVC device 1
uvcvideo: Found format MJPEG.
uvcvideo: - 352x288 (10.0 fps)
uvcvideo: Found UVC 1.00 device USB Web Camera (04cb:0172)
uvcvideo: Scanning UVC chain: OT 3 - Unit 2 - IT 1
uvcvideo: Found a valid video chain (1 - 3).
uvcvideo: UVC device initialized.
uvcvideo: uvc_v4l2_open
uvcvideo: uvc_v4l2_release
uvcvideo: uvc_v4l2_open
uvcvideo: uvc_v4l2_ioctl
v4l1 ioctl VIDIOCGCAP, dir=r- (0x803c7601)
v4l2 ioctl VIDIOC_QUERYCAP, dir=r- (0x80685600)
v4l2 ioctl VIDIOC_ENUMINPUT, dir=rw (0xc04c561a)
v4l2 ioctl VIDIOC_ENUMINPUT, dir=rw (0xc04c561a)
v4l2 ioctl VIDIOC_ENUM_FMT, dir=rw (0xc0405602)
v4l2 ioctl VIDIOC_TRY_FMT, dir=rw (0xc0cc5640)
uvcvideo: Trying format 0x47504a4d (MJPG): 1x1.
uvcvideo: Using default frame interval 10.0 us (10.0 fps).
uvcvideo: uvc_v4l2_release
uvcvideo: uvc_v4l2_open
uvcvideo: uvc_v4l2_ioctl
v4l2 ioctl VIDIOC_QUERYCAP, dir=r- (0x80685600)
uvcvideo: uvc_v4l2_release
uvcvideo: uvc_v4l2_open
uvcvideo: uvc_v4l2_ioctl
v4l2 ioctl VIDIOC_QUERYCAP, dir=r- (0x80685600)
uvcvideo: uvc_v4l2_release
uvcvideo: uvc_v4l2_open
uvcvideo: uvc_v4l2_ioctl
v4l2 ioctl VIDIOC_QUERYCAP, dir=r- (0x80685600)
uvcvideo: uvc_v4l2_release
uvcvideo: uvc_v4l2_open
uvcvideo: uvc_v4l2_ioctl
v4l2 ioctl VIDIOC_QUERYCAP, dir=r- (0x80685600)
uvcvideo: uvc_v4l2_release
uvcvideo: uvc_v4l2_open
uvcvideo: uvc_v4l2_ioctl
v4l2 ioctl VIDIOC_QUERYCAP, dir=r- (0x80685600)
uvcvideo: uvc_v4l2_release
uvcvideo: uvc_v4l2_open
uvcvideo: uvc_v4l2_ioctl
v4l2 ioctl VIDIOC_QUERYCAP, dir=r- (0x80685600)
uvcvideo: uvc_v4l2_release
uvcvideo: uvc_v4l2_open
uvcvideo: uvc_v4l2_ioctl
v4l2 ioctl VIDIOC_QUERYCAP, dir=r- (0x80685600)
uvcvideo: uvc_v4l2_ioctl
v4l2 ioctl VIDIOC_G_PARM, dir=rw (0xc0cc5615)
uvcvideo: uvc_v4l2_ioctl
v4l2 ioctl VIDIOC_ENUMSTD, dir=rw (0xc0405619)
uvcvideo: Unsupported ioctl 0xc0405619
uvcvideo: uvc_v4l2_ioctl
v4l2 ioctl VIDIOC_S_STD, dir=-w (0x40085618)
uvcvideo: Unsupported ioctl 0x40085618
uvcvideo: uvc_v4l2_ioctl
v4l2 ioctl VIDIOC_ENUMINPUT, dir=rw (0xc04c561a)
uvcvideo: uvc_v4l2_ioctl
v4l2 ioctl VIDIOC_ENUMINPUT, dir=rw (0xc04c561a)
uvcvideo: uvc_v4l2_ioctl
v4l2 ioctl VIDIOC_S_INPUT, dir=rw (0xc0045627)
uvcvideo: uvc_v4l2_ioctl
v4l2 ioctl VIDIOC_QUERYBUF, dir=rw (0xc0445609)
uvcvideo: uvc_v4l2_ioctl
v4l2 ioctl VIDIOC_G_PARM, dir=rw (0xc0cc5615)
uvcvideo: uvc_v4l2_ioctl
v4l2 ioctl VIDIOC_G_FMT, dir=rw (0xc0cc5604)
BUG: unable to handle kernel paging request at virtual address ffe2
 printing eip:
f8f13af7
*pde = 4067
Oops:  [#2]
SMP
last sysfs file: /class/net/eth0/carrier
Modules linked in: uvcvideo(U) videodev v4l1_compat v4l2_common autofs4 
hidp rfcomm l2cap vmnet(U) vmmon(U) sunrpc i8k ip_conntrack_netbios_ns 
ipt_REJECT iptable_filter ip_tables xt_state ip_conntrack nfnetlink 
xt_tcpudp ip6table_filter ip6_tables x_tables cpufreq_ondemand video sbs 
i2c_ec dock button battery asus_acpi ac ipv6 parport_pc lp parport 
snd_intel8x0m snd_intel8x0 snd_ac97_codec snd_ac97_bus snd_seq_dummy 
snd_seq_oss snd_seq_midi_event snd_seq nvidia(U) snd_seq_device 
snd_pcm_oss ide_cd snd_mixer_oss snd_pcm hci_usb joydev snd_timer 
ohci1394 tg3 cdrom ieee1394 pcspkr i2c_core snd ndiswrapper(U) bluetooth 
soundcore serio_raw snd_page_alloc dm_snapshot dm_zero dm_mirror dm_mod 
ext3 jbd ehci_hcd ohci_hcd uhci_hcd
CPU:0
EIP:0060:[f8f13af7]Tainted: P  VLI
EFLAGS: 00010282   (2.6.18-1.2869.fc6 #1)
EIP is at uvc_v4l2_do_ioctl+0x5c0/0xadf [uvcvideo]
eax: d642b280   ebx: d824b180   ecx: e220540c   edx: ffe0
esi: c0cc5604   edi: 0008   ebp: f15a4030   esp: d3612e18
ds: 007b   es: 007b   ss: 0068
Process ekiga (pid: 9373, ti=d3612000 task=cc662b10 task.ti=d3612000)
Stack: 014d 40085618    000a d0590900 
f3fc0720
   d0c948a0 cc662b10 001b c04c16f7 0006 d3612e58 cc840dc0 
d3612e58
   01ef 0166 000a 06da c07e52d4 000a c0692e80 
c053e819
Call Trace:
 [f8e7cbc8] video_usercopy+0x172/0x237 

Re: [Linux-uvc-devel] fuji finepix support?

2007-01-17 Thread Laurent Pinchart
Patch attached :-)

Laurent
Index: uvc_v4l2.c
===
--- uvc_v4l2.c	(revision 76)
+++ uvc_v4l2.c	(working copy)
@@ -205,6 +205,8 @@
 	struct uvc_format *format = video-streaming-cur_format;
 	struct uvc_frame *frame = video-streaming-cur_frame;
 
+	uvc_printk(KERN_INFO, G_FMT: fmt %p format %p frame %p\n,
+		fmt, format, frame);
 	if (fmt-type != V4L2_BUF_TYPE_VIDEO_CAPTURE)
 		return -EINVAL;
 
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel