On 23/11/2016 11:05, Edgar E. Iglesias wrote: >> > >> > But in general, the idea is that the qtest acts as the CPU. The test >> > cases can control the passing of time precisely, and they can _observe_ >> > additional events (such as interrupts or GPIO lines) but they don't inject >> > anything that the CPU cannot inject. The reason is to make the tests >> > more like small programs. It does mean that you are limited by the >> > connections of the board. > Hi Paolo, > > At some point we added support for using Qtest together with emulated > CPUs. In those cases, Qtest acts more like a test access port that can > access stuff within the VM. It can be used to test devices in combination > with guest SW. > > IMO, raising and lowering signals is useful and extending it to support > named interrupts seems like a useful feature to me...
Fair enough! Paolo
