From: Rick Warner <rick@microway.com>
To: edk2-devel@lists.01.org
Subject: how do I use RamDiskDxe?
Date: Mon, 12 Feb 2018 16:07:34 -0500 [thread overview]
Message-ID: <be55f5c5-0ca8-0b55-9cbd-b719434a2c50@microway.com> (raw)
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?
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?
Thanks!
Rick Warner
next reply other threads:[~2018-02-12 21:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 21:07 Rick Warner [this message]
2018-02-13 0:40 ` how do I use RamDiskDxe? Andrew Fish
2018-02-13 3:05 ` Wu, Hao A
2018-02-13 16:33 ` Rick Warner
2018-02-14 0:48 ` Wu, Hao A
2018-03-06 19:41 ` Rick Warner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=be55f5c5-0ca8-0b55-9cbd-b719434a2c50@microway.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox