From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:40853) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xu8Jg-0001LT-65 for qemu-devel@nongnu.org; Thu, 27 Nov 2014 18:17:46 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xu8Ja-0006OO-2V for qemu-devel@nongnu.org; Thu, 27 Nov 2014 18:17:40 -0500 Received: from mx1.redhat.com ([209.132.183.28]:53602) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xu8JZ-0006OD-RX for qemu-devel@nongnu.org; Thu, 27 Nov 2014 18:17:34 -0500 Message-ID: <5477B0FD.9040806@redhat.com> Date: Fri, 28 Nov 2014 00:17:17 +0100 From: Laszlo Ersek MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] expose QEMU's fw_cfg boot order to ARM guest firmware (Intel BDS) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu devel list , edk2-devel list Cc: Peter Maydell , Drew Jones , "Michael S. Tsirkin" , Igor Mammedov , Ard Biesheuvel Hi, this message is meant as a short, cross-posted thread starter, so that both qemu- and edk2-side comments can be kept in one thread. I'll follow up with two series: - the first small series for qemu adds fw_cfg to the arm "virt" machine type in qemu, automatically exposing the "bootorder" fw_cfg file to the guest (when at least one bootindex=N device property is specified on the command line), - the second, not so small, dependent series for edk2: - adds an MMIO-based fw_cfg client to the ARM guest firmware in edk2, - makes the OpenFirmware-to-UEFI devpath translation stuff in OvmfPkg reusable for the ArmVirtualizationQemu platform, - makes the virtio-pci specific bits in that logic conditional, and introduces (similarly conditional) coverage for virtio-mmio. Thanks Laszlo