From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-x22f.google.com (mail-wr0-x22f.google.com [IPv6:2a00:1450:400c:c0c::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 3B00721A02F37 for ; Mon, 12 Jun 2017 12:49:15 -0700 (PDT) Received: by mail-wr0-x22f.google.com with SMTP id g76so108344126wrd.1 for ; Mon, 12 Jun 2017 12:50:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=iL3Uu8peujpHrC4lr4tdj8UzV1FSWtX1Wil0McO+7Hc=; b=D/KOIUmfyqsYQssj5CdyXKZ65uYBUBQUqlrD/g6A34SfX1Stn2x/f4nCcLdcCBbAdR cWqM5p+wSus2HhHoBTPowGM4kYFQSEqlWsHnz4BsU+WIvU74aopF4XOF47vA8DQTdPYM lNsiRKqcrRHqWA/rB2kcjG9afqNH0RhjNKH1g= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=iL3Uu8peujpHrC4lr4tdj8UzV1FSWtX1Wil0McO+7Hc=; b=Wtn/5gQ3T4DaYtzwJs6B/38RIqgqrE3T+bIH0AU0AOG+JnhxZXYS509JwfgMkZal0T 2EPyw9XuVvepLNv0x79SL/fmQFk3ZtkQh+oiWgU0P9q/SoW2YgXD3ouIkA4rUOTApd0T DCEpOrO+x2EI9v5qOHaNBmMLYlhT9BMN3trgYswRKPAXXPqA0fznx1TlXuL7iiRHivvS 8Hm3RDlcCkpdYcP8sjwZit5hvu0YAesVocTj/lrkGDhyOf8o3c58LRsXTRHhAueSPzW8 jwYwFpIC18dKuI5Q3VdN/NPFFG9eejogQTdqwA8KEFd1E10DXxj5uF/nGLBSY4qFEZ0h NESA== X-Gm-Message-State: AKS2vOzj2eArKCIJBOVmxFPrdYbvaafqNkycxPY6lNm06qoSCTWq0vCU L2BYVHSfBEEGvg3i46DT3w== X-Received: by 10.223.163.93 with SMTP id d29mr388549wrb.95.1497297027057; Mon, 12 Jun 2017 12:50:27 -0700 (PDT) Received: from [1.1.3.70] ([185.23.97.10]) by smtp.gmail.com with ESMTPSA id z184sm15977418wmz.0.2017.06.12.12.50.25 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 12 Jun 2017 12:50:26 -0700 (PDT) Mime-Version: 1.0 (1.0) From: Ard Biesheuvel X-Mailer: iPhone Mail (14D27) In-Reply-To: <2c75cb93-d4ee-15bd-637e-b883f7380731@redhat.com> Date: Mon, 12 Jun 2017 21:50:19 +0200 Cc: Andre , "edk2-devel@lists.01.org" , "Leif Lindholm (Linaro address)" Message-Id: <1797349F-FF4A-48B0-B057-D23231309A2E@linaro.org> References: <2c75cb93-d4ee-15bd-637e-b883f7380731@redhat.com> To: Laszlo Ersek Subject: Re: Can OVMF run on an emulated QEMU ARM vexpress-a9? X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jun 2017 19:49:15 -0000 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > On 12 Jun 2017, at 21:38, Laszlo Ersek wrote: > > (side track) > >> On 06/12/17 18:40, Ard Biesheuvel wrote: >> On 12 June 2017 at 18:28, Laszlo Ersek wrote: > >>> - ArmVirtPkg/ArmVirtQemuKernel.dsc: >>> >>> - Not really sure about the QEMU configuration for this, but see >>> commit 8de84d424221 ("ArmVirtPkg: implement ArmVirtQemuKernel", >>> 2016-02-05) for the intended use. I think Ard can explain it better. >>> >> >> The standard mach-virt machine you get when using -bios boots with the >> firmware image exposed as an emulated XIP NOR flash. Many ARM systems >> that boot with ARM trusted firmware don't run UEFI in place but load >> it into DRAM and execute it from there. >> >> So ArmVirtQemuKernel runs from DRAM instead. It borrows the Linux >> kernel boot protocol to achieve this, since it was already implemented >> by QEMU via -kernel (and -bios/-pflash omitted) > > Ah! So you boot that firmware binary itself with the "-kernel" option; > is that right? > > (I guess I'll finally understand why you called the DSC file > "ArmVirtQemuKernel" :) ) > > Yes :-)