I add the control print of B/C to decrease the log file for debug
options. My control print modification is in file sn9c20x-bridge.c
in function sn9c20x_set_camera_control
And look:
snip
case V4L2_CID_CONTRAST:
printk(KERN_INFO PREFIX "Value Contrast=%x\n", value);
snip
case V4L2_CID_BRIGHTNESS:
printk(KERN_INFO PREFIX "Value Brightness=%x\n", value);
snip
After inserting the module:
snip
Mar 15 11:47:20 shemet sn9c20x: SN9C20X USB 2.0 Webcam - 0C45:6270
plugged-in.
Mar 15 11:47:20 shemet sn9c20x: I2C slave 0x5d returned error during
write to address 0xff
Mar 15 11:47:20 shemet sn9c20x: Detected MT9V111 Sensor.
Mar 15 11:47:20 shemet device: 'video0': device_add
Mar 15 11:47:20 shemet PM: Adding info for No Bus:video0
Mar 15 11:47:20 shemet sn9c20x: Webcam device 0C45:6270 is now
controlling video device /dev/video0
Mar 15 11:47:20 shemet sn9c20x: Value Brightness=7f
Mar 15 11:47:20 shemet sn9c20x: Value Contrast=7f
snip
After start application:
Mar 15 11:49:17 shemet sn9c20x: Using yuv420 output format
Mar 15 11:49:17 shemet device: 'usbdev2.4_ep81': device_unregister
No preseting of B/C, picture is B/W
Contrast on 0
Mar 15 11:53:12 shemet sn9c20x: Value Brightness=7e
Contrast on 1
Mar 15 11:54:46 shemet sn9c20x: Value Contrast=0
On this case I think this is no bug in driver maybe this is bug on v4l
calls in ekiga.
But maybe startup with B/W is bug in the driver
Brian Johnson wrote:
> Boris,
> that patch will break contrast and brightness due to the fact the
>
snip
--~--~---------~--~----~------------~-------~--~----~
Lets make microdia webcams plug'n play, (currently plug'n pray)
To post to this group, send email to [email protected]
Visit us online https://groups.google.com/group/microdia
-~----------~----~----~----~------~----~------~--~---
