[Linux-uvc-devel] Quickcam Pro 9000 LED control

2010-04-29 Thread Alan
Hello list,

I have a Quickcam Pro 9000 and I can't control the LED:

# uvcdynctrl -d video0 -s 'LED1 Mode' 0
ERROR: Unknown control specified.

Effectively, running uvcdynctrl -c doesn't show this control, but I
thought all new models supported the LED control.
Is this a hardware limitation or a software limitation?
My camera's usb id is: 046d:0809

Thanks.

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


Re: [Linux-uvc-devel] Quickcam Pro 9000 LED control

2010-04-29 Thread Alan
Thanks a lot, I ran udevadm and now the led control is working :)

By the way, I just had a thought that it would be cool to export the
led control of the webcam using leds-class:

http://www.mjmwired.net/kernel/Documentation/leds-class.txt

Alan


On Fri, Apr 30, 2010 at 12:41 AM, Paulo Assis pj.as...@gmail.com wrote:
 Hi,
 you need to import the extension controls first.

 If you have libwebcam installed try retriggering udev with udevadm
 trigger or by replugging your camera.
 For Ubuntu (at least), udev doesn't seem to work very well when cold
 plugging the webcam.

 You can also use guvcview (run it as root at least once).

 Best regards,
 Paulo

 2010/4/29 Alan lameventa...@gmail.com:
 Hello list,

 I have a Quickcam Pro 9000 and I can't control the LED:

 # uvcdynctrl -d video0 -s 'LED1 Mode' 0
 ERROR: Unknown control specified.

 Effectively, running uvcdynctrl -c doesn't show this control, but I
 thought all new models supported the LED control.
 Is this a hardware limitation or a software limitation?
 My camera's usb id is: 046d:0809

 Thanks.

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


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


[Linux-uvc-devel] Framerate of Quickcam Pro 9000

2010-04-29 Thread Alan
I have a problem with my camera: the framerate is too low.
I tested the camera using mplayer and motion with different light levels.

So I tried to fix it by following the instructions here:
http://www.quickcamteam.net/documentation/how-to/how-to-maximize-the-frame-rate

Unfortunately its still slow, and I think I messed up something
because every time I run uvcdynctrl I get this error:
[libwebcam] Unknown V4L2 private control ID encountered: 0x0A046D04
(V4L2_CID_PRIVATE_BASE + 33844484)

So I think at some moment I used an invalid parameter, so I thought I
could rmmod and modprobe uvcvideo to fix it, but no. Reconnecting the
camera doesn't help either.

So is this an invalid parameter? If so, where is it stored, in some
memory inside the camera?
And how do I fix the framerate issue?

Thanks!

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


Re: [Linux-uvc-devel] 2.6.27-rc2: uvcvideo breaks after suspend to ram

