On Fri, 19 Jul 2019 at 02:58, Palmer Dabbelt <pal...@sifive.com> wrote: > > The following changes since commit 0b18cfb8f1828c905139b54c8644b0d8f4aad879: > > Update version for v4.1.0-rc1 release (2019-07-16 18:01:28 +0100) > > are available in the Git repository at: > > git://github.com/palmer-dabbelt/qemu.git tags/riscv-for-master-4.1-rc2 > > for you to fetch changes up to fdd1bda4b47cfbec61d0e63a516c614feea0b00b: > > hw/riscv: Load OpenSBI as the default firmware (2019-07-18 14:18:45 -0700) > > ---------------------------------------------------------------- > RISC-V Patches for 4.2-rc2 > > This contains a pair of patches that add OpenSBI support to QEMU on > RISC-V targets. The patches have been floating around for a bit, but > everything seems solid now. These pass my standard test of booting > OpenEmbedded, and also works when I swap around the various command-line > arguments to use the new boot method. > > ---------------------------------------------------------------- > Alistair Francis (2): > roms: Add OpenSBI version 0.4 > hw/riscv: Load OpenSBI as the default firmware
This passes the 'make check' tests but it prints out a lot of warnings as it does so: qemu-system-riscv64: warning: No -bios option specified. Not loading a firmware. qemu-system-riscv64: warning: This default will change in QEMU 4.3. Please use the -bios option to aviod breakages when this happens. qemu-system-riscv64: warning: See QEMU's deprecation documentation for details (repeated 7 or 8 times during the course of a test run) Can we make the tests not trigger warnings, please? (I have a filter where I search through for strings like "warning" because warnings that shouldn't happen often don't actually cause the tests to fail.) Also, I notice that you have a typo: "aviod" should be "avoid". PS: something in your pull-request creation process seems to add this junk at the bottom of the pullreq emails, though since it doesn't appear in the merge commit it's harmless: > From Palmer Dabbelt <pal...@sifive.com> # This line is ignored. > From: Palmer Dabbelt <pal...@sifive.com> > Reply-To: > Subject: > In-Reply-To: thanks -- PMM