qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@codesourcery.com>
To: Leon Alrae <leon.alrae@imgtec.com>
Cc: qemu-devel@nongnu.org, Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] MIPS/Malta: pci_add_option_rom: failed to find romfile "efi-pcnet.rom"
Date: Thu, 11 Dec 2014 20:41:17 +0000	[thread overview]
Message-ID: <alpine.DEB.1.10.1412112029220.19155@tp.orcam.me.uk> (raw)
In-Reply-To: <5489EB80.1040908@imgtec.com>

On Thu, 11 Dec 2014, Leon Alrae wrote:

> >  The current trunk QEMU fails to run in the system emulation mode for 
> > the MIPS/Malta (mips64-softmmu) target.  It fails right away:
> > 
> > $ qemu-system -M malta -m 256 -k /dev/null -kernel vmlinux-3.2.0-4-4kc-malta -nographic -monitor null
> > qemu-system: pci_add_option_rom: failed to find romfile "efi-pcnet.rom"
> > qemu-system: Device initialization failed.
> > $ 
> 
> I'm not able to reproduce your problem. Could you please double check
> your QEMU installation? (looks like efi-pcnet.rom is missing for some
> reason)

 I see the file in the source tree, but that does not address my concern.  
The Malta board does not include any x86 firmware and so requiring one is 
IMHO the wrong way to go.  The setup should specify the onboard NIC has no 
ROM and should not require an image for it.  Having to distribute x86 
firmware with a MIPS simulator and toolchain makes no sense to me (OK, we 
could probably `dd' /dev/zero to substitute a dummy image, but that is 
more like a hack to me than a proper solution).

  Maciej

  reply	other threads:[~2014-12-11 20:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11 16:18 [Qemu-devel] MIPS/Malta: pci_add_option_rom: failed to find romfile "efi-pcnet.rom" Maciej W. Rozycki
2014-12-11 19:07 ` Leon Alrae
2014-12-11 20:41   ` Maciej W. Rozycki [this message]
2014-12-12 11:43     ` Gerd Hoffmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.1.10.1412112029220.19155@tp.orcam.me.uk \
    --to=macro@codesourcery.com \
    --cc=aurelien@aurel32.net \
    --cc=leon.alrae@imgtec.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).