------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
http://bugs.kde.org/show_bug.cgi?id=151368
taupter gmail com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |INVALID
------- Additional Comments From taupter gmail com 2008-01-08 23:21 -------
Well,
ov51x driver is V4L-only (doesn't support V4L2 ioctls), and it's the culprit.
V4L2 offers an ioctl that allows us to ask gently what pixel formats the device
supports, something V4L lacks, so we're forced to try to test every single
format under the sun until the driver agrees to operate with a given one. The
pixel format priority is set from less-expensive-to-convert-to-RGB32 (Qt's
QImage) to most-expensive. It's done to reduce processing power needed by
Kopete during webcam use.
ov51x driver is strange, because some chipsets supported by the driver send
only JPEG images, something not defined at all by the already-deprecated V4L
API (V4L defines M-JPEG, but it's a different beast), forcing software
developers to add tweaks to support it or use an alternative driver (
http://www.rastageeks.org/ov51x-jpeg/index.php/Main_Page ). As a principle bugs
must be fixed where they exist, so there's no workadounds for buggy drivers in
kopete anymore (there was only one, but it was removed), so I recommend you to
talk to ov51x developers so they see how they could help us. A good one would
be to ask them to port the driver to the V4L2 API, that has a V4L2_PIXFMT_JPEG,
has a sane way to scan for supported modules and would be one less driver using
the already deprecated V4L API.
Best regards!
_______________________________________________
kopete-devel mailing list
kopete-devel@kde.org
https://mail.kde.org/mailman/listinfo/kopete-devel
