From: Tom Rini <trini@konsulko.com>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.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 19:01:33 -0400 [thread overview]
Message-ID: <20220419230133.GX3045430@bill-the-cat> (raw)
In-Reply-To: <2c7c9217-ad4c-3de4-da82-ca9ba3948ca3@canonical.com>
[-- Attachment #1: Type: text/plain, Size: 2179 bytes --]
On Wed, Apr 20, 2022 at 12:20:43AM +0200, Heinrich Schuchardt wrote:
> On 4/19/22 23:54, Simon Glass wrote:
> > Hi Heinrich,
> >
> > On Tue, 19 Apr 2022 at 15:14, Heinrich Schuchardt
> > <heinrich.schuchardt@canonical.com> 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>
> >> ---
> >> MAINTAINERS | 6 ++
> >> common/board_r.c | 4 +
> >> drivers/Kconfig | 2 +
> >> drivers/Makefile | 1 +
> >> drivers/block/blk-uclass.c | 2 +
> >> drivers/memdisk/Kconfig | 13 ++++
> >> drivers/memdisk/Makefile | 11 +++
> >> drivers/memdisk/memdisk-uclass.c | 22 ++++++
> >> drivers/memdisk/memdisk.c | 128 +++++++++++++++++++++++++++++++
> >> drivers/memdisk/memdisk_file.S | 17 ++++
> >> include/asm-generic/sections.h | 2 +
> >> include/blk.h | 1 +
> >> include/dm/uclass-id.h | 1 +
> >> include/memdisk.h | 28 +++++++
> >> 14 files changed, 238 insertions(+)
> >> create mode 100644 drivers/memdisk/Kconfig
> >> create mode 100644 drivers/memdisk/Makefile
> >> create mode 100644 drivers/memdisk/memdisk-uclass.c
> >> create mode 100644 drivers/memdisk/memdisk.c
> >> create mode 100644 drivers/memdisk/memdisk_file.S
> >> create mode 100644 include/memdisk.h
> >
> > Can this use binman to create the image and find the memdisk?
>
> binman requires board specific layout information. I cannot see how binman
> would help for a Kconfig option that can be switched on and off for any
> board.
>
> binman may provide addresses in the control device-tree which later could be
> relocated. But this seems to result in a larger image size.
This is something analogous to the initrd/initramfs framework within the
Linux kernel, yes?
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-04-19 23:01 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
2022-04-19 22:20 ` Heinrich Schuchardt
2022-04-19 23:01 ` Tom Rini [this message]
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=20220419230133.GX3045430@bill-the-cat \
--to=trini@konsulko.com \
--cc=heinrich.schuchardt@canonical.com \
--cc=sjg@chromium.org \
--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