[V4L] Common V4L1/V4L2 interface layer

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



Hi Everybody,

For a lot of people, the big problem with V4L2 has been the difficulty
of actually maintaining two seperate video4linux interfaces.

I have made an attempt to integrate the two interfaces in a single
layer.  This layer operates in exactly the same way (in fact, for all
practical purposes, it is the same code) as the v4l1 and v4l2 videodev
layer.  It allows both v4l1 and v4l2 device drivers to register, and
then based on the driver type, will use the correct interface layer to
talk between the user app and the driver.

This means that you should be able to do something like this:

1) Download and install videodevX (this package)
2) Download and install bttv2 or your favourite v4l2 driver.
3) modprobe bttv2
4) modprobe radio-cadet (or your favourite v4l1 driver).
5) run mp1e (on /dev/video0) and kradio (on /dev/radio0) at the same
time.

The interface layer SHOULD handle all the v4l1/2 specifics without any
user intervention.

Unfortunately, I only have a single Bt848 card (and no other v4l
devices), so I can't actually test this functionality - so if you have
multiple v4l1/2 devices, please test this out, and let me know!

-justin

Alan:  A while ago, you said something like this was required to get
v4l2 into the kernel.  Could you please have a look, and see if it was
what you were thinking of - you should be able to replace videodev.c and
videodev.h with these, without affecting the v4l1 drivers at all, but
still be able to load v4l2 drivers.





[Index of Archives]     [Linux DVB]     [Video Disk Recorder]     [Asterisk]     [Photo]     [DCCP]     [Netdev]     [Xorg]     [Util Linux NG]     [Xfree86]     [Free Photo Albums]     [Fedora Users]     [Fedora Women]     [ALSA Users]     [ALSA Devel]     [Linux USB]

Powered by Linux