From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=17.151.62.29; helo=mail-in7.apple.com; envelope-from=afish@apple.com; receiver=edk2-devel@lists.01.org Received: from mail-in7.apple.com (mail-out7.apple.com [17.151.62.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id A022321E0BA11 for ; Mon, 12 Feb 2018 16:34:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; d=apple.com; s=mailout2048s; c=relaxed/simple; q=dns/txt; i=@apple.com; t=1518482405; x=2382396005; h=From:Sender:Reply-To:Subject:Date:Message-id:To:Cc:MIME-version:Content-type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-reply-to:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=vtmqjem6FJdrpUSbUdzCZQy3mckGuoL6Vd7CBG6q1D0=; b=K4QE6pZZUFv2YWpkvsGaRQBYeW+6zksWYZ5PVjJtXbf5DxQBx5DHaMVhaMtxUH1m k9X1R5qgEW5VUxuLrVGtrCuY5tjnJw2MGlE6Bh2QA//VEXkDi9FBC8OM5YdyFPNU KM3eNoZMp9p8rnW4jhCZI/J9X5+aW/fpo2fiJvAdO4glHdf7fwbsSG81C+rdJB3Q /qnMeClxK0gu+SZd2a/tPC9eFoK09/hZO9JVo5g/cilLq3UfjwmV3oNjmQ6Up8Y0 kH5LQe7e2TG+4usu7RPz1LjPERfObR0EwQQUeVBQCVIGsHwo0YaYzeWAs70/Khql 2bVtsN71kdcqemDOnGYnOw==; Received: from relay25.apple.com (relay25.apple.com [17.171.128.106]) (using TLS with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mail-in7.apple.com (Apple Secure Mail Relay) with SMTP id 07.C5.04908.5E3328A5; Mon, 12 Feb 2018 16:40:05 -0800 (PST) X-AuditID: 11973e16-446529e00000132c-69-5a8233e5bafb Received: from ma1-mmpp-sz08.apple.com (ma1-mmpp-sz08.apple.com [17.171.128.176]) by relay25.apple.com (Apple SCV relay) with SMTP id 7B.A1.16465.4E3328A5; Mon, 12 Feb 2018 16:40:04 -0800 (PST) MIME-version: 1.0 Received: from [17.234.214.76] by ma1-mmpp-sz08.apple.com (Oracle Communications Messaging Server 8.0.2.2.20180130 64bit (built Jan 30 2018)) with ESMTPSA id <0P4200H5UCIPSXA0@ma1-mmpp-sz08.apple.com>; Mon, 12 Feb 2018 16:40:04 -0800 (PST) Sender: afish@apple.com From: Andrew Fish Message-id: Date: Mon, 12 Feb 2018 16:40:00 -0800 In-reply-to: Cc: edk2-devel@lists.01.org To: Rick Warner References: X-Mailer: Apple Mail (2.3445.5.20) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrELMWRmVeSWpSXmKPExsUiuLohS/epcVOUwcGvYhZ7Dh1lttiybyab A5NH9+x/LB77TrYzBTBFcdmkpOZklqUW6dslcGVM2fyQueBJO2PF3Dvb2RsYf5Z2MXJySAiY SDy8Npuxi5GLQ0hgHZPElOM/WGAS5/7+hEocZpSYOHkCE0iCV0BQ4sfke0BFHBzMAmES52/Y gYSFBL4yShxaWQRiCwuIS7w7s4kZxGYTUJZYMf8DO0SrjcS2e4eZIWp0JFbvfg+2i0VAVaKl fx5YDaeAg8SiD8dZQWxmAWmJhxMhbBGgOR8vdLFB7LKXuPn1NRPEnUoS07/fZgO5U0JgDpvE 76YbTBMYhWYhOXUWwqmzwMZqSXx/1AoVlpc4eF4WIqwp8ezeJ3YIW1viybsLrAsY2VYxCuUm ZuboZuaZ6yUWFOSk6iXn525iBEXCdDuxHYwPV1kdYhTgYFTi4X0wtzFKiDWxrLgy9xCjNAeL kjjv/udAIYH0xJLU7NTUgtSi+KLSnNTiQ4xMHJxSDYxzqgWr5TcvW7r794Yk2VW+vN0Tjutk cfxTtBR/X560KOHxu8OP4vM2rqk/eaFKbLVvyKGJx6MMLj2U+O7l+nmR8jkrbbbIWeGM1vn/ XvLtjdvC3PD4z4d5K1KrUnf37Pi3eV2yP7+0Jdf2NT/N7bzWT9DgYJvWdr+2W08xbt2Tmwsq hVwv2J1XYinOSDTUYi4qTgQA0qi4k2UCAAA= X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrGLMWRmVeSWpSXmKPExsUiuLphg+4T46YogztTbCz2HDrKbLFl30w2 ByaP7tn/WDz2nWxnCmCK4rJJSc3JLEst0rdL4MqYsvkhc8GTdsaKuXe2szcw/iztYuTkkBAw kTj39ydjFyMXh5DAYUaJiZMnMIEkeAUEJX5MvsfSxcjBwSwQJnH+hh1IWEjgK6PEoZVFILaw gLjEuzObmEFsNgFliRXzP7BDtNpIbLt3mBmiRkdi9e73LCA2i4CqREv/PLAaTgEHiUUfjrOC 2MwC0hIPJ0LYIkBzPl7oYoPYZS9x8+trJog7lSSmf7/NNoGRfxaS62YhXDcLbJKWxPdHrVBh eYmD52UhwpoSz+59YoewtSWevLvAuoCRbRWjYFFqTmKlkaleYkFBTqpecn7uJkZI6GbtYLx9 0+wQowAHoxIP74O5jVFCrIllxZW5hxglOJiVRHj/NAOFeFMSK6tSi/Lji0pzUosPMUpzsCiJ 8y42aIgSEkhPLEnNTk0tSC2CyTJxcEo1MKozvLr5/rBf0duTaS36V9tCmCTl0vkvGJxqZTMJ XdVSb9utoat3XWuV49o9i3yWJc0/dVryghfHa6mef4xWJXwnb6Z/WLKDtyszr+mf6f+552ID ZXPqOrqrUl6Vi321ZlHi3364Yc/U5gKrsmnfbX0/BcvN2n/i+JcTp698P95TcCr31q74JiWW 4oxEQy3mouJEAJHOh1FZAgAA X-Content-Filtered-By: Mailman/MimeDel 2.1.23 Subject: Re: how do I use RamDiskDxe? 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: Tue, 13 Feb 2018 00:34:16 -0000 Content-Type: text/plain; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT > On Feb 12, 2018, at 1:07 PM, Rick Warner wrote: > > Hi All, > > I'm trying to develop a tool for automated BIOS flashing from the EFI shell using IPMI serial over lan to drive it. To accomplish this, my plan is to use a network booted EFI shell with a tftp client and a ramdisk to download the flash tools and ROM into as a workspace and then run the flash commands from that ram disk. > > I've been able to successfully build and boot an efi shell from the edk 2 sources including the tftp client. I've also been able to separately build the RamDiskDxe driver from the MdeModulePkg. Loading the RamDiskDxe.efi driver file results in a successful message, but I do not get any usable ram disk made available to me? > > How do I get a usable drive letter/name (ie blk0: or any other name) from the RamDiskDxe driver? > Looks like when you load the RamDiskDxe it registers gEfiRamDiskProtocolGuid https://github.com/tianocore/edk2/blob/master/MdePkg/Include/Protocol/RamDisk.h which notes this API was added in UEFI 2.6 so you can read up on it in that version of the EFI Spec. >>From a quick site read of the code it looks like the driver just produces a Protocol that lets you create a RAM disk and VRF (Setup Pages) that let you configure one. Seems like you still need to call it and give the raw disk image. > Once I've done that, will it be possible to include the RamDiskDxe driver as part of the network bootable efi shell image? I assume I'll need to modify the .dsc file for the ShellPkg to include the MdeModulePkg pieces. > > If anyone has any other suggestions for this, I'm open to ideas. The only way I've been successful in network booting EFI shell is using just that file directly. I tried creating a dos filesystem image with the efi shell file in it just like would work with a USB key, but that would not boot over the network stack. If there is some way of creating a network bootable EFI shell filesystem image (similar to how Linux can network boot a separate vmlinuz kernel and initrd image)? > > Are there any docs that I've missed (I've tried looking in the user docs and on the wiki) regarding setting up RamDiskDxe? > Traditionally network booting has involved loading a single file over the network (like an OS Loader) and that file uses the UEFI networking stack to download (TFTP read) more images (like the Kernel) from a location implied by the location used to download the single file (OS Loader). Thanks, Andrew Fish > Thanks! > Rick Warner > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel