Ronald,
On Tue, 17 Apr 2007 13:13:19 -0400, Ronald S. Bultje wrote:
> could you test (using the debug options in the driver) whether it's
> using v4l1 vs. v4l2? If it's using v4l2, could you test whether
> making it use v4l1 (see man xawtv or so) makes a difference?
I've set the zr36067 debug level to 3, but nothing in the kernel logs
tells me whether the device is doing v4l1 or v4l2. However, xawtv
itself seems to be thinking that it's v4l2:
$ xawtv -hwscan
This is xawtv-3.95, running on Linux/x86_64 (2.6.21-rc7)
looking for available devices
port 65-65 [ -xvport 65 ]
type : Xvideo, video overlay
type : Xvideo, image scaler
name : ATI Radeon Video Overlay
/dev/video0: OK [ -device /dev/video0 ]
type : v4l2
name : DC10plus[0]
flags: overlay capture
And "xawtv -device /dev/video0 -debug 1" says:
vid-open: trying: v4l2-old...
vid-open: failed: v4l2-old
vid-open: trying: v4l2...
v4l2: open
v4l2: device info:
zoran 0.9.5 / DC10plus[0] @ PCI:0000:00:09.0
vid-open: ok: v4l2
So it definitely looks like v4l2 to me. I couldn't find any option to
force xawtv to handle the DC10+ as a v4l1 device. I found that v4l-conf
has a flag (-1) to force the v4l1 API however it doesn't seem to have
any effect on xawtv, which still treats my device as v4l2.
So is it possible to force v4l1 at all? Or is it possible to prevent
the zr36067 driver from advertising itself as v4l2, so that xawtv
doesn't have the choice?
--
Jean Delvare
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Mjpeg-users mailing list
Mjpeg-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mjpeg-users
