Difference between revisions of "V4L framework progress"

From LinuxTVWiki
Jump to: navigation, search
(Bridge Drivers)
(Bridge Drivers)
Line 152: Line 152:
 
| y  
 
| y  
 
| y
 
| y
|
+
| radio only
 
|-
 
|-
 
| em28xx
 
| em28xx
Line 285: Line 285:
 
| y
 
| y
 
| n
 
| n
|
+
| radio only
 
|-
 
|-
 
| radio-aztech
 
| radio-aztech
Line 292: Line 292:
 
| y
 
| y
 
| n
 
| n
|
+
| radio only
 
|-
 
|-
 
| radio-cadet
 
| radio-cadet
Line 299: Line 299:
 
| y
 
| y
 
| n
 
| n
|
+
| radio only
 
|-
 
|-
 
| radio-gemtek
 
| radio-gemtek
Line 306: Line 306:
 
| y
 
| y
 
| y
 
| y
|
+
| radio only
 
|-
 
|-
 
| radio-gemtek-pci
 
| radio-gemtek-pci
Line 313: Line 313:
 
| y
 
| y
 
| n
 
| n
|
+
| radio only
 
|-
 
|-
 
| radio-maestro
 
| radio-maestro
Line 320: Line 320:
 
| y
 
| y
 
| n
 
| n
|
+
| radio only
 
|-
 
|-
 
| radio-maxiradio
 
| radio-maxiradio
Line 327: Line 327:
 
| y
 
| y
 
| n
 
| n
|
+
| radio only
 
|-
 
|-
 
| radio-miropcm20
 
| radio-miropcm20
Line 334: Line 334:
 
| y
 
| y
 
| n
 
| n
|
+
| radio only
 
|-
 
|-
 
| radio-mr800  
 
| radio-mr800  
Line 341: Line 341:
 
| y  
 
| y  
 
| y
 
| y
|
+
| radio only
 
|-
 
|-
 
| radio-rtrack2
 
| radio-rtrack2
Line 348: Line 348:
 
| y
 
| y
 
| n
 
| n
|
+
| radio only
 
|-
 
|-
 
| radio-sf16fmi
 
| radio-sf16fmi
Line 355: Line 355:
 
| y
 
| y
 
| n
 
| n
|
+
| radio only
 
|-
 
|-
 
| radio-sf16fmr2
 
| radio-sf16fmr2
Line 362: Line 362:
 
| y
 
| y
 
| n
 
| n
|
+
| radio only
 
|-
 
|-
 
| radio-si470x
 
| radio-si470x
Line 369: Line 369:
 
| y  
 
| y  
 
| y
 
| y
|
+
| radio only
 
|-
 
|-
 
| radio-si4713
 
| radio-si4713
Line 376: Line 376:
 
| y
 
| y
 
| n
 
| n
|
+
| radio transmitter only
 
|-
 
|-
 
| radio-tea5764
 
| radio-tea5764
Line 383: Line 383:
 
| y  
 
| y  
 
| y
 
| y
|
+
| radio only
 
|-
 
|-
 
| radio-terratec
 
| radio-terratec
Line 390: Line 390:
 
| y
 
| y
 
| n
 
| n
|
+
| radio only
 
|-
 
|-
 
| radio-timb
 
| radio-timb
Line 397: Line 397:
 
| y
 
| y
 
| n
 
| n
|
+
| radio only
 
|-
 
|-
 
| radio-trust
 
| radio-trust
Line 404: Line 404:
 
| y
 
| y
 
| n
 
| n
|
+
| radio only
 
|-
 
|-
 
| radio-typhoon
 
| radio-typhoon
Line 411: Line 411:
 
| y
 
| y
 
| n
 
| n
|
+
| radio only
 
|-
 
|-
 
| radio-zoltrix
 
| radio-zoltrix
Line 418: Line 418:
 
| y
 
| y
 
| n
 
