Date: Wed, 17 Jun 2020 13:50:04 -0600 From: Rebecca Cran <rebecca@bsdio.com> To: Warner Losh <imp@bsdimp.com> Cc: "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net>, Miguel C <miguelmclara@gmail.com>, FreeBSD Current <FreeBSD-current@freebsd.org> Subject: Re: CTF: UEFI HTTP boot support Message-ID: <890A1C97-31A1-46F9-BE9B-340F6039DD45@bsdio.com> In-Reply-To: <CANCZdfrJ86b%2Bf6WDi=P9dPv8MJM-%2BC5-6dfBx3KKrct_D8L4tg@mail.gmail.com> References: <CANCZdfrJ86b%2Bf6WDi=P9dPv8MJM-%2BC5-6dfBx3KKrct_D8L4tg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Jun 17, 2020, at 12:12 PM, Warner Losh <imp@bsdimp.com> wrote: > > I missed the start of this thread, so maybe I'm missing a key detail. However, I thought UEFI didn't have a RAM-disk, per se, but that we could load memory areas and pass that into the kernel using freebsd-only methods. But UEFI is a bit weird, so maybe it will generate a virtual cdrom... See https://uefi.org/sites/default/files/resources/FINAL%20Pres4%20UEFI%20HTTP%20Boot.pdf “ RAM Disk Standard • UEFI 2.5 defined RAM Disk device path nodes - Standard access to a RAM Disk in UEFI - Supports Virtual Disk and Virtual CD (ISO image) in persistent or volatile memory” — Rebecca Cran
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?890A1C97-31A1-46F9-BE9B-340F6039DD45>