qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Shannon Zhao <shannon.zhao@linaro.org>,
	Gerd Hoffmann <kraxel@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] ipxe and arm
Date: Wed, 11 May 2016 16:44:32 +0200	[thread overview]
Message-ID: <2ee0c33a-81e9-dea9-9f28-bd1344cf936b@redhat.com> (raw)
In-Reply-To: <573338F8.9080200@linaro.org>

On 05/11/16 15:51, Shannon Zhao wrote:
> On 2016年05月11日 21:38, Laszlo Ersek wrote:
>> On 05/11/16 15:03, Gerd Hoffmann wrote:
>>>   Hi,
>>>
>>> ipxe gained support for arm and aarch64 efi platforms.  So we could add
>>> support to our nic pci roms with the next ipxe update.
>>>
>>> But: The question is whenever that makes sense in the first place.
>>> Support for virtio-net is in edk2, so that is covered already.  The
>>> other pci nics are not, but given that virtio-net predates arm
>>> virtualization all guests should be able to handle virtio-net just fine.
>>> And I doubt anybody seriously prefers rtl8139 or e1000 over virtio-net
>>> unless the lack of guest driver support mandates it ...
>>>
>>> Comments anyone?
>>
>> AFAIK all aarch64 OS installers will come with virtio-net drivers on the
>> install media.
>>
> But if the user doesn't specify a virtio-net nic, then ipxe will fail,
> right?

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?

Thanks
Laszlo

  reply	other threads:[~2016-05-11 14:44 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 [this message]
2016-05-12 13:29       ` Shannon Zhao
2016-05-12 14:03         ` Gerd Hoffmann
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=2ee0c33a-81e9-dea9-9f28-bd1344cf936b@redhat.com \
    --to=lersek@redhat.com \
    --cc=kraxel@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).