Max Filippov <jcmvb...@gmail.com> writes: > On Tue, Aug 7, 2012 at 11:26 PM, Markus Armbruster <arm...@redhat.com> wrote: >> Very basic smoke test: start QEMU with -monitor stdio, quit immediately. >> Wouldn't it be nice if that worked for all targets and machine types? >> >> Many targets have mandatory options (fun oxymoron), such as -kernel or >> -pflash. Can't stop me, I just try a bunch until something works. >> >> Many targets expect various files to be present, and some of them need >> to have the right size. Can't stop me, I hack up the file loaders until >> it works (silly patch appended). To do this right, we'd need the >> required files or suitable mock-ups in-tree. > > [...] > >> Summary of results: >> >> * Bad unexplained > >> qemu-system-xtensaeb lx60 >> qemu-system-xtensaeb lx200 >> qemu-system-xtensaeb sim >> Unable to find CPU definition >> >> I'm not saying these are all busted. If you know how to "start to >> monitor" one of these, let us know. > > For xtensa the default CPU name is the same for both big-endian and > little-endian binaries, but actually it denotes little-endian CPU not > supported > by xtensaeb. It will start with the explicit -cpu fsf. I can post a patch to > make fsf the default CPU type in big-endian case.
Sounds worthwhile to me.