2008-08-21 Thread Alan Jenkins
Laurent Pinchart wrote:
 On Wednesday 20 August 2008, Alan Jenkins wrote:
   
 Laurent Pinchart wrote:
 
 Hi Alan,
   
 I've added a reset_resume method to the UVC driver. Could you please test
 the latest SVN revision and tell me if it helps ?
   
 Alan Stern said the problem was that USB needed to move to the new PM
 ops.  He posted a patch for this which fixed my problem (the scary
 WARNING with call-trace).

 So I'll try to test SVN but it's not very interesting :-).
 

 The warning message in the kernel log came from the USB subsystem core, but 
 the driver was also kinda faulty as it didn't implement all power management 
 callbacks (even though the missing one isn't mandatory). The two patches 
 address different issues, they are complementary.
   
Ok, thanks for both of your explanations.

I tested SVN uvcvideo on a kernel without Alans patch, and it's fine.  I
can suspend and resume without any errors.  I also checked it works
using the Kopete settings dialogue, which includes a webcam demo.

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


Re: [Linux-uvc-devel] 2.6.27-rc2: uvcvideo breaks after suspend to ram

2008-08-07 Thread Alan Jenkins
Oliver Neukum wrote:
 Am Mittwoch 06 August 2008 17:23:43 schrieb Alan Jenkins:
   
 [  290.127788] uvcvideo 1-8:1.0: no reset_resume for driver uvcvideo?
 

 [..]

   
 [  290.128909]  [c023465e] usb_rebind_intf+0x27/0x4e
 [  290.128916]  [c02346eb] do_unbind_rebind+0x4d/0x5a
 [  290.128924]  [c0234738] usb_external_resume_device+0x40/0x51
 [  290.128933]  [c020cd87] device_resume+0x8a/0x2d2
 [  290.128941]  [c01334e2] suspend_devices_and_enter+0x10f/0x138
 [  290.128954]  [c013363a] enter_state+0x10b/0x164
 [  290.128963]  [c0133721] state_store+0x8e/0xa4
 [  290.128972]  [c0133693] state_store+0x0/0xa4
 [  290.128981]  [c01a3087] kobj_attr_store+0x18/0x1c
 [  290.128991]  [c018bedc] sysfs_write_file+0xaf/0xdc
 [  290.129000]  [c018be2d] sysfs_write_file+0x0/0xdc
 [  290.129007]  [c015ec41] vfs_write+0x83/0xf6
 [  290.129016]  [c015efd2] sys_write+0x3c/0x63
 [  290.129024]  [c01035c1] sysenter_do_call+0x12/0x21
 [  290.129035]  [c02b] wait_for_common+0xe0/0xe3
 

   if (reset_resume) {
   if (driver-reset_resume) {
   status = driver-reset_resume(intf);
   if (status)
   dev_err(intf-dev, %s error %d\n,
   reset_resume, status);
   } else {
   intf-needs_binding = 1;

 It doesn't have reset_resume, so it is marked for rebinding. That in turn
 triggers the warning because the parent is still asleep. That shouldn't
 happen if we walk the device tree properly. Can you add a printk
 to device_pm_add() to print out the parent? We need to rule out that the
 device tree is bad.

   Regards
   Oliver
   
Done.  (For the record, I've posted the results at
http://bugzilla.kernel.org/show_bug.cgi?id=11263).
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel


[Linux-uvc-devel] 2.6.27-rc2: uvcvideo breaks after suspend to ram

2008-08-06 Thread Alan Jenkins

I don't use the webcam on my EeePC; I just happened to try it while
testing 2.6.27-rc2.  I don't know about any other version so this isn't
neccessarily a regression.

I think I tested it using Kopete, then later I got this warning on
resume.  I definitely didn't have Kopete open when I suspended though.

Thanks
Alan

[0.00] Linux version 2.6.27-rc2eeepc-4-gd2ceca8 ([EMAIL PROTECTED]) 
(gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #22 Wed Aug 6 14:32:25 BST 2008
[0.00] PAT disabled. Not yet verified on this CPU type.
[0.00] BIOS-provided physical RAM map:
[0.00]  BIOS-e820:  - 0009fc00 (usable)
[0.00]  BIOS-e820: 0009fc00 - 000a (reserved)
[0.00]  BIOS-e820: 000e4000 - 0010 (reserved)
[0.00]  BIOS-e820: 0010 - 1f78 (usable)
[0.00]  BIOS-e820: 1f78 - 1f79 (ACPI data)
[0.00]  BIOS-e820: 1f79 - 1f7d (ACPI NVS)
[0.00]  BIOS-e820: 1f7d - 1f7de000 (reserved)
[0.00]  BIOS-e820: 1f7e - 1f80 (reserved)
[0.00]  BIOS-e820: fee0 - fee01000 (reserved)
[0.00]  BIOS-e820: fff8 - 0001 (reserved)
[0.00] last_pfn = 0x1f780 max_arch_pfn = 0x100
[0.00] kernel direct mapping tables up to 1f78 @ 7000-d000
[0.00] NX (Execute Disable) protection: active
[0.00] RAMDISK: 1f3ff000 - 1f76ff9b
[0.00] DMI present.
[0.00] ACPI: RSDP 000FBE60, 0014 (r0 ACPIAM)
[0.00] ACPI: RSDT 1F78, 0034 (r1 A M I  OEMRSDT   1000808 MSFT  
 97)
[0.00] ACPI: FACP 1F780200, 0081 (r1 A M I  OEMFACP   1000808 MSFT  
 97)
[0.00] ACPI: DSDT 1F780400, 5F2B (r1  A0797 A07970000 INTL 
20051117)
[0.00] ACPI: FACS 1F79, 0040
[0.00] ACPI: APIC 1F780390, 0068 (r1 A M I  OEMAPIC   1000808 MSFT  
 97)
[0.00] ACPI: OEMB 1F790040, 0046 (r1 A M I  AMI_OEM   1000808 MSFT  
 97)
[0.00] ACPI: MCFG 1F786330, 003C (r1 A M I  OEMMCFG   1000808 MSFT  
 97)
[0.00] 503MB LOWMEM available.
[0.00]   mapped low ram: 0 - 1f78
[0.00]   low ram:  - 1f78
[0.00]   bootmap 1000 - 4ef0
[0.00] (7 early reservations) == bootmem [00 - 001f78]
[0.00]   #0 [00 - 001000]   BIOS data page == [00 
- 001000]
[0.00]   #1 [10 - 480194]TEXT DATA BSS == [10 
- 480194]
[0.00]   #2 [001f3ff000 - 001f76ff9b]  RAMDISK == [001f3ff000 
- 001f76ff9b]
[0.00]   #3 [481000 - 488000]INIT_PG_TABLE == [481000 
- 488000]
[0.00]   #4 [09fc00 - 10]BIOS reserved == [09fc00 
- 10]
[0.00]   #5 [007000 - 00a000]  PGTABLE == [007000 
- 00a000]
[0.00]   #6 [001000 - 005000]  BOOTMAP == [001000 
- 005000]
[0.00] Scan SMP from c000 for 1024 bytes.
[0.00] Scan SMP from c009fc00 for 1024 bytes.
[0.00] Scan SMP from c00f for 65536 bytes.
[0.00] found SMP MP-table at [c00ff780] 000ff780
[0.00] Zone PFN ranges:
[0.00]   DMA  0x - 0x1000
[0.00]   Normal   0x1000 - 0x0001f780
[0.00] Movable zone start PFN for each node
[0.00] early_node_map[2] active PFN ranges
[0.00] 0: 0x - 0x009f
[0.00] 0: 0x0100 - 0x0001f780
[0.00] On node 0 totalpages: 128799
[0.00] free_area_init_node: node 0, pgdat c03bded4, node_mem_map 
c100
[0.00]   DMA zone: 3967 pages, LIFO batch:0
[0.00]   Normal zone: 123825 pages, LIFO batch:31
[0.00] ACPI: PM-Timer IO Port: 0x808
[0.00] ACPI: Local APIC address 0xfee0
[0.00] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
[0.00] ACPI: IOAPIC (id[0x01] address[0xfec0] gsi_base[0])
[0.00] IOAPIC[0]: apic_id 1, version 32, address 0xfec0, GSI 0-23
[0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[0.00] ACPI: IRQ0 used by override.
[0.00] ACPI: IRQ2 used by override.
[0.00] ACPI: IRQ9 used by override.
[0.00] Enabling APIC mode:  Flat.  Using 1 I/O APICs
[0.00] Using ACPI (MADT) for SMP configuration information
[0.00] mapped APIC to b000 (fee0)
[0.00] mapped IOAPIC to a000 (fec0)
[0.00] PM: Registered nosave memory: 0009f000 - 000a
[0.00] PM: Registered nosave memory: 000a

[Linux-uvc-devel] New Camera Feiya Technology 090c:b370

2007-12-20 Thread Alan James
http://www.chinavasion.com/product_info.php/pName/driverless-webcam-stylish-bendable-design/

I've just got hold of three of these funky looking webcams, (the brass
version not the silver they show on the web page) but unfortunately it
doesn't just work.

