Hi Tomi, Apologies that I didn't make it particularly clear, but I should have prefixed this series title with a nice big [RFC] :-D This is ongoing work to support loop-back validation on our platforms. Regards Kieran On 13/12/17 23:10, Kieran Bingham wrote: > From: Kieran Bingham <kieran.bingham@xxxxxxxxxxxxxxxx> > > Our kms-tests test suite for verifying the R-Car DU is based on kmsxx. > > We are implementing a 'loop-back' validator, by providing an HDMI cable from > the display output directly into the HDMI receiver on the same development > board. > > By using the existing VideoStreamer and pyvid objects, we can capture the output > and compare to provide automated display validation. > > As an effort to commence this process, this series implements a basic frame > buffer comparison, which expects identical frame sizes to operate. > > This could be could be expanded upon later to provide a more detailed > comparison at the pixel level later, but this serves as an initial starting > point to quickly verify if the data captured matches the data that we expected. > > Kieran Bingham (4): > videodevice: Fix minor spacing > py: pyvid: Provide stream_off binding > kms++util: Add verification module > kms++util: Add frame compare functionality > > kms++util/inc/kms++util/kms++util.h | 3 ++- > kms++util/src/verification.cpp | 52 ++++++++++++++++++++++++++++++- > kms++util/src/videodevice.cpp | 2 +- > py/pykms/pykmsutil.cpp | 7 ++++- > py/pykms/pyvid.cpp | 1 +- > 5 files changed, 64 insertions(+), 1 deletion(-) > create mode 100644 kms++util/src/verification.cpp > > base-commit: fee73296cae1a4984e18c8d8ee8e50ab217b1e4a >
