[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kopete-devel
Subject:    [kopete-devel] Kopete support for uvc
From:       Taupter <taupter () gmail ! com>
Date:       2007-01-24 9:31:10
Message-ID: 200701240631.11715.taupter () gmail ! com
[Download RAW message or body]

Hi, Alexandre.


I'm the maintainer of Kopete's video support.
Thanks for the patch! I'm reviewing it for inclusion in the SVN.
I have a question about your patch. You said you disabled V4L support if V4L2 
was detected. Trying V4L is necessary because if the V4L2 driver is 
incomplete (missing functionality) or broken the user has the option 
(configurable by the video device control panel) to try to access the video 
device in "workaround mode", and some problems with buggy drivers can be 
bypassed by this strategy. A V4L2 driver doesn't have the obligation to have 
a V4L compatibility layer, so the code tests it to be sure it will be able to 
use the device in "workaround mode" if the user asks to. The sole function of 
the "workaround mode" is to do this, so there are no device-specific 
workaround code and I advise people to be in touch with the driver's 
developers to  fix those quirks (once I found a driver that returned BGR 
images when it was asked to use GBR or RGB modes), but the size of the image 
of some cameras and the MJPEG frames were concerns to be addressed and your 
code is _very_ appreciated.
If you have ideas, reasons or strategies that would be applicable in Kopete's 
video support please stay in touch with me. I'd love to discuss about it. The 
easier way to reach me is sending an email to taupter@gmail.com or #kopete 
(freenode).


Thanks and best regards


Cláudio Pinheiro
_______________________________________________
kopete-devel mailing list
kopete-devel@kde.org
https://mail.kde.org/mailman/listinfo/kopete-devel

[prev in list] [next in list] [prev in thread] [next in thread]