uvcvideo has a go but fails to initialise the device:

usb 2-6: new high speed USB device using ehci_hcd and address 8
usb 2-6: configuration #1 chosen from 1 choice
uvcvideo: Found UVC 1.00 device USB 2.0 PC Cam (090c:b370)
nm_hal_device_added(): New device added (hal udi is
'/org/freedesktop/Hal/devices/usb_device_90c_b370_noserial').
nm_hal_device_added(): New device added (hal udi is
'/org/freedesktop/Hal/devices/usb_device___noserial').
uvcvideo: Failed to query (135) UVC control 1 (unit 0) : -110 (exp. 26).
uvcvideo: Failed to query (129) UVC control 1 (unit 0) : -110 (exp. 26).
uvcvideo: Failed to initialize the device (-5).
nm_hal_device_added(): New device added (hal udi is
'/org/freedesktop/Hal/devices/usb_device_90c_b370_noserial_if1').
nm_hal_device_added(): New device added (hal udi is
'/org/freedesktop/Hal/devices/usb_device_90c_b370_noserial_usbraw').

I'm using a stock Ubuntu 2.6.22 kernel so I wont have the latest
uvcvideo but since I don't see this device id on your supported list
I'm guessing that wont work either.
Let me know if you need to me to do anything or need more information.
lsusb output is attached.

Alan.

Bus 002 Device 008: ID 090c:b370 Feiya Technology Corp. 
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   2.00
  bDeviceClass  239 Miscellaneous Device
  bDeviceSubClass 2 Common Class
  bDeviceProtocol 1 Interface Association
  bMaxPacketSize064
  idVendor   0x090c Feiya Technology Corp.
  idProduct  0xb370 
  bcdDevice1.00
  iManufacturer   1 
  iProduct2 
  iSerial 0 
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength  439
bNumInterfaces  2
bConfigurationValue 1
iConfiguration  0 
bmAttributes 0x80
  (Bus Powered)
