linux-kernel - cafe_ccic: possible reason why gqcam is not working

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 23 Oct 2008 11:17:39 +0200
From:	Németh Márton <nm127@...email.hu>
To:	Jonathan Corbet <corbet@....net>
CC:	video4linux-list@...hat.com, LKML <linux-kernel@...r.kernel.org>
Subject: cafe_ccic: possible reason why gqcam is not working

Dear Jonathan,

I read in your documentation found at linux-2.6.27/Documentation/video4linux/cafe_ccic, and
found that you mention that "gqcam" is not working together with cafe_ccic.

I have done some investigation of the gqcam 0.9.1-4 found in Debian system. I wanted
to use gqcam with a different webcam and found out the following things:

 - gqcam currently only supports video4linux 1, and it uses the following
   ioctls: VIDIOCSPICT, VIDIOCSWIN, VIDIOCGCAP, VIDIOCGWIN and VIDIOCGPICT.

 - gqcam only supports read() method of getting the frames.

 - gqcam currently has a limitation that it allocates a static buffer size of
   640*480*3 bytes. This is defined in gqcam.h, struct Camera, field rawbuffer.

As I came across with this buffer limitation, I created a simple patch which at least
can warn the user about this problem instead of getting segmentation fault. The
patch available at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502350 .

I hope this helps you to track down why gqcam is not working with cafe_ccic.

Regards,

	Márton Németh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/