From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=2607:f8b0:4001:c0b::241; helo=mail-it0-x241.google.com; envelope-from=ard.biesheuvel@linaro.org; receiver=edk2-devel@lists.01.org Received: from mail-it0-x241.google.com (mail-it0-x241.google.com [IPv6:2607:f8b0:4001:c0b::241]) (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 B69CB2034D8E8 for ; Wed, 28 Feb 2018 00:13:38 -0800 (PST) Received: by mail-it0-x241.google.com with SMTP id u66so141456ith.1 for ; Wed, 28 Feb 2018 00:19:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=1L6WdHZLlPmNYkiJxoCmAGtd6FEwjgryKIWmK8Ett80=; b=SxN5gZZOp+x4hPRgE3zDuaearU9rXAZgPTyOQGErtjfOa6HJxBlE8cs82STm4RP39i qa+E3u2n0/h1j2+63mUXERvOqDAEDCJlTd+S0PfsJ4E2U8mmQs3HjDSJFzIf6P07Yglb s2gb+pXOUw3VurAQVBU1bGnbVu4VkPJ5pFRhA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=1L6WdHZLlPmNYkiJxoCmAGtd6FEwjgryKIWmK8Ett80=; b=I9+zJOKPt1HMSUYopKiZZErgKxXztN7ntlMaiL1Wses95XLOLbajBGOBRrqizUZzYA N7BDD45pNdSdWR0C7u78GZPe8hgKIIrvKymDfhfcXCSPfeTEH/bIWmWaVC1wgltuPuO6 T8+cIjBpwLtnYN05G4lZ2Ofpem9dR7Q7odjLgMHfAQ5ry4lUObTAE+4jxuSjF3g4ObZu L9WM1ORQjzPBKjdZKT+Ww+g011MhShEx+R4XfaZxca/95772OvlFSd8i2f2cQ+WZ5CRj TvQ7Pumu48NRnan0M8QBpgaYTBjZexmyqgtwu4SqlFQUVCyYmZ9me1DpI5Pw9iJas5AE 7/wg== X-Gm-Message-State: APf1xPCVgKn65pAfXmfjmaxyoLM9BLaTrgIb4Xb46+XuMFrXOcnt02Zo t4uLlazR1ttJXDLwy/rV4KAdFE9VnXplDAyRx5CGsw== X-Google-Smtp-Source: AH8x226Qrn4TYS5i4lJEYju4qW1SkIDNAWPz8T/NxtFiOVy0ZXoNQW4kQAoDtS2RPtpV+gRFmMHD697e+eyA3URZpMw= X-Received: by 10.36.91.138 with SMTP id g132mr20014070itb.50.1519805985127; Wed, 28 Feb 2018 00:19:45 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.138.209 with HTTP; Wed, 28 Feb 2018 00:19:44 -0800 (PST) In-Reply-To: References: <26da6afd-102b-0006-c6b7-a10d8e13f96e@Intel.com> From: Ard Biesheuvel Date: Wed, 28 Feb 2018 08:19:44 +0000 Message-ID: To: Michael Zimmermann Cc: Andrew Fish , "Ni, Ruiyu" , edk2-devel-01 , Leif Lindholm Subject: Re: 'fastboot boot' TPL X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Feb 2018 08:13:39 -0000 Content-Type: text/plain; charset="UTF-8" On 28 February 2018 at 08:15, Michael Zimmermann wrote: >> I agree. Did you run into any issues due to this? > Surprisingly no. I was just trying to understand the fastboot implementation > before I use it on my platform > and was surprised that this works at all. I can imagine that's because this > is supposed to load linux's efistub which probably doesn't do anything but > calling SetVirtualMemoryMap and ExitBootServices. The ARM/Linux EFI stub does quite a bit more than that, actually. It uses the various memory allocation and protocol handling services, to carve out an allocation for the kernel, initrd and device tree, and to access the command line, the EFI_RNG_PROTOCOL (if available) and to interrogate the protocol database for GOP instances. > I can imagine that more complex loaders like the one used for Windows > wouldn't work this way. > No, and this is indeed something that should be fixed. Any clue as to how?