Em 24-12-2010 11:42, Hans Verkuil escreveu: > Hi Hans, Mauro, > > The se401, vicam, ibmcam and konicawc drivers are the only V4L1 drivers left in > 2.6.37. The others are either converted or moved to staging (stradis and cpia), > ready to be removed. > > Hans, what is the status of those four drivers? How likely is it that they will be > converted to V4L2? > > If we can't convert them to V4L2 for 2.6.38, then we can at least remove the > V4L1_COMPAT code throughout the v4l drivers and move those four drivers to staging. > > For 2.6.39 we either remove them or when they are converted to V4L2 they are moved > out of staging again (probably to gspca). > > As an illustration I have removed the V4L1_COMPAT mode in this branch: > > http://git.linuxtv.org/hverkuil/media_tree.git?a=shortlog;h=refs/heads/v4l1 Seems ok for me. > > There are two drivers that need more work: stk-webcam has some controls under sysfs > that are enabled when CONFIG_VIDEO_V4L1_COMPAT is set. These controls should be > rewritten as V4L2 controls. Hans, didn't you have hardware to test this driver? > I should be able to make a patch that you can test. The conversion seems trivial. Even knowing that none of us have that hardware, I think we should just convert it and apply the patch. We'll have the entire .38 kernel cycle for people to test. > The other driver is the zoran driver which has a bunch of zoran-specific ioctls > under CONFIG_VIDEO_V4L1_COMPAT. I think I can just delete the lot since they are > all replaced by V4L2 counterparts AFAIK. But it would be good if someone else can > also take a look at that. They seem to mimic v4l2. Also, they implement their own private API, and this is a bad thing. I doubt that most applications would use that API. So, if the driver works fine with just V4L2, I think it is ok to just remove that old code. So let's go ahead and remove, asking people to test it. I'll do some tests also in Jan. Cheers, Mauro -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
