tree c3c236b322663c2fd52bd63d573e3a67f70bddb9
parent 1d57485a119ba7f4773da1ec8b653a66ba52b624
author subrata_modak <subrata_modak> 1230622373 +0000
committer subrata_modak <subrata_modak> 1230622373 +0000

Linux drivers based on Video for Linux Two (V4L2) API, test addition:
Németh Márton <nm127@freemail.hu> wrote:
I started a project to test the Linux drivers based on Video for Linux Two (V4L2) API, release 0.24. This project is using the CUnit framework and is available at http://v4l-test.sourceforge.net/. I found your project at http://ltp.sourceforge.net/ . As far as I know the LTP currently do not have any tests for V4L2. Maybe test cases created for v4l-test project can be used for LTP also. What do you think?
Subrata Modak <subrata@linux.vnet.ibm.com> wrote back:
Yes, it can be. We have a rather old code base for Device Drivers testing. And time and again i was trying to revive the device drivers tests inside LTP, but, did not get sufficient volunteers to do the same. Your test code can be a starting point for us. I downloaded your testsuite and was able to compile the stuff, with some modification(s). However, i did not test it. Can you also share the logs of the run on your machine ?? More info is required in the documentation. I have prepared a patch(attached & embedded), which will integrate these tests inside LTP with minor modifications in documentation and some #defines in some source files (to be able to compile on machines not having respective header files containing the definition). Now, we have 2 choices:
1) You can voluntarily allow us to maintain this code inside LTP. Send your patches/modifications to us, whenever you want to add/modify/remove any tests out of: ltp/testcases/kernel/device-drivers/v4l-test/, We will then do the needful. You benefit by showcasing your test code to a bigger LTP community, and hence can attract more contribution from them. We gain by re-introducing/re-starting device drivers testing, which can then move to other device drivers as well. If you agree, please reply to this mail with a DCO Sign-off:  Signed-Off-By: Németh Márton <nm127@freemail.hu>, I can then go ahead and include this patch.
2) You can keep your project running at: http://v4l-test.sourceforge.net/, as well as agree to apply this patch to include in LTP. In such a case, send us updates whenever you update your project. In any case, i  would require a DCO Sign-off: Signed-Off-By: Németh Márton <nm127@freemail.hu>,  from you. I would like to thank you for deciding to contribute this to LTP, and would also request you to help us fix the  existing device drivers tests in LTP, so that we can start using them. If necessary we can delete the obsolete ones and add new ones: http://ltp.cvs.sourceforge.net/viewvc/ltp/ltp/testcases/kernel/device-drivers/. Do you think, you will also be able to help us here ??
Németh Márton <nm127@freemail.hu> wrote back:
Yes, sorry about that. I have had no access to my emails during the last days. I also wanted to think about this a little. I would like to choose the 2nd solution: I try to run my project forward and send you patches to include them in LTP. The source code and the test design was created by me. However, the V4L2 API specification which is also included in the tarball is only downloaded and saved under the 'doc' directory so I always have a local copy of the V4L2 API revision 0.24. This you might not want to include in the LTP source code. I had some difficulties with the inline patch you sent me, it was not usable at my side because my email client was not able to handle it correctly. Could you please send it as an attachment? What I could recognised that the v4l-test project was placed in LTP source directory under ltp-intermediate-20081223.orig/testcases/kernel/device-drivers/v4l-test . However, if I look around in the "device-drivers" subdirectory I would use the subdirectory: ltp/testcases/kernel/device-drivers/v4l/user_space . What do you think? Signed-Off-By: Márton Németh <nm127@freemail.hu>.