| n
|
+
| radio only
 
|-
 
|-
 
| s2255drv
 
| s2255drv

Revision as of 09:41, 23 March 2010

This page contains the status of all drivers with respect to their adoption of all the new structures that the V4L framework offers.

This should help in identifying those drivers that need more work.

It is expected that this page will be continuously updated whenever new conversion tasks appear.

Note: the driver lists are not yet complete. This is work in progress.

Bridge Drivers

driver

The driver name

V4L2

Whether the driver implements the V4L2 API or still uses the old V4L1 API

v4l2_device

Whether the driver uses struct v4l2_device

video_ioctls

Whether the driver uses the video_ioctl2 fops .ioctl op

have hardware

Can someone test this driver?

driver V4L2 v4l2_device video_ioctl2 have hardware comments
arv 1 n n n
au0828 2 y y y
av7110 2 y y y
bttv 2 y y y
budget-av 2 y y y
bw-qcam 1 n n n
c-qcam 1 n n y
cafe_ccic 2 y y y
cpia_pp 1 n n n
cpia_usb 1 n n n deprecated, replaced by gspca
cpia2 2 n n y
cx18 2 y y y
cx25821 2 y y y staging driver
cx231xx 2 y y y
cx23885 2 y y y
cx88 2 y y y
davinci 2 y y y
dsbr100 2 y y y radio only
em28xx 2 y y y
et61x251 2 n n y
go7007 2 y y y staging driver
gspca 2 n y y
hdpvr 2 y y y
hexium_gemini 2 y y n
hexium_orion 2 y y n
ibmcam 1 n n y
ivtv 2 y y y
konicawc 1 n n n
meye 2 n y n
mxb 2 y y y
omap24xcam 2 n y y still uses v4l2-int-device
ov511 1 n n y deprecated, replaced by gspca
pms 2 y y y
pvrusb2 2 y y y
pwc 2 n n y
quickcam_messenger 1 n n y deprecated, replaced by gspca
radio-aimslab 2 y y n radio only
radio-aztech 2 y y n radio only
radio-cadet 2 y y n radio only
radio-gemtek 2 y y y radio only
radio-gemtek-pci 2 y y n radio only
radio-maestro 2 y y n radio only
radio-maxiradio 2 y y n radio only
radio-miropcm20 2 y y n radio only
radio-mr800 2 y y y radio only
radio-rtrack2 2 y y n radio only
radio-sf16fmi 2 y y n radio only
radio-sf16fmr2 2 y y n radio only
radio-si470x 2 n y y radio only
radio-si4713 2 y y n radio transmitter only
radio-tea5764 2 n y y radio only
radio-terratec 2 y y n radio only
radio-timb 2 y y n radio only
radio-trust 2 y y n radio only
radio-typhoon 2 y y n radio only
radio-zoltrix 2 y y n radio only
s2255drv 2 n y  ?
saa7134 2 y y y
saa7164 2 y y y
se401 1 n n y
sn9c102 2 n n  ?
soc_camera 2 n y y
stk-webcam 2 y n  ?
stradis 1 n n n
stv680 1 n n y deprecated, replaced by gspca
tea575x-tuner 2 n y n
tm6000 2 y y y staging driver
usbvision 2 y y y
uvc 2 n n y
vicam 1 n n y
vino 2 y y  ?
vivi 2 y y y
w9966 1 n n n
w9968cf 1 n n y deprecated, replaced by gspca
zc0301 2 n n n
zoran 2 y y y
zr364xx 2 n y y

Sub-Device Drivers

subdev driver

The sub-device driver name

uses mediabus

Whether the driver implements the new *_mbus_fmt subdev ops

uses init

Whether the driver uses the deprecated .core init op

uses reset

Whether the driver uses the deprecated .core reset op

have hardware

Can someone test this i2c driver?

i2c driver uses mediabus uses init uses reset have hardware comments
adv7170 n/a n n