>>> Yes, there will likely be heavy merge conflicts... >>> In which tree are the videobuf2 patches ? >> It's in a private tree right now, and it doesn't support VBI >> currently. Once I've setup a public tree with yours and Hans changes, >> I'll start merging in my changes. > > I suggest to do the conversion on top of my patches, as they should make > things much easier for you. > I unified the handling of the VBI and video buffers, leaving just a few > common functions dealing with the videobuf stuff. Yup, that's exactly what I had planned. > In any case, we should develop against a common tree with a minimum > number of pending patches. > And we should coordinate development. > I don't work on further changes of the frame processing stuff at the moment. > Some I2C fixes/changes will be next. After that, I will try to fix > support for remote controls with external IR IC (connected via i2c). > >> Obviously it would be great for you to test with your webcam and make >> sure I didn't break anything along the way. > > Sure, I will be glad to test your changes. > >> I've also got changes to support V4L2_FIELD_SEQ_TB, which is needed in >> order to take the output and feed to certain hardware deinterlacers. >> In reality this is pretty much just a matter of treating the video >> data as progressive but changing the field type indicator. > > Ok, so I assume most of the changes will happen in em28xx_copy_video(). The changes really are all over the tree because it's not just vb2 support but also support for v4l2_fh, which means every ioctl() has a change to its arguments, and there is no longer an open/close call implemented. Also significant impact on the locking model. > Maybe we can then use a common copy function for video and VBI. Placing > the field data sequentially in the videobuf is what we already do with > the VBI data in em28xx_copy_vbi() Let's get something that works, at which point we can tune/optimize as needed. Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com -- 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
