While rvu can (and historically has) executed a driver as an independent
process, it is supposed to communicate with that driver via a couple of pipes.
I didn't realize that it handed over execution to qtrvu. There is a "slave
mode" that reverses operation, permitting the display driver to cal
On 3/16/16, 3:02 PM, "Georg Mischler" wrote:
>
>That sounds like a lot of duplicate work...
>
>Wouldn't it make more sense to maintain just one test suite, and
>have either build system just invoke that?
Definitely a lot of duplicate work, you're right. I was thinking maybe a
little too specifi
