qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Shannon Zhao <shannon.zhao@linaro.org>
Cc: Laszlo Ersek <lersek@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] ipxe and arm
Date: Thu, 12 May 2016 16:03:43 +0200	[thread overview]
Message-ID: <1463061823.14756.11.camel@redhat.com> (raw)
In-Reply-To: <5734851D.8060901@linaro.org>

  Hi,

> > I don't understand the question, sorry. How can ipxe fail if ipxe is not
> > made available to the guest, in any NIC's PCI option ROM BAR?
> What I meat to say is that on x86 user can use rtl8139 or e1000 to use
> ipxe. If uefi doesn't support rtl8139 or e1000, user can't use ipxe with
> uefi when he only uses rtl8139 or e1000.

ipxe provides efi drivers.  They are sitting in the PCI rom bar of the
qemu emulated nics and edk2 can use them just fine, on x86.  Right now
we support legacy bios, ia32 efi and x64 efi.

Now ipxe got arm and aarch64 support and the questions is whenever we
should add arm efi and/or aarch64 efi support to the nic pci roms.  I
somehow doubt it is that useful b/c I expect virtio-net being the only
relevant nic on arm virt and edk2 ships with a driver for virtio-net, so
it works fine without the ipxe driver in the rom.

hope this clarifies,
  Gerd

  reply	other threads:[~2016-05-12 14:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-11 13:03 [Qemu-devel] ipxe and arm Gerd Hoffmann
2016-05-11 13:38 ` Laszlo Ersek
2016-05-11 13:51   ` Shannon Zhao
2016-05-11 14:44     ` Laszlo Ersek
2016-05-12 13:29       ` Shannon Zhao
2016-05-12 14:03         ` Gerd Hoffmann [this message]
2016-05-13  7:37           ` Thomas Huth
2016-05-12 16:13         ` Laszlo Ersek

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=1463061823.14756.11.camel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=lersek@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=shannon.zhao@linaro.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).