From: Tobias Waldekranz <tobias@waldekranz.com>
To: Masahisa Kojima <masahisa.kojima@linaro.org>, u-boot@lists.denx.de
Cc: Heinrich Schuchardt <xypron.glpk@gmx.de>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Simon Glass <sjg@chromium.org>,
Takahiro Akashi <takahiro.akashi@linaro.org>,
Masahisa Kojima <masahisa.kojima@linaro.org>
Subject: Re: [PATCH v2 0/6] introduce EFI_RAM_DISK_PROTOCOL
Date: Sat, 15 Jul 2023 00:01:35 +0200 [thread overview]
Message-ID: <87jzv2p2yo.fsf@waldekranz.com> (raw)
In-Reply-To: <20230714054406.761508-1-masahisa.kojima@linaro.org>
Hi Masahisa,
On fre, jul 14, 2023 at 14:44, Masahisa Kojima <masahisa.kojima@linaro.org> wrote:
> This series introduces the EFI_RAM_DISK_PROTOCOL implementation.
> The major purpose of this series is a preparation for EFI HTTP(S) boot.
>
> Now U-Boot can download the distro installer ISO image
> via wget or tftpboot commands, but U-Boot can not mount
> the downloaded ISO image.
A while back, I added the blkmap command and backend to U-Boot, which
is, among other things, capable of creating ramdisks. What exactly does
this series add that can't be supported by a block map? There is some
documentation available here:
https://u-boot.readthedocs.io/en/latest/usage/blkmap.html
next prev parent reply other threads:[~2023-07-14 22:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 5:44 [PATCH v2 0/6] introduce EFI_RAM_DISK_PROTOCOL Masahisa Kojima
2023-07-14 5:44 ` [PATCH v2 1/6] efi_loader: add RAM disk device path Masahisa Kojima
2023-07-14 13:39 ` Heinrich Schuchardt
2023-07-18 1:31 ` Masahisa Kojima
2023-07-18 5:57 ` Heinrich Schuchardt
2023-07-18 6:40 ` Masahisa Kojima
2023-07-14 5:44 ` [PATCH v2 2/6] ramdisk: add ramdisk uclass and driver Masahisa Kojima
2023-07-19 15:10 ` Heinrich Schuchardt
2023-07-20 0:18 ` Masahisa Kojima
2023-07-19 19:11 ` Simon Glass
2023-07-20 0:21 ` Masahisa Kojima
2023-07-14 5:44 ` [PATCH v2 3/6] cmd: ramdisk: add ramdisk control command Masahisa Kojima
2023-07-14 5:44 ` [PATCH v2 4/6] efi_loader: add EFI_RAM_DISK_PROTOCOL implementation Masahisa Kojima
2023-07-14 5:44 ` [PATCH v2 5/6] cmd: efidebug: add RAM disk mount command Masahisa Kojima
2023-07-14 5:44 ` [PATCH v2 6/6] efi_selftest: add EFI_RAM_DISK_PROTOCOL selftest Masahisa Kojima
2023-07-14 22:01 ` Tobias Waldekranz [this message]
2023-07-18 2:49 ` [PATCH v2 0/6] introduce EFI_RAM_DISK_PROTOCOL Masahisa Kojima
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-all 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=87jzv2p2yo.fsf@waldekranz.com \
--to=tobias@waldekranz.com \
--cc=ilias.apalodimas@linaro.org \
--cc=masahisa.kojima@linaro.org \
--cc=sjg@chromium.org \
--cc=takahiro.akashi@linaro.org \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
/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