Difference between revisions of "V4L framework progress"

From LinuxTVWiki
Jump to: navigation, search
(Bridge Drivers)
(Add legend and add the start of the subdev driver table)
Line 1: Line 1:
=V4l Framework Progress=
 
 
 
This page contains the status of all drivers with respect to their adoption of all the new structures that the V4L framework offers.
 
This page contains the status of all drivers with respect to their adoption of all the new structures that the V4L framework offers.
  
Line 8: Line 6:
  
 
==Bridge Drivers==
 
==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?
  
 
{| class="wikitable" style="text-align:center"
 
{| class="wikitable" style="text-align:center"
 
! driver
 
! driver
! V4L1/2
+
! V4L2
 
! v4l2_device
 
! v4l2_device
 
! video_ioctl2
 
! video_ioctl2
Line 26: Line 35:
  
 
==Sub-Device Drivers==
 
==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?
 +
 +
{| class="wikitable" style="text-align:center"
 +
! i2c driver
 +
! uses mediabus
 +
! uses init
 +
! uses reset
 +
! have hardware
 +
! comments
 +
|-
 +
| au0828
 +
| n
 +
|
 +
|
 +
| y
 +
|
 +
|}

Revision as of 12:43, 22 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.

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
ivtv 2 y 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
au0828 n y