MaxPower  500mA
Interface Association:
  bLength 8
  bDescriptorType11
  bFirstInterface 0
  bInterfaceCount 2
  bFunctionClass 14 Video
  bFunctionSubClass   3 Video Interface Collection
  bFunctionProtocol   0 
  iFunction   0 
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   1
  bInterfaceClass14 Video
  bInterfaceSubClass  1 Video Control
  bInterfaceProtocol  0 
  iInterface  0 
  VideoControl Interface Descriptor:
bLength13
bDescriptorType36
bDescriptorSubtype  1 (HEADER)
bcdUVC   1.00
wTotalLength   77
dwClockFrequency   30.00MHz
bInCollection   1
baInterfaceNr( 0)   1
  VideoControl Interface Descriptor:
bLength18
bDescriptorType36
bDescriptorSubtype  2 (INPUT_TERMINAL)
bTerminalID 1
wTerminalType  0x0201 Camera Sensor
bAssocTerminal  0
iTerminal   0 
wObjectiveFocalLengthMin  0
wObjectiveFocalLengthMax  0
wOcularFocalLength0
bControlSize  3
bmControls   0x0004
  Auto-Exposure Priority
  VideoControl Interface Descriptor:
bLength26
bDescriptorType36
bDescriptorSubtype  6 (EXTENSION_UNIT)
bUnitID 2
guidExtensionCode {46394292-0cd1-4ae3-8783-3133f9eaaa3b}
bNumControl 3
bNrPins 1
baSourceID( 0)  1
bControlSize1
bmControls( 0)   0xff
iExtension  0 
  VideoControl Interface Descriptor:
bLength11
bDescriptorType36
bDescriptorSubtype  5 (PROCESSING_UNIT)
  Warning: Descriptor too short
bUnitID 3
bSourceID   2
wMaxMultiplier  0
bControlSize2
bmControls 0x043f
  Brightness
  Contrast
  Hue
  Saturation
  Sharpness
  Gamma
  Power Line Frequency
iProcessing 0 
bmVideoStandards 0x 9
  None
  SECAM - 625/50
  VideoControl Interface Descriptor:
bLength 9
bDescriptorType36

Re: [Linux-uvc-devel] New Camera Feiya Technology 090c:b370

2007-12-20 Thread Alan James
 The camera might have crashed when getting the first request. Please try the
 attached patch and let me know if it helps. The Failed to query (135) message
 should disappear complete. If it doesn't, you're still using the unpatched
 driver.

Thanks for your help. The driver now loads without any problems, and a
video device gets registered.

Unfortunately the errors were only delayed until I tried to use it.
This is kopete scanning the device:

uvcvideo: Failed to query (135) UVC control 2 (unit 3) : -110 (exp. 2).
uvcvideo: Failed to query (135) UVC control 3 (unit 3) : -110 (exp. 2).
uvcvideo: Failed to query (135) UVC control 7 (unit 3) : -110 (exp. 2).
uvcvideo: Failed to query (135) UVC control 6 (unit 3) : -110 (exp. 2).
uvcvideo: Failed to query (135) UVC control 9 (unit 3) : -110 (exp. 2).
uvcvideo: Failed to query (1) UVC control 1 (unit 0) : -110 (exp. 26).
uvcvideo: Failed to query (135) UVC control 2 (unit 3) : -110 (exp. 2).
uvcvideo: Failed to query (135) UVC control 3 (unit 3) : -110 (exp. 2).
uvcvideo: Failed to query (135) UVC control 7 (unit 3) : -110 (exp. 2).
uvcvideo: Failed to query (135) UVC control 9 (unit 3) : -110 (exp. 2).
uvcvideo: Failed to query (135) UVC control 6 (unit 3) : -110 (exp. 2).

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


Re: [Linux-uvc-devel] New Camera Feiya Technology 090c:b370

2007-12-20 Thread Alan James
It turns out that the GET_DEF wasn't causing the original error at
all. The old Ubuntu version of uvcvideo must be doing something
different.
So I'm now running the unpatched code I grabbed from svn earlier today
and I've got it kinda working.

luvcview -f yuv works, and once I figured out that there was a
channel 0, I got ekiga working too. The one program I wanted to use
though, kopete, still sends errors to syslog and somehow crashes the
camera too. I'll play more tomorrow.

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