On Mon, Sep 18, 2017 at 11:33:01AM -0600, Stephen Warren wrote: > On 09/17/2017 01:32 PM, Heinrich Schuchardt wrote: > >The necessary parameters for running Python tests on qemu are > >tediouus to find. > > > >The patch adds examples for u-boot-test-console and > >u-boot-test-reset. > > This README doesn't contain examples for other cases. I'm not sure > whether we should add them for qemu either. Instead, does it make > sense to augment my repo, which already contains a variety of > examples, and is mentioned in the README? > > https://github.com/swarren/uboot-test-hooks > > Tom Rini already added some qemu examples to that repo, although > they use much simpler command-lines than in the examples in this > patch. Perhaps that's because they fire off a new qemu instance > every time the virtual system is reset, whereas yours seem to create > one qemu instance and then reset it multiple times. If so, your > scripts are more how I imagined it would work; perhaps you could > update Tom's scripts?
I was thinking about this too. Heinrich's example is along the lines of "adapt QEMU to provide what test.py wants" while the uboot-test-hooks QEMU parts are more along the lines of "plumb QEMU into the frameworks for real HW too". What I like about the latter is that I leverage information from my real HW too (tftp stuff, etc). Why I think we should also apply Heinrich's patch, or maybe a v2 with a few wording tweaks, is that it's less overhead and easier for people to setup if they just want QEMU available for testing. Say testing while on the road at some conference. -- Tom
signature.asc
Description: Digital signature
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
