From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35299) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b17fh-0001EV-Cy for qemu-devel@nongnu.org; Fri, 13 May 2016 03:38:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b17fd-00024O-4i for qemu-devel@nongnu.org; Fri, 13 May 2016 03:38:04 -0400 Received: from mx1.redhat.com ([209.132.183.28]:32885) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b17fc-00024I-VU for qemu-devel@nongnu.org; Fri, 13 May 2016 03:38:01 -0400 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (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 B89B03B71D for ; Fri, 13 May 2016 07:37:59 +0000 (UTC) Received: from [10.36.7.225] (vpn1-7-225.ams2.redhat.com [10.36.7.225]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u4D7bvYV028655 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 13 May 2016 03:37:59 -0400 References: <1462971832.5679.50.camel@redhat.com> <0dc66f36-97c7-f207-f0ba-4c4b99e20c6d@redhat.com> <573338F8.9080200@linaro.org> <2ee0c33a-81e9-dea9-9f28-bd1344cf936b@redhat.com> <5734851D.8060901@linaro.org> <1463061823.14756.11.camel@redhat.com> From: Thomas Huth Message-ID: <57358455.3030301@redhat.com> Date: Fri, 13 May 2016 09:37:57 +0200 MIME-Version: 1.0 In-Reply-To: <1463061823.14756.11.camel@redhat.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] ipxe and arm List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On 12.05.2016 16:03, Gerd Hoffmann wrote: > Hi, >=20 >>> 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 wi= th >> uefi when he only uses rtl8139 or e1000. >=20 > 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. >=20 > 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. Simply add a EFI byte code (EBC) driver to the PCI ROM, then you're done for all future UEFI based platforms ;-) /me ducks and covers Thomas