From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:58530)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <lersek@redhat.com>) id 1b0ULN-0006HE-W2
	for qemu-devel@nongnu.org; Wed, 11 May 2016 09:38:33 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <lersek@redhat.com>) id 1b0ULG-0003RE-K5
	for qemu-devel@nongnu.org; Wed, 11 May 2016 09:38:28 -0400
Received: from mx1.redhat.com ([209.132.183.28]:56398)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <lersek@redhat.com>) id 1b0ULG-0003R9-EM
	for qemu-devel@nongnu.org; Wed, 11 May 2016 09:38:22 -0400
Received: from int-mx14.intmail.prod.int.phx2.redhat.com
	(int-mx14.intmail.prod.int.phx2.redhat.com [10.5.11.27])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by mx1.redhat.com (Postfix) with ESMTPS id 041D380E4A
	for <qemu-devel@nongnu.org>; Wed, 11 May 2016 13:38:22 +0000 (UTC)
References: <1462971832.5679.50.camel@redhat.com>
From: Laszlo Ersek <lersek@redhat.com>
Message-ID: <0dc66f36-97c7-f207-f0ba-4c4b99e20c6d@redhat.com>
Date: Wed, 11 May 2016 15:38:20 +0200
MIME-Version: 1.0
In-Reply-To: <1462971832.5679.50.camel@redhat.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] ipxe and arm
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel/>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel <qemu-devel@nongnu.org>

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.

Thanks
Laszlo