After running the automated camera module tests and digging through the printout, it looks like there is a bug with the ICamera2ModuleControl interface. All of the get methods are returning -1 values. Additionally, all of the set methods are also returning -1 for their IOCTL returns. The other camera module interfaces seem to be working correctly. This may be a bug on my end since I am just porting my test suite over to 3.0 for the first time. Let me know if you think that's the case.
-Davis
Pastes:
Example Code: http://pastebin.com/BGZtvWB6
Example Printout: http://pastebin.com/97hRvR8q
-Still trying to work out the formatting on my tests' printouts. This printout shows the returns for the last 'get' method and then the printouts for each of the 'set' methods followed by their errors/failures
After running the automated camera module tests and digging through the printout, it looks like there is a bug with the ICamera2ModuleControl interface. All of the get methods are returning -1 values. Additionally, all of the set methods are also returning -1 for their IOCTL returns. The other camera module interfaces seem to be working correctly. This may be a bug on my end since I am just porting my test suite over to 3.0 for the first time. Let me know if you think that's the case.
-Davis
Pastes:
Example Code: http://pastebin.com/BGZtvWB6
Example Printout: http://pastebin.com/97hRvR8q
-Still trying to work out the formatting on my tests' printouts. This printout shows the returns for the last 'get' method and then the printouts for each of the 'set' methods followed by their errors/failures