public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
To: Tom Rini <trini@konsulko.com>
Cc: Simon Glass <sjg@chromium.org>, u-boot@lists.denx.de
Subject: Re: [PATCH 1/1] drivers: add memory disk support
Date: Tue, 19 Apr 2022 23:55:00 +0200	[thread overview]
Message-ID: <14f67fd8-623a-2054-e995-73d54898b886@canonical.com> (raw)
In-Reply-To: <20220419212651.GS3045430@bill-the-cat>

On 4/19/22 23:26, Tom Rini wrote:
> On Tue, Apr 19, 2022 at 11:16:41PM +0200, Heinrich Schuchardt wrote:
> 
>> In some scenarios it is desirable to package U-Boot with other files into
>> a single blob. This patch allows to embed a memory disk into the U-Boot
>> binary. This memory disk can be accessed like any other block
>> device as 'mem 0'.
>>
>> Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
> 
> What's the use case for this, which isn't covered by some combination of
> U-Boot being in a FIT image and the "load a firmware blob" that we have
> today?  Thanks!
> 

"U-Boot being in a FIT image" requires a loader that understands FIT.
"load a firmware blob" requires a block device or a network file system.

If you put U-Boot's payload into the U-Boot blob, you need neither a 
separate block device nor a network file system.

Packaging into U-Boot makes most sense where follow-up binaries are 
tightly integrated:

* adding a custom graphical boot manager as EFI application
* adding iPXE
* delivering device-trees

Best regards

Heinrich


  reply	other threads:[~2022-04-19 21:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-19 21:16 [PATCH 1/1] drivers: add memory disk support Heinrich Schuchardt
2022-04-19 21:26 ` Tom Rini
2022-04-19 21:55   ` Heinrich Schuchardt [this message]
2022-04-19 22:20     ` Heinrich Schuchardt
2022-04-19 23:01       ` Tom Rini
2022-04-20  6:48         ` Heinrich Schuchardt
2022-04-20 13:37           ` Tom Rini
2022-04-19 22:59     ` Tom Rini
2022-04-20  6:58       ` Heinrich Schuchardt
2022-04-20 13:45         ` Tom Rini

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=14f67fd8-623a-2054-e995-73d54898b886@canonical.com \
    --to=heinrich.schuchardt@canonical.com \